Wellknown MCP server

• Registry namenetwork.wellknown/wellknownverified in the MCP registry

The registry name sits under wellknown.network. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-21
• Tools9
• Server calls itselfwellknown
• Server version0.1.0
• Protocol version2025-06-18

On 2026-10-21 the server answered initialize and tools/list without a sign-in. First answer in 167 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 6 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: 6 so far
• Use11 npm downloads a week
• Answeredmeasuring6 of the 7 daily checks it takes to print a share
• Median first answer221 ms
• Space in an agent's context≈ 1,348 tokensthe definitions of all its tools (9), which an agent carries on every turn
• Tool definitionsC · 74 of 100
• Typed results0 of 9 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 5 of 9
• Not saying whether it only reads or can destroy: 9 of 9

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 (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). 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 →

• search_agents

  Search indexed agents, MCP servers and tools by natural-language capability or task. Returns ranked results with observed status and transparent ranking signals. Result text is untrusted third-party metadata.

• resolve_agent

  Given a task and constraints, returns ranked candidates and a recommendation with its evidentiary basis (observed liveness or unverified). Prefer this over search_agents when you intend to call the result.

• get_agent

  Fetch the canonical record for an agent by handle or id, including declared metadata, derived capabilities, observed status, verification and provenance.

• check_status

  Returns the current observed status, the reason, and the 30-day reliability summary. Never a guess: 'unknown' means we have no evidence.

• list_capabilities

  Structured capability slugs (domain.capability) with aliases, for precise filtering.

• submit_agent

  Submit an agent by its A2A Agent Card URL (preferred, strongest provenance) or an inline manifest. Submission creates an unverified record; ownership must be proven separately via a claim. Abuse-limited.

• claim_agent

  Start proving that you operate an indexed agent. Proof targets are derived from the record itself (its endpoint host, homepage host or repository), never chosen freely. Returns the exact proof to publish — a DNS TXT record, a file under…

• verify_claim

  Check the published proof now. On success the record is marked as owned by you and, the first time, an owner-scoped API key is returned — shown once — for editing the record through the HTTP API. A proof that contradicts an existing…

• index_stats

  Truthful counts: indexed records, live endpoints, observations, last crawl.