io.github.H129hj/checkmcp
PYPI · AUDIT-MCP
Audit any MCP server's security & quality — OWASP MCP Top 10 + explainable 0-100 MCP Score
Available components
Last scanned (1 hour ago)
Scores higher than 96% of PyPI servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to H129hj/checkmcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 86 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 219 tokens (~219/item across 1 items; 1 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
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.
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 30 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 0
- Stability: 0.97 → pass security
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 −1
- Stability: pass → 0.93 functional
- 16 Oct 26 0
- Stability: 0.97 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 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 5 Nov 2026 · Analysed pypi/audit-mcp@0.5.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | H129hj/checkmcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/H129hj/checkmcp/.github/workflows/publish-pypi.yml@refs/tags/v0.5.0 |
| Rekor log index | 2071326109 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:edcc80a67986f56b640e07f47efad19716b7640811833ca3fa84427026730f55 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
audit_mcp_server Audit an MCP server (MCP Score) ~181
Audit a remote MCP server and return its MCP Score (0-100, grade A-F) with the findings that explain it. Probes the live endpoint (streamable-http or SSE), runs an OWASP MCP Top 10 security pass (tool poisoning, hardcoded secrets in schemas, command injection, the lethal trifecta) plus tool-design, schema, reliability, context-cost and compliance checks. Read-only: it never invokes the target's tools. Call this when the user asks whether an MCP server is safe or well built, before recommending or adding a server to a client config, or to compare two servers (call once per server).
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | – | Optional Bearer token if the target server requires authentication. |
| url | string | yes | The MCP endpoint URL to audit, e.g. https://mcp.example.com/mcp |
No output schema declared.
No examples provided.
How do I install the io.github.H129hj/checkmcp MCP server?
io.github.H129hj/checkmcp runs locally as a PyPI package, launched with uvx audit-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · audit-mcp
claude mcp add h129hj-checkmcp -- uvx audit-mcp
What is the io.github.H129hj/checkmcp MCP server?
io.github.H129hj/checkmcp is an MCP server listed in the public MCP registry as io.github.H129hj/checkmcp. Audit any MCP server's security & quality, OWASP MCP Top 10 + explainable 0-100 MCP Score. This page covers its PyPI package (audit-mcp).
Is the io.github.H129hj/checkmcp MCP server safe to use?
io.github.H129hj/checkmcp scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 io.github.H129hj/checkmcp MCP server expose?
io.github.H129hj/checkmcp exposes 1 tool: audit_mcp_server. Their descriptions and schemas cost roughly 181 tokens of context every time the server is loaded.
Is the io.github.H129hj/checkmcp MCP server still maintained?
io.github.H129hj/checkmcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.H129hj/checkmcp MCP server under?
io.github.H129hj/checkmcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.