Visible by AI MCP server
Which MCP servers are Visible by AI's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-30
- Registry namecom.visiblebyagents.mcp/slipdockverified in the MCP registry
The registry name sits under visiblebyagents.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-30
- Tools3
- Server calls itselfcom.visiblebyagents.mcp/slipdock
- Server version1.0.1
- Protocol version2025-06-18
On 2026-10-30 the server answered initialize and tools/list without a sign-in. First answer in 143 ms.
- Its tools do none of the product's use cases we checked: check how AI assistants describe your business; publish ten articles written for search and AI answers.
- Checked on 3 of the 7 days it takes to judge reliability.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
- What an agent can do with it0 of 2 use cases
- Answeredmeasuring3 of the 7 daily checks it takes to print a share
- Median first answer183 ms
- Space in an agent's context≈ 205 tokensthe definitions of all its tools (3), which an agent carries on every turn
- Tool definitionsB · 83 of 100
- Typed results0 of 3 toolsdeclared outputSchema: results come typed, read once
- Not saying whether it only reads or can destroy: 3 of 3
What an agent can do with it
- cannot · check how AI assistants describe your business
- not sure · build a static microsite structured for AI answers
- cannot · publish ten articles written for search and AI answers
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
get_slipdock_infoWhat Slipdock is: agent-first infrastructure (domains, DNS, TLS, app hosting, static sites). Returns signup flow and capabilities. No arguments.
get_slipdock_pricingCurrent Slipdock pricing (hosting plans + domain registration), read live from the public slipdock.ai/pricing.json, including wholesale cost transparency. No arguments.
how_an_agent_signs_upExact, human-free steps for an AI agent to create a Slipdock workspace and start hosting, via the public REST API. No arguments.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"slipdock": {
"type": "http",
"url": "https://visiblebyagents.com/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http visiblebyagents https://visiblebyagents.com/mcpclaude.ai, ChatGPT and other clients: add https://visiblebyagents.com/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.