# sh.knowngood/knowngood (remote · knowngood.sh)

Search agent-ready sites or fetch one site's report; every capability probe-verified, dated.

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

## Components

- remote · `knowngood.sh`: 78/100 (this document), [markdown](https://verifymcp.io/servers/sh-knowngood-knowngood/knowngood.md), [page](https://verifymcp.io/servers/sh-knowngood-knowngood/knowngood)

## Channel facts

- Endpoint: `https://knowngood.sh/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.7.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-24.

- **Endpoint Security**: 66/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 3 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 is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 628 tokens (~209/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 82% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the sh.knowngood/knowngood MCP server?

sh.knowngood/knowngood is a hosted endpoint at https://knowngood.sh/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 sh-knowngood-knowngood 'https://knowngood.sh/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "sh-knowngood-knowngood": {
      "url": "https://knowngood.sh/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.sh-knowngood-knowngood]
url = "https://knowngood.sh/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add sh-knowngood-knowngood --url 'https://knowngood.sh/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  sh-knowngood-knowngood:
    url: "https://knowngood.sh/mcp"
```

### Netclaw

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

### Vellum

```bash
assistant mcp add sh-knowngood-knowngood -t streamable-http -u 'https://knowngood.sh/mcp'
```

### Other

```json
{
  "mcpServers": {
    "sh-knowngood-knowngood": {
      "type": "http",
      "url": "https://knowngood.sh/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-23 (score 78, +1)

- [cosmetic] “find_capability” reworded the description of “has_md”
- [cosmetic] “find_capability” reworded the description of “query”
- [cosmetic] “find_capability” made “query” optional

### 2026-09-21 (score 77, +1)

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

### 2026-09-19 (score 76, +1)

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

### 2026-09-17 (score 75, +1)

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

### 2026-09-14 (score 74, +1)

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

### 2026-09-12 (score 73, +1)

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

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

## MCP tools (3)

### `check_webmcp` (~138 tokens)

Check a website LIVE for WebMCP tools, and where a browser is available whether any tool actually registers when the page runs. Returns one of: registered, declared_only, declared, not_declared, could_not_ask, or excluded when the site's robots.txt refuses AI input. could_not_ask is a distinct answer and is never reported as a no. Tools are listed, never called. Reads only the site named plus published population figures — it does not consult the index, and running it changes no ranking or listing.

Input parameters:

- `url` (string, required): The site to check. A hostname or a full URL; https is assumed.

### `find_capability` (~373 tokens)

Find websites where an agent can accomplish a task. Returns probe-verified agent-readiness signals, unverified apparent actions read from page content, the verification tier, how each site was found (it declared agent access, probe discovery, or it was submitted), and a report URL to cite. Returns count:0 with an empty_note when nothing in the index matches — never a nearest guess.

Input parameters:

- `country` (string): ISO 3166-1 alpha-2, e.g. GB
- `entity_type` (string)
- `has_endpoint` (boolean): Only sites with a verified endpoint surface (working MCP server or API catalog).
- `has_mcp` (boolean): Only sites whose MCP server answered tools/list when we tested; results include the tool names
- `has_md` (boolean): Only sites with verified markdown: negotiation that passed the strict re-grade (the body is markdown and differs from the HTML), or a .md twin. Omit both class flags for the whole index — the default.
- `has_webmcp` (boolean): Only sites whose in-page WebMCP tools were RUNTIME-VERIFIED: the page was executed in a headless browser with a modelContext supplied, and it registered at least one tool. Source-only hosts — the reg…
- `limit` (integer)
- `query` (string): What you are trying to do, in plain language. Optional when at least one filter is set: with no query the tool lists every listed site matching the filters, in a fixed published order, with `total`.
- `transactional` (boolean): Only sites where an agent can act, not just read

### `get_site_report` (~117 tokens)

Fetch Known Good's dated verification report for one listed website: which capabilities were tested, which passed, when it was probed, what an agent can apparently do there, and how the site was found: whether it declared agent access, came from probe discovery, or was submitted. Answers "is this specific host agent-ready?". Returns found:false for anything not in the index — it never guesses a nearest match. Cite the report URL and its date.

Input parameters:

- `host` (string, required): The site's hostname or URL, e.g. example.com

## Diagnostics

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

## Score history

- 2026-09-24: 78
- 2026-09-23: 78
- 2026-09-22: 77
- 2026-09-21: 77
- 2026-09-20: 76
- 2026-09-19: 76
- 2026-09-18: 75
- 2026-09-17: 75
- 2026-09-16: 74
- 2026-09-15: 74
- 2026-09-14: 74
- 2026-09-13: 73
- 2026-09-12: 73
- 2026-09-11: 72
- 2026-09-10: 72
- 2026-09-09: 71
- 2026-09-08: 71
- 2026-09-07: 70
- 2026-09-06: 70
- 2026-09-05: 69
- 2026-09-04: 69
- 2026-09-03: 68
- 2026-09-02: 68
- 2026-09-01: 67
- 2026-08-31: 67
- 2026-08-30: 60
- 2026-08-29: 58
- 2026-08-28: 58
- 2026-08-27: 58

## Common questions

### What is the sh.knowngood/knowngood MCP server?

sh.knowngood/knowngood is an MCP server listed in the public MCP registry as sh.knowngood/knowngood. Search agent-ready sites or fetch one site's report; every capability probe-verified, dated. This page covers its hosted endpoint (https://knowngood.sh/mcp).

### Is the sh.knowngood/knowngood MCP server safe to use?

sh.knowngood/knowngood scores 78 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 sh.knowngood/knowngood MCP server expose?

sh.knowngood/knowngood exposes 3 tools: check_webmcp, find_capability, get_site_report. Their descriptions and schemas cost roughly 628 tokens of context every time the server is loaded.

### Does the sh.knowngood/knowngood MCP server require authentication?

No. We connected to sh.knowngood/knowngood without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the sh.knowngood/knowngood MCP server still maintained?

sh.knowngood/knowngood is still listed as active in the MCP registry. We last reached this channel on 24 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://knowngood.sh/mcp
- Website: https://knowngood.sh/
- Changelog RSS feed: https://verifymcp.io/servers/sh-knowngood-knowngood/knowngood.xml
- Changelog JSON feed: https://verifymcp.io/servers/sh-knowngood-knowngood/knowngood.json
- HTML version of this page: https://verifymcp.io/servers/sh-knowngood-knowngood/knowngood