# network.wellknown/wellknown (remote · wellknown.network)

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

- Trust score: 73/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `wellknown.network`: 73/100 (this document), [markdown](https://verifymcp.io/servers/network-wellknown-wellknown/wellknown.md), [page](https://verifymcp.io/servers/network-wellknown-wellknown/wellknown)
- npm · `wellknown-mcp`: 39/100, [markdown](https://verifymcp.io/servers/network-wellknown-wellknown/wellknown-mcp.md), [page](https://verifymcp.io/servers/network-wellknown-wellknown/wellknown-mcp)

## Channel facts

- Endpoint: `https://wellknown.network/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 858 tokens (~95/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 58% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http network-wellknown-wellknown 'https://wellknown.network/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "network-wellknown-wellknown": {
      "url": "https://wellknown.network/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "network-wellknown-wellknown": {
      "type": "http",
      "url": "https://wellknown.network/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.network-wellknown-wellknown]
url = "https://wellknown.network/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "network-wellknown-wellknown": {
      "type": "remote",
      "url": "https://wellknown.network/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add network-wellknown-wellknown --url 'https://wellknown.network/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  network-wellknown-wellknown:
    url: "https://wellknown.network/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "network-wellknown-wellknown": {
      "Transport": "http",
      "Url": "https://wellknown.network/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add network-wellknown-wellknown -t streamable-http -u 'https://wellknown.network/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 73, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 73, +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.

### 2026-09-21 (score 72, +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.

### 2026-09-19 (score 71, +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.

### 2026-09-17 (score 70, +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.

### 2026-09-15 (score 69, +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.

### 2026-09-13 (score 68, +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.

### 2026-09-11 (score 67, +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.

## MCP tools (9)

### `search_agents` (~115 tokens)

Search the agent index

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.

Input parameters:

- `limit` (integer)
- `protocols` (array): Restrict to protocols
- `query` (string, required): 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)

### `resolve_agent` (~106 tokens)

Resolve the best available agent for a task

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.

Input parameters:

- `limit` (integer)
- `need` (string, required)
- `protocols` (array)
- `remoteOnly` (boolean): Default true: only network-callable candidates
- `requireLive` (boolean): Only candidates that responded to a check in the last 24h

### `get_agent` (~43 tokens)

Get an agent record

Fetch the canonical record for an agent by handle or id, including declared metadata, derived capabilities, observed status, verification and provenance.

Input parameters:

- `idOrHandle` (string, required)

### `check_status` (~47 tokens)

Check liveness evidence for an agent

Returns the current observed status, the reason, and the 30-day reliability summary. Never a guess: 'unknown' means we have no evidence.

Input parameters:

- `idOrHandle` (string, required)

### `list_capabilities` (~25 tokens)

List the capability taxonomy

Structured capability slugs (domain.capability) with aliases, for precise filtering.

### `submit_agent` (~98 tokens)

Announce an agent to the index

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.

Input parameters:

- `cardUrl` (string): https://<host>/.well-known/agent-card.json
- `manifest` (object): Inline manifest: name, kind, summary, endpoints[{url,type}], protocols, tags, repository, homepage

### `claim_agent` (~198 tokens)

Claim a record you control

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.

Input parameters:

- `idOrHandle` (string, required): The record to claim, by handle or id (from search_agents or get_agent)
- `method` (string, required): 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.

### `verify_claim` (~92 tokens)

Verify a claim you started

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.

Input parameters:

- `claimId` (string, required)
- `verifySecret` (string, required): The verifySecret returned by claim_agent

### `index_stats` (~23 tokens)

Index statistics

Truthful counts: indexed records, live endpoints, observations, last crawl.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/network-wellknown-wellknown/wellknown#diagnostics

## Score history

- 2026-09-25: 73
- 2026-09-24: 73
- 2026-09-23: 73
- 2026-09-22: 72
- 2026-09-21: 72
- 2026-09-20: 71
- 2026-09-19: 71
- 2026-09-18: 70
- 2026-09-17: 70
- 2026-09-16: 69
- 2026-09-15: 69
- 2026-09-14: 68
- 2026-09-13: 68
- 2026-09-12: 67
- 2026-09-11: 67
- 2026-09-10: 66
- 2026-09-09: 66

## Common questions

### 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.

## Links

- Remote endpoint: https://wellknown.network/mcp
- Repository: https://github.com/sanemavcil/wellknown-mcp
- Website: https://wellknown.network/
- Changelog RSS feed: https://verifymcp.io/servers/network-wellknown-wellknown/wellknown.xml
- Changelog JSON feed: https://verifymcp.io/servers/network-wellknown-wellknown/wellknown.json
- HTML version of this page: https://verifymcp.io/servers/network-wellknown-wellknown/wellknown