network.wellknown/wellknown

network.wellknown/wellknown · v0.1.0 · agents-and-memory

network.wellknown/wellknown is healthy: it completed an MCP handshake in 1158 ms and exposes 9 tools.

Live index of AI agents, MCP servers and tools with observed liveness and capability search.

Endpoint: https://wellknown.network/mcp (streamable-http)

Repository · Website · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count9
Latency1158 ms
Last checked (UTC)2026-10-15T12:50:17.051Z

Health history

Checked (UTC)StatusLatencyError
2026-10-15T12:50:17.051ZHealthy1158

Tools (9)

search_agentsSearch 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_agentGiven 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_agentFetch the canonical record for an agent by handle or id, including declared metadata, derived capabilities, observed status, verification and provenance.
check_statusReturns the current observed status, the reason, and the 30-day reliability summary. Never a guess: 'unknown' means we have no evidence.
list_capabilitiesStructured capability slugs (domain.capability) with aliases, for precise filtering.
submit_agentSubmit 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_agentStart 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 /.well-known/, or a file in the repository — plus the claim id
verify_claimCheck 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 verified owner is held for review rather than transferring ownershi
index_statsTruthful counts: indexed records, live endpoints, observations, last crawl.