network.wellknown/wellknown
REMOTE · WELLKNOWN.NETWORK · 2 COMPONENTS · SCANNED SEP 25
Live index of AI agents, MCP servers and tools with observed liveness and capability search.
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 9 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 Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 858 tokens (~95/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 58% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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 network.wellknown/wellknown MCP server?
network.wellknown/wellknown is a hosted endpoint at https://wellknown.network/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 · wellknown.network
claude mcp add --transport http network-wellknown-wellknown 'https://wellknown.network/mcp'
{
"mcpServers": {
"network-wellknown-wellknown": {
"url": "https://wellknown.network/mcp"
}
}
} {
"servers": {
"network-wellknown-wellknown": {
"type": "http",
"url": "https://wellknown.network/mcp"
}
}
} [mcp_servers.network-wellknown-wellknown] url = "https://wellknown.network/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"network-wellknown-wellknown": {
"type": "remote",
"url": "https://wellknown.network/mcp",
"enabled": true
}
}
} openclaw mcp add network-wellknown-wellknown --url 'https://wellknown.network/mcp' --transport streamable-http
mcp_servers:
network-wellknown-wellknown:
url: "https://wellknown.network/mcp" {
"McpServers": {
"network-wellknown-wellknown": {
"Transport": "http",
"Url": "https://wellknown.network/mcp"
}
}
} assistant mcp add network-wellknown-wellknown -t streamable-http -u 'https://wellknown.network/mcp'
{
"mcpServers": {
"network-wellknown-wellknown": {
"type": "http",
"url": "https://wellknown.network/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.
- 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
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
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 25 Sept 2026 · Probed https://wellknown.network/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=wellknown.network | CN=YE2,O=Let's Encrypt,C=US | 5 Sept 2026 | 4 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 552b048bf371cb588b8d6b0150289ca3298 |
| SANs: wellknown.network | ||||||
| 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 wellknown.network. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| network. | present | 40414 | 8 | Verified |
| wellknown.network. | 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'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://www.google-analytics.com https://*.google-analytics.com; font-src 'self' data:; connect-src 'self' https://www.googletagmanager.com https://www.google-analytics.com https://*.google-analytics.com https://*.analytics.google.com; frame-ancestors 'none'; base-uri 'self'; form-action 'self' https://github.com |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://wellknown.network/mcp | Verified | 200 | |
| http (plaintext) | http://wellknown.network/mcp | HTTPS enforced | 301 | https://wellknown.network/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 →
check_status Check liveness evidence for an agent ~47
Returns the current observed status, the reason, and the 30-day reliability summary. Never a guess: 'unknown' means we have no evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| idOrHandle | string | yes | – |
No output schema declared.
No examples provided.
claim_agent Claim a record you control ~198
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 /.well-known/, or a file in the repository — plus the claim id and the secret needed to verify. Publish the proof, then call verify_claim. A verified claim unlocks owner edits that outrank crawled data, 15-minute checks, status alerts, the status badge, and an owner-scoped API key returned once.
| Name | Type | Req | Description |
|---|---|---|---|
| idOrHandle | string | yes | The record to claim, by handle or id (from search_agents or get_agent) |
| method | string | yes | dns_txt and well_known_file prove control of a domain; repo_file proves control of the source repository |
| target | string | – | Which derived target to use, when the record offers several. Omit to take the first. |
No output schema declared.
No examples provided.
get_agent Get an agent record ~43
Fetch the canonical record for an agent by handle or id, including declared metadata, derived capabilities, observed status, verification and provenance.
| Name | Type | Req | Description |
|---|---|---|---|
| idOrHandle | string | yes | – |
No output schema declared.
No examples provided.
index_stats Index statistics ~23
Truthful counts: indexed records, live endpoints, observations, last crawl.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_capabilities List the capability taxonomy ~25
Structured capability slugs (domain.capability) with aliases, for precise filtering.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
resolve_agent Resolve the best available agent for a task ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| need | string | yes | – |
| protocols | array | – | – |
| remoteOnly | boolean | – | Default true: only network-callable candidates |
| requireLive | boolean | – | Only candidates that responded to a check in the last 24h |
No output schema declared.
No examples provided.
search_agents Search the agent index ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| protocols | array | – | Restrict to protocols |
| query | string | yes | What you need, e.g. 'search the web and cite sources' or 'postgres mcp server' |
| remoteOnly | boolean | – | Only agents with a network endpoint (excludes local packages) |
| status | array | – | – |
No output schema declared.
No examples provided.
submit_agent Announce an agent to the index ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cardUrl | string | – | https://<host>/.well-known/agent-card.json |
| manifest | object | – | Inline manifest: name, kind, summary, endpoints[{url,type}], protocols, tags, repository, homepage |
No output schema declared.
No examples provided.
verify_claim Verify a claim you started ~92
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 verified owner is held for review rather than transferring ownership.
| Name | Type | Req | Description |
|---|---|---|---|
| claimId | string | yes | – |
| verifySecret | string | yes | The verifySecret returned by claim_agent |
No output schema declared.
No examples provided.
What is the network.wellknown/wellknown MCP server?
network.wellknown/wellknown is an MCP server listed in the public MCP registry as network.wellknown/wellknown. Live index of AI agents, MCP servers and tools with observed liveness and capability search. This page covers its hosted endpoint (https://wellknown.network/mcp).
Is the network.wellknown/wellknown MCP server safe to use?
network.wellknown/wellknown scores 73 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 network.wellknown/wellknown MCP server expose?
network.wellknown/wellknown exposes 9 tools: search_agents, resolve_agent, get_agent, check_status, list_capabilities, and 4 more. Their descriptions and schemas cost roughly 747 tokens of context every time the server is loaded.
Does the network.wellknown/wellknown MCP server require authentication?
No. We connected to network.wellknown/wellknown without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the network.wellknown/wellknown MCP server still maintained?
network.wellknown/wellknown is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.