Licensed local MCP server for deterministic review cards from supplied MCP tools/list snapshots.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mcp-tool-approval-change-card-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# MCP Tool Approval Change Card Compare two user-supplied local MCP `tools/list` JSON snapshots and create deterministic review cards. The tool reports advertised descriptor changes; it does not connect to a server, call listed tools, approve access, or prove that runtime behavior stayed the same. ## Requirements - Windows 11 with Python 3.11–3.14 - An MCP-compatible client that can launch a local stdio server - `MCP_LICENSE_KEY` from this MCP Marketplace purchase - Internet access for initial and periodic license verification The marketplace license check transmits only the buyer's license key and this product's public slug. Buyer snapshots, paths, and generated reports remain local. Apart from license verification, the package performs no network call or telemetry. The license SDK may use a previously verified local cache if its service is unavailable; revocation may therefore take effect later. ## Install ```powershell python -m pip install mcp-tool-approval-change-card-mcp==0.2.0 mcp-approval-card --json doctor ``` Place `MCP_LICENSE_KEY` in your MCP client's environment configuration. For a client using `mcpServers`: ```json { "mcpServers": { "mcp-tool-approval-card": { "command": "mcp-approval-card-mcp", "env": {"MCP_LICENSE_KEY": "PASTE_THE_KEY_FROM_YOUR_PURCHASE"} } } } ``` Launch the client with its working directory set to the folder containing the two buyer-authorized JSON snapshots. The one MCP tool is `make_change_cards(previous, current, output_directory)`. Use relative paths and a **new** output directory. Do not place real credentials in snapshots. For a first local check, save these two synthetic files in the client's working directory: `previous.json` ```json {"tools":[{"name":"lookup","description":"Search local index","inputSchema":{"type":"object"}}]} ``` `current.json` ```json {"tools":[{"name":"lookup","description":"Search updated local index","inputSchema":{"type":"object"}}]} ``` Then pass `previous.j…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.