Wellknown
REMOTE · WELLKNOWNHQ.COM · SCANNED OCT 2
Check whether AI agents can discover, validate, and trust your domain's services.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 936 tokens (~187/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Wellknown MCP server?
Wellknown is a hosted endpoint at https://wellknownhq.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · wellknownhq.com
claude mcp add --transport http com-wellknownhq-wellknown 'https://wellknownhq.com/mcp'
{
"mcpServers": {
"com-wellknownhq-wellknown": {
"url": "https://wellknownhq.com/mcp"
}
}
} {
"servers": {
"com-wellknownhq-wellknown": {
"type": "http",
"url": "https://wellknownhq.com/mcp"
}
}
} [mcp_servers.com-wellknownhq-wellknown] url = "https://wellknownhq.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-wellknownhq-wellknown": {
"type": "remote",
"url": "https://wellknownhq.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-wellknownhq-wellknown --url 'https://wellknownhq.com/mcp' --transport streamable-http
mcp_servers:
com-wellknownhq-wellknown:
url: "https://wellknownhq.com/mcp" {
"McpServers": {
"com-wellknownhq-wellknown": {
"Transport": "http",
"Url": "https://wellknownhq.com/mcp"
}
}
} assistant mcp add com-wellknownhq-wellknown -t streamable-http -u 'https://wellknownhq.com/mcp'
{
"mcpServers": {
"com-wellknownhq-wellknown": {
"type": "http",
"url": "https://wellknownhq.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
- Injection markers: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.77 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 3 Sept 26 76
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.70 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 2 Oct 2026 · Probed https://wellknownhq.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=wellknownhq.com | CN=YE2,O=Let's Encrypt,C=US | 13 Aug 2026 | 11 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 672b626aa8e42d1bbac7cf0530a5fd67bad |
| SANs: wellknownhq.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of wellknownhq.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| wellknownhq.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; img-src 'self' data:; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; script-src 'self' 'unsafe-inline' https://www.paypal.com https://checkout.razorpay.com; connect-src 'self' https://api-m.sandbox.paypal.com https://api-m.paypal.com; frame-src https://www.paypal.com https://api.razorpay.com |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| www-authenticate | Bearer resource_metadata="https://wellknownhq.com/.well-known/oauth-protected-resource/mcp" |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://wellknownhq.com/mcp | Verified | 200 | |
| http (plaintext) | http://wellknownhq.com/mcp | HTTPS enforced | 308 | https://wellknownhq.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_domain Audit a domain's agent discoverability ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| competitors | array | – | Up to 3 competitor domains to compare against. |
| domain | string | yes | Domain to audit, e.g. notion.so. URLs are accepted and reduced to the host. |
No output schema declared.
No examples provided.
generate_catalog Generate a conformant ai-catalog.json ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to generate a catalog for. |
No output schema declared.
No examples provided.
get_capability Resolve one capability by identifier ~196
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from_query | string | – | Optional. The queryId from the search_registry response that led you here. Passing it lets the registry learn which results were actually useful, which improves ranking for everyone. Nothing about yo… |
| identifier | string | yes | A urn:air: identifier. |
No output schema declared.
No examples provided.
search_registry Search the open registry of agent capabilities ~194
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results, default 10. |
| published_only | boolean | – | Only entries found on the publisher's own domain, excluding anything mirrored from another registry. |
| query | string | yes | What you need, in your own words. e.g. 'query a postgres database'. |
No output schema declared.
No examples provided.
validate_catalog Validate an ai-catalog.json ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| catalog | string | yes | The catalog document as a JSON string. |
| domain | string | yes | Domain the catalog is served from. Needed to check that entry URNs name the right publisher, which is how copied examples get caught. |
No output schema declared.
No examples provided.
What is the Wellknown MCP server?
Wellknown is an MCP server listed in the public MCP registry as com.wellknownhq/wellknown. Check whether AI agents can discover, validate, and trust your domain's services. This page covers its hosted endpoint (https://wellknownhq.com/mcp).
Is the Wellknown MCP server safe to use?
Wellknown scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Wellknown MCP server expose?
Wellknown exposes 5 tools: search_registry, get_capability, audit_domain, validate_catalog, generate_catalog. Their descriptions and schemas cost roughly 760 tokens of context every time the server is loaded.
Does the Wellknown MCP server require authentication?
No. We connected to Wellknown without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Wellknown MCP server still maintained?
Wellknown is still listed as active in the MCP registry. We last reached this channel on 2 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.