# Wellknown (remote · wellknownhq.com)

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

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-18

## Components

- remote · `wellknownhq.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/com-wellknownhq-wellknown/wellknownhq.md), [page](https://verifymcp.io/servers/com-wellknownhq-wellknown/wellknownhq)

## Channel facts

- Endpoint: `https://wellknownhq.com/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-08-18.

- **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 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.
  - 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**: 79/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 706 tokens (~141/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

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

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-wellknownhq-wellknown --url https://wellknownhq.com/mcp --transport streamable-http
```

### Hermes

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

### Other

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

## 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-08-17 (score 69, +1)

- [security] Tool “get_capability” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 125 → 141

### 2026-08-15 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-14 (score 67, +3)

- [security improvement] HSTS header: fail → pass
- [functional] MCP protocol: Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
- [functional] MCP protocol version: 2026-07-28 → 2025-11-25

### 2026-08-13 (score 64, 0)

- [functional regression] Schema quality: pass → fail
- [functional improvement] Stability: unverified → 0.03
- [functional] New tool “get_capability”
- [functional] New tool “search_registry”

### 2026-08-12 (score 64)

First indexed and scored.

## MCP tools (5)

### `search_registry` (~140 tokens)

Search the open registry of agent capabilities

Find capabilities, MCP servers, and APIs that agents can use, across every publisher indexed by Wellknown. 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. Use this when you need a capability you do not already have wired up.

Input parameters:

- `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, required): What you need, in your own words. e.g. 'query a postgres database'.

### `get_capability` (~196 tokens)

Resolve one capability by identifier

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.

Input parameters:

- `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, required): A urn:air: identifier.

### `audit_domain` (~143 tokens)

Audit a domain's agent discoverability

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.

Input parameters:

- `competitors` (array): Up to 3 competitor domains to compare against.
- `domain` (string, required): Domain to audit, e.g. notion.so. URLs are accepted and reduced to the host.

### `validate_catalog` (~132 tokens)

Validate an ai-catalog.json

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.

Input parameters:

- `catalog` (string, required): The catalog document as a JSON string.
- `domain` (string, required): Domain the catalog is served from. Needed to check that entry URNs name the right publisher, which is how copied examples get caught.

### `generate_catalog` (~95 tokens)

Generate a conformant ai-catalog.json

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.

Input parameters:

- `domain` (string, required): Domain to generate a catalog for.

## Diagnostics

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

## Score history

- 2026-08-18: 69
- 2026-08-17: 69
- 2026-08-16: 68
- 2026-08-15: 68
- 2026-08-14: 67
- 2026-08-13: 64
- 2026-08-12: 64

## Links

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