io.github.CloudCorpRecords/mcpaudit
NPM · @RENETURCIOS/MCPAUDIT · 2 COMPONENTS
Audit any MCP server: handshake, schemas, descriptions, error handling, scored.
Available components
Last scanned (2 hours ago)
Scores higher than 40% of npm servers
Category Developer Tools
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 9 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 337 tokens (~112/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 26 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.10 ▲ functional
- Package version: 0.1.1 → 0.1.2 functional
- 24 Oct 26 +21
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: unverified → fail ▼ security
- Malware scan: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ functional
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 npm/@reneturcios/mcpaudit@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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_config ~110
Audit every server in an MCP client config file (Claude/Cursor style: {"mcpServers": {name: {command, args}}}) or a single named entry. Each server is launched and audited like audit_server. Returns one scored report per server.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Path to the config JSON file, on the machine running this server |
| server | string | – | Only audit this named entry |
| timeoutMs | number | – | Per-step timeout in milliseconds, default 60000 |
No output schema declared.
No examples provided.
audit_server ~151
Audit an MCP server by launching it over stdio: initialize handshake, protocol version, server info, tools/list quality (names, descriptions, inputSchema validity, undescribed parameters), response times, and error handling on a deliberately bad tool call. Returns a scored report (0-100) with named, evidence-backed issues.
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | – | Command arguments, e.g. ["-y", "@reneturcios/shipcheck", "mcp"] |
| command | string | yes | Server launch command, e.g. npx or node |
| env | object | – | Extra environment variables for the server process |
| timeoutMs | number | – | Per-step timeout in milliseconds, default 60000 |
No output schema declared.
No examples provided.
audit_tools ~76
Offline audit of a tools/list array (no server launched): validates tool names, descriptions, inputSchema shape, required-vs-properties consistency, and duplicate names. Returns a scored report.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | – | Label for the report target |
| tools | array | yes | The tools array exactly as a server returned it from tools/list |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/mcpaudit MCP server?
io.github.CloudCorpRecords/mcpaudit runs locally as an npm package, launched with npx -y @reneturcios/mcpaudit. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/mcpaudit
claude mcp add cloudcorprecords-mcpaudit -- npx -y @reneturcios/mcpaudit
What is the io.github.CloudCorpRecords/mcpaudit MCP server?
io.github.CloudCorpRecords/mcpaudit is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/mcpaudit. Audit any MCP server: handshake, schemas, descriptions, error handling, scored. This page covers its npm package (@reneturcios/mcpaudit).
Is the io.github.CloudCorpRecords/mcpaudit MCP server safe to use?
io.github.CloudCorpRecords/mcpaudit scores 71 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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.CloudCorpRecords/mcpaudit MCP server expose?
io.github.CloudCorpRecords/mcpaudit exposes 3 tools: audit_server, audit_config, audit_tools. Their descriptions and schemas cost roughly 337 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/mcpaudit MCP server still maintained?
io.github.CloudCorpRecords/mcpaudit 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.CloudCorpRecords/mcpaudit MCP server under?
io.github.CloudCorpRecords/mcpaudit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.