wellknown MCP server
network.wellknown/wellknownwellknown.networkstreamable-httpv0.1.0Scanned
Live index of AI agents, MCP servers and tools with observed liveness and capability search.
9 tools: 4 change things and 5 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the wellknown MCP server can do
The wellknown MCP server is published by wellknown.network, a domain the MCP Registry verified. It has 9 tools. It can create or change data (4 tools: submit_agent, claim_agent, verify_claim and index_stats), but cannot delete data. 5 tools only read.
1 tool brings in text other people can write (index_stats).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 18, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
9 tools
Changes things 4Claude Code: ask
claim_agentStart proving that you operate an indexed agent.No findings
Why it is in this group
- The description's first verb is "start": a word for a change.
Description, as the server wrote it 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.
index_statsTruthful counts: indexed records, live endpoints, observations, last crawl.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe description's first sentence says "crawl": it reads web pages, which anyone can write.
Description, as the server wrote it Truthful counts: indexed records, live endpoints, observations, last crawl.
submit_agentSubmit an agent by its A2A Agent Card URL (preferred, strongest provenance) or an inline manifest.No findings
Why it is in this group
- The name "submit_agent" says "submit": a word for a change.
Description, as the server wrote it 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.
verify_claimCheck the published proof now.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Only reads 5Show 5 read-only tools
check_statusReturns the current observed status, the reason, and the 30-day reliability summary.No findings
Why it is in this group
- The name "check_status" says "status": a word for reading.
Description, as the server wrote it Returns the current observed status, the reason, and the 30-day reliability summary. Never a guess: 'unknown' means we have no evidence.
get_agentFetch the canonical record for an agent by handle or id, including declared metadata, derived capabilities, observed status, verification and provenance.No findings
Why it is in this group
- The name "get_agent" says "get": a word for reading.
Description, as the server wrote it Fetch the canonical record for an agent by handle or id, including declared metadata, derived capabilities, observed status, verification and provenance.
list_capabilitiesStructured capability slugs (domain.capability) with aliases, for precise filtering.No findings
Why it is in this group
- The name "list_capabilities" says "list": a word for reading.
Description, as the server wrote it Structured capability slugs (domain.capability) with aliases, for precise filtering.
resolve_agentGiven a task and constraints, returns ranked candidates and a recommendation with its evidentiary basis (observed liveness or unverified).No findings
Why it is in this group
- The name "resolve_agent" says "resolve": a word for reading.
Description, as the server wrote it 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.
search_agentsSearch indexed agents, MCP servers and tools by natural-language capability or task.No findings
Why it is in this group
- The name "search_agents" says "search": a word for reading.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:16 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://wellknown.network/mcp: tools/list returned 9 tools to an anonymous client, including submit_agent (write), claim_agent (write), verify_claim (write), index_stats (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http wellknown https://wellknown.network/mcpclaude mcp add --transport http wellknown https://wellknown.network/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__wellknown__search_agents",
"mcp__wellknown__resolve_agent",
"mcp__wellknown__get_agent",
"mcp__wellknown__check_status",
"mcp__wellknown__list_capabilities"
],
"ask": [
"mcp__wellknown__submit_agent",
"mcp__wellknown__claim_agent",
"mcp__wellknown__verify_claim",
"mcp__wellknown__index_stats"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as wellknown. Review it before you use it.
Capability tags behind 1 rule
- mcp__wellknown__index_stats untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/network.wellknown/wellknown/verify?hash=2ec49410c0145aab81ef22c42ae388ea9a3a4d462b9bf7aa822a52833f37e209" | jq -e '.changed == false'Pinned hash 2ec49410c014, from Nov 18, 2026, 01:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/network.wellknown/wellknown/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/network.wellknown/wellknown)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:53 UTC.
wellknown MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the wellknown MCP server safe?
- No scan can promise that. What its definitions show: 9 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the wellknown MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the wellknown MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the wellknown MCP server have?
- 9 tools: 4 write, 5 read. submit_agent, claim_agent, verify_claim, index_stats, search_agents, resolve_agent, get_agent, check_status and 1 more.
Does the wellknown MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the wellknown MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the wellknown MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.