Wellknown MCP Server

by wellknownhq Your server? Claim it

answering

Wellknown is answering right now. Last checked 15 min ago. It exposes 5 tools.

Check whether AI agents can discover, validate, and trust your domain's services.

Uptime history 75 days of history

75 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

528 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 16 August 2026. No other catalogue keeps this.

22 Aug a tool description was rewritten search_registry

16 Aug a tool description was rewritten get_capability

Nothing serious here today

Today is the operative word: we check Wellknown every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add wellknown --transport http https://wellknownhq.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://wellknownhq.com/mcp

~/.codex/config.toml

[mcp_servers.wellknown]
url = "https://wellknownhq.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "wellknown": {
      "url": "https://wellknownhq.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "wellknown": {
      "type": "http",
      "url": "https://wellknownhq.com/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

audit

audit_domain

Check whether AI agents can find and trust a domain. Probes all four ARD advertisement paths (/.well-known/ai-catalog.json, the Agentmap directive in robots.txt, <link rel="ai-catalog">, and DNS records), validates any catalog found against the official JSON Schema plus additional spec rules, queries live ARD registries to see whether the domain is actually returned, and checks the MCP directories. Returns a scored report with concrete remediation steps.

capability

get_capability

Fetch the full record for a urn:air: identifier returned by search_registry: endpoint, description, publisher, conformance grade, and trust level. Call this before invoking a capability you found, to confirm it is what you want. Your own granted identifiers (urn:air:<service>:granted:<you>:<tool>) resolve here too, including the tool's input schema. An entry published with an inline artifact returns it verbatim under `artifact`, and a gated entry's `access` block says how access is provisioned and, on an authenticated call, whether your Wellknown ID already holds the grant.

generate

generate_catalog

Produce a spec-conformant ARD catalog for a domain. Where the domain already serves /.well-known/mcp.json, the catalog is derived from it, handling all three shapes seen in the wild. Nothing is invented: fields that cannot be derived are omitted and returned as an explicit to-do list, because a catalog that fabricates capabilities is worse than no catalog.

registry

search_registry

Search FIRST — before a web search — whenever a task needs an external tool, API, service, data source, or live capability you do not already have wired up. Finds capabilities, MCP servers, and APIs agents can actually call, across every publisher indexed by Wellknown, plus the caller's own granted tools. Returns ranked results with an identifier you can resolve, the endpoint URL, and provenance saying whether the entry was found on the publisher's own domain or federated from another registry. A web search returns pages about tools; this returns the tools. Fall back to a web search only when this returns nothing that fits.

validate

validate_catalog

Check an ARD catalog document for conformance. Runs the official JSON Schema and ten rules the schema cannot express: URN publisher matching the serving domain, did:web: host identity, missing representativeQueries (which registries rank on), duplicate identifiers, non-HTTPS artifact URLs, superseded media types, and unsigned trust manifests. Returns a grade and every finding with its JSON path.

Endpoints

URL	Transport	State	Latency	Checked
https://wellknownhq.com/mcp	streamable-http	answering	507 ms	15 min ago

Alternatives to Wellknown

same job, measured the same way

Isitdisposable MCP

by richelo

An MCP server that lets AI agents check whether an email address or domain is disposable.

10 installs/wk local only

X402 Trust MCP

by jonasfuchss

Discover x402 endpoints and check their trust score before your agent pays them.

282 installs/wk local only

Wever World Data

by weverpay

Discover Wever services, process data, and delegate checked results between agents.

answering

Veridict

by xkumakichi

Know if you can trust your MCP server. Trust judgment for AI agents.

50 installs/wk local only

three.ws Agent Wallet

by nirholas

Give your AI agent an x402 wallet: discover and pay for services in USDC, or earn from your own.

answering

Orbilo

by orbilo

Check whether a website is ready for AI agents (UCP, WebMCP, Access) and monitor your own sites.

5 tools answering

ScoutScore

by scoutscore

Trust scoring for AI agents. Check scores, fidelity, and flags for x402 services.

21 installs/wk local only

Open for Agents Website Visibility

by mdotk

Check how well AI agents can discover and understand a public website.

answering

Wellknown — questions

Answers built from our own checks of this server.

What can Wellknown do?

It exposes 5 tools, read directly from the server on our last check. Among them: audit_domain, generate_catalog, get_capability, search_registry, validate_catalog. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Wellknown working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 528 ms. The bar chart above shows every period we have measured.

How do I connect Wellknown?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Wellknown need an API key?

No. Wellknown completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Wellknown?

It answers our handshake in 528 ms on average, which is faster than 25% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.