Wellknown MCP MCP server

A live, machine-queryable index of AI agents, MCP servers, and tools that separates declared capabilities from observed liveness and reliability. It allows agents to search for other agents, resolve the best agent for a task, retrieve canonical records, check status, and list capabilities without requiring authentication.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Wellknown

MCP endpoint (Streamable HTTP)

https://wellknown.network/mcp

Vendor documentation

What you can do with it

Search for AI agents using natural language queries with protocol filters
Resolve the best available agent for a specific task
Check the observed status and 30-day reliability of an agent
Retrieve full canonical records for specific agent handles

Tools advertised by the last live check:

search_agents
resolve_agent
get_agent
check_status
list_capabilities
submit_agent
claim_agent
verify_claim
index_stats

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 a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http wellknown-mcp https://wellknown.network/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 wellknown-mcp --url https://wellknown.network/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable wellknown-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "wellknown-mcp": {
      "url": "https://wellknown.network/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "wellknown-mcp": {
      "type": "streamableHttp",
      "url": "https://wellknown.network/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start wellknown-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "wellknown-mcp": {
      "type": "http",
      "url": "https://wellknown.network/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 wellknown-mcp https://wellknown.network/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": {
    "wellknown-mcp": {
      "url": "https://wellknown.network/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": {
    "wellknown-mcp": {
      "serverUrl": "https://wellknown.network/mcp"
    }
  }
}

See all 782

Do you run Wellknown 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