# io.github.CloudCorpRecords/mcpaudit (npm · @reneturcios/mcpaudit)

Audit any MCP server: handshake, schemas, descriptions, error handling, scored.

- Trust score: 71/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@reneturcios/mcpaudit`: 71/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-mcpaudit/reneturcios-mcpaudit.md), [page](https://verifymcp.io/servers/cloudcorprecords-mcpaudit/reneturcios-mcpaudit)
- oci · `ghcr.io/cloudcorprecords/mcpaudit`: 46/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-mcpaudit/ghcr-io-cloudcorprecords-mcpaudit.md), [page](https://verifymcp.io/servers/cloudcorprecords-mcpaudit/ghcr-io-cloudcorprecords-mcpaudit)

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/mcpaudit`
- Version: `0.1.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 9 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 337 tokens (~112/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

### Claude

```bash
claude mcp add cloudcorprecords-mcpaudit -- npx -y @reneturcios/mcpaudit
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-mcpaudit": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/mcpaudit"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-mcpaudit": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/mcpaudit"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-mcpaudit -- npx -y @reneturcios/mcpaudit
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-mcpaudit": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@reneturcios/mcpaudit"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloudcorprecords-mcpaudit --command npx --arg -y --arg @reneturcios/mcpaudit
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-mcpaudit:
    command: "npx"
    args: ["-y", "@reneturcios/mcpaudit"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-mcpaudit": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@reneturcios/mcpaudit"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloudcorprecords-mcpaudit -t stdio -c npx -a -y @reneturcios/mcpaudit
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-mcpaudit": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/mcpaudit"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 71, +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.

### 2026-11-03 (score 70, +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.

### 2026-11-01 (score 69, +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.

### 2026-10-30 (score 68, +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.

### 2026-10-28 (score 67, +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.

### 2026-10-27 (score 66, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-26 (score 51, −14)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.10
- [functional] Package version: 0.1.1 → 0.1.2

### 2026-10-24 (score 65, +21)

- [security regression] CVE-2023-54404 affects this package: high
- [security regression] Known CVEs: unverified → fail
- [security improvement] Malware scan: unverified → pass
- [functional improvement] Dependency health: unverified → 0.85

## MCP tools (3)

### `audit_server` (~151 tokens)

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.

Input parameters:

- `args` (array): Command arguments, e.g. ["-y", "@reneturcios/shipcheck", "mcp"]
- `command` (string, required): 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

### `audit_config` (~110 tokens)

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.

Input parameters:

- `path` (string, required): 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

### `audit_tools` (~76 tokens)

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.

Input parameters:

- `label` (string): Label for the report target
- `tools` (array, required): The tools array exactly as a server returned it from tools/list

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-mcpaudit/reneturcios-mcpaudit#diagnostics

## Score history

- 2026-11-05: 71
- 2026-11-04: 70
- 2026-11-03: 70
- 2026-11-02: 69
- 2026-11-01: 69
- 2026-10-31: 68
- 2026-10-30: 68
- 2026-10-29: 67
- 2026-10-28: 67
- 2026-10-27: 66
- 2026-10-26: 51
- 2026-10-25: 65
- 2026-10-24: 65
- 2026-10-23: 44

## Common questions

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

## Links

- npm package: https://www.npmjs.com/package/@reneturcios/mcpaudit
- Socket report: https://socket.dev/npm/package/@reneturcios/mcpaudit
- Repository: https://github.com/CloudCorpRecords/mcpaudit
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-mcpaudit/reneturcios-mcpaudit.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-mcpaudit/reneturcios-mcpaudit.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-mcpaudit/reneturcios-mcpaudit