Other · Remote MCP server
Sitelas
Build a real website from a chat - then run it: read messages, check traffic, publish changes.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.sitelas/sitelas- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-08-06
- Updated
- 2026-08-06
- Publisher
- com.sitelas
- Namespace
- Namespace verified by the MCP Registry via the domain sitelas.com · how
- Website
- sitelas.com
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://sitelas.com/api/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Sitelas
Sitelas is a remote MCP server: there is nothing to install. Its endpoint is https://sitelas.com/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
Site checks
The website's own root, sitelas.com, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | No real file found |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More other servers
| Server | Runs |
|---|---|
| Site-ShotWebsite screenshots for AI agents: full-page, country proxies, ad & cookie-banner removal. | Local · stdio |
| SitecombA digital audit for small-business websites: a score out of 100 and the main problems. | Remote · HTTPLive check: ✓ handshake |
| SiteGPTManage SiteGPT chatbots and account resources through the SiteGPT API v2. | Remote · HTTPLive check: sign-in required |
| SiteHelmLet an AI agent run your WordPress site: every write previewed, verified and reversible. | Remote · HTTP |
| Sitemap StatsSitemap Stats MCP - reads a domain's sitemap(s) and reports their STRUCTURE,. | Remote · HTTPLive check: ✓ handshake |
| Sitemap URL Extractor for AI AgentsX402 sitemap discovery and URL extraction for agents. $0.0001 per emitted URL. | Remote · HTTPLive check: ✓ handshake |
| sitepulsar.aiSitePulsar AEO audits: fetch FIND/READ/USE agent-readiness scores for any website. | Remote · HTTPLive check: ✓ handshake |
| sitesai.netSitesAI App for civil/earthworks contractors: leads, jobs, shifts, dockets, sites, compliance. | Remote · HTTPLive check: sign-in required |