Koskamo

Wondaverse MCP

An MCP server that checks a website for AI agent readiness by validating llms.txt, robots.txt, A2A agent cards, and other factors, then providing ranked fixes and text to paste.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Wondaverse MCP logo, by WondaverseVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-01Operated by Wondaverse
MCP endpoint (Streamable HTTP)
https://wondaverse.com/check/mcp
Vendor documentation

What you can do with it

  • Validate llms.txt and robots.txt for AI bots
  • Check A2A agent card presence
  • Generate drafted fixes for AI readiness

Source and maintenance

Vendor evidenceRegistry 1.0.0

Protocol and capabilities

Server
agent-readiness 1.0.0
MCP protocol
2025-06-18
Tools
1 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Checks how well a website works with AI agents: whether agents that act for a person, AI search and training crawlers may fetch it (robots.txt, read by purpose), whether its llms.txt is valid and its links resolve, whether an MCP endpoint answers and describes its tools, whether its A2A agent card is complete, and whether the home page can be indexed and is described. The answer lists findings and what to fix, most important first, with text to paste: a drafted llms.txt, robots.txt lines, an agent card. After a fix, call it again with fresh=true to see what changed. Not logged: who asks is never recorded. Provided by wondaverse.com (https://wondaverse.com/check).

Tools

1 advertised

check_site — Agent-readiness check
Advertised by the server during the last successful anonymous check.

Check how well a website welcomes AI agents: robots.txt rules for AI bots, llms.txt, sitemap, search indexing, title and description, A2A agent card, MCP endpoint, OpenAPI description, and whether automated visitors are blocked. Returns what is there, what is missing and how to fix it.

check_site input schema
{
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "The website to check, for example https://example.com."
    },
    "fresh": {
      "type": "boolean",
      "description": "Optional: check again now instead of using a result from the last 10 minutes, for example after a fix. The answer then says what changed."
    }
  },
  "additionalProperties": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
398 ms
95th percentile latency
398 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 398 ms · metadata changed · 1 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http wondaverse-mcp https://wondaverse.com/check/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add wondaverse-mcp --url https://wondaverse.com/check/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable wondaverse-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "wondaverse-mcp": {
      "url": "https://wondaverse.com/check/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "wondaverse-mcp": {
      "type": "streamableHttp",
      "url": "https://wondaverse.com/check/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start wondaverse-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "wondaverse-mcp": {
      "type": "http",
      "url": "https://wondaverse.com/check/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http wondaverse-mcp https://wondaverse.com/check/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "wondaverse-mcp": {
      "url": "https://wondaverse.com/check/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "wondaverse-mcp": {
      "serverUrl": "https://wondaverse.com/check/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Wondaverse MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run Wondaverse MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing