Skip to content

knowngood MCP server

sh.knowngood/knowngoodknowngood.shstreamable-httpv1.9.0Scanned

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

3 tools: 1 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 1 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

Anlyon alternative

1 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Its sign-in does not let Anlyon set up an OAuth client on its own, so there is no link to it here.

What the knowngood MCP server can do

The knowngood MCP server is published by knowngood.sh, a domain the MCP Registry verified. It has 3 tools. It can create or change data (1 tool: check_webmcp), but cannot delete data. 2 tools only read.

3 tools bring in text other people can write (check_webmcp, find_capability and get_site_report); 1 tool can send data out of your system (check_webmcp).

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 19, 2026, version 1.9.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.

3 tools

Changes things 1Claude Code: ask
  • check_webmcpCheck a website LIVE for WebMCP tools, and where a browser is available whether any tool actually registers when the page runs.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check a site for WebMCP tools
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • find_capabilityFind websites where an agent can accomplish a task.Reads text others writeNo findings

    Why it is in this group

    • The name "find_capability" says "find": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "find" and "website": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Find agent-ready websites
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_site_reportFetch 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 ho…Reads text others writeNo findings

    Why it is in this group

    • The name "get_site_report" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "fetch" and "website": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Fetch one site's verification report
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

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.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
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.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:18 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
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://knowngood.sh/.well-known/oauth-protected-resource
Authorization servers
https://knowngood.sh
Legacy HTTP+SSE transport
no
Dynamic client registration
no
Client ID metadata documents
no
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://knowngood.sh/mcp: tools/list returned 3 tools to an anonymous client, including check_webmcp (write)

    What this check looks for

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 1.9.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http knowngood https://knowngood.sh/mcp
claude mcp add --transport http knowngood https://knowngood.sh/mcp

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

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__knowngood__find_capability",
      "mcp__knowngood__get_site_report"
    ],
    "ask": [
      "mcp__knowngood__check_webmcp"
    ],
    "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 knowngood. Review it before you use it.

Capability tags behind 3 rules
  • mcp__knowngood__check_webmcp untrusted-input, outbound
  • mcp__knowngood__find_capability untrusted-input
  • mcp__knowngood__get_site_report 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/sh.knowngood/knowngood/verify?hash=efd836a1334dcfc43c011f3ba58152ac8dd571a16d755efdef7774ca9dd3029f" | jq -e '.changed == false'

Pinned hash efd836a1334d, from Nov 19, 2026, 04:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/sh.knowngood/knowngood/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for sh.knowngood/knowngood
[![Anlyon Radar](https://radar.anlyon.com/badge/sh.knowngood/knowngood.svg)](https://radar.anlyon.com/servers/sh.knowngood/knowngood)

Source: MCP Registry. Synced Oct 21, 2026, 18:54 UTC.

knowngood MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the knowngood MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 1 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 knowngood MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the knowngood 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 knowngood MCP server have?

3 tools: 1 write, 2 read. check_webmcp, find_capability and get_site_report.

Does the knowngood MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the knowngood MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_webmcp.

Has the knowngood MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.