sh.knowngood/knowngood
REMOTE · KNOWNGOOD.SH · SCANNED SEP 24
Search agent-ready sites or fetch one site's report; every capability probe-verified, dated.
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 Security66
- 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 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. 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · knowngood.sh
claude mcp add --transport http sh-knowngood-knowngood 'https://knowngood.sh/mcp'
{
"mcpServers": {
"sh-knowngood-knowngood": {
"url": "https://knowngood.sh/mcp"
}
}
} {
"servers": {
"sh-knowngood-knowngood": {
"type": "http",
"url": "https://knowngood.sh/mcp"
}
}
} [mcp_servers.sh-knowngood-knowngood] url = "https://knowngood.sh/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sh-knowngood-knowngood": {
"type": "remote",
"url": "https://knowngood.sh/mcp",
"enabled": true
}
}
} openclaw mcp add sh-knowngood-knowngood --url 'https://knowngood.sh/mcp' --transport streamable-http
mcp_servers:
sh-knowngood-knowngood:
url: "https://knowngood.sh/mcp" {
"McpServers": {
"sh-knowngood-knowngood": {
"Transport": "http",
"Url": "https://knowngood.sh/mcp"
}
}
} assistant mcp add sh-knowngood-knowngood -t streamable-http -u 'https://knowngood.sh/mcp'
{
"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.
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.
- 23 Sept 26 +1
- “find_capability” reworded the description of “has_md” cosmetic
- “find_capability” reworded the description of “query” cosmetic
- “find_capability” made “query” optional cosmetic
3 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 21 Sept 26 +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.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 14 Sept 26 +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.
- 12 Sept 26 +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.
- 10 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.
- 8 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.
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 24 Sept 2026 · Probed https://knowngood.sh/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=knowngood.sh | CN=WE1,O=Google Trust Services,C=US | 24 Aug 2026 | 22 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 56afa75f886532f81308303bfe2c2d35 |
| SANs: knowngood.sh, *.knowngood.sh | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of knowngood.sh. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| sh. | present | 55297 | 8 | Verified |
| knowngood.sh. | present | 2371 | 13 | Verified |
| knowngood.sh. | Verified address RRset verified with the apex keys |
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=86400 |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://knowngood.sh/mcp | Verified | 200 | |
| http (plaintext) | http://knowngood.sh/mcp | HTTPS enforced | 301 | https://knowngood.sh/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_webmcp ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The site to check. A hostname or a full URL; https is assumed. |
No output schema declared.
No examples provided.
find_capability ~373
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
get_site_report ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | The site's hostname or URL, e.g. example.com |
No output schema declared.
No examples provided.
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.