# ProtocolProbe (npm · protocolprobe-mcp)

Read ProtocolProbe's public facts on MCP registry entries: record checks, topics, daily changes.

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

## Components

- npm · `protocolprobe-mcp`: 77/100 (this document), [markdown](https://verifymcp.io/servers/com-protocolprobe-protocolprobe-mcp/protocolprobe-mcp.md), [page](https://verifymcp.io/servers/com-protocolprobe-protocolprobe-mcp/protocolprobe-mcp)

## Channel facts

- Registry: `npm`
- Package: `protocolprobe-mcp`
- Version: `0.1.1`
- 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-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (ISC).
  - Actively maintained (last published 15 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 605 tokens (~151/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 ProtocolProbe MCP server?

ProtocolProbe runs locally as an npm package, launched with npx -y protocolprobe-mcp. 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 com-protocolprobe-protocolprobe-mcp -- npx -y protocolprobe-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-protocolprobe-protocolprobe-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "protocolprobe-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-protocolprobe-protocolprobe-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "protocolprobe-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-protocolprobe-protocolprobe-mcp -- npx -y protocolprobe-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-protocolprobe-protocolprobe-mcp --command npx --arg -y --arg protocolprobe-mcp
```

### Hermes

```yaml
mcp_servers:
  com-protocolprobe-protocolprobe-mcp:
    command: "npx"
    args: ["-y", "protocolprobe-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-protocolprobe-protocolprobe-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "protocolprobe-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-protocolprobe-protocolprobe-mcp -t stdio -c npx -a -y protocolprobe-mcp
```

### Other

```json
{
  "mcpServers": {
    "com-protocolprobe-protocolprobe-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "protocolprobe-mcp"
      ]
    }
  }
}
```

## 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-20 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 76, +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-16 (score 75, +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-14 (score 74, +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-11-12 (score 73, +1)

- [functional improvement] Security disclosure: unverified → pass

### 2026-11-11 (score 72, 0)

- [functional regression] Security disclosure: pass → unverified

### 2026-11-10 (score 72, +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-11-07 (score 71, +1)

- [functional improvement] Stability: unverified → 0.07

## MCP tools (4)

### `get_record_checks` (~167 tokens)

Record checks of one registry server

Returns the nine record checks ProtocolProbe read for one MCP server listed in the official MCP registry: for each check its state (met, not-met, not-applicable, not-checked), a short detail and, when the API gives one, a help object (kind, text, and a documentation link). Data comes from public records (the registry, npm or PyPI, GitHub) on the dates in asOf. It is not a security rating. The registry name must be exact: namespace and name as the registry lists them, for example io.github.example and my-server.

Input parameters:

- `name` (string, required): Server name, the part after the slash
- `namespace` (string, required): Registry namespace, the part of the server name before the slash, for example io.github.example

### `list_servers_by_topic` (~162 tokens)

Registry server names by topic

Lists the exact names of MCP registry servers ProtocolProbe holds, optionally for one topic, in name order. The API pages are 500 names; use page to move on and limit (1 to 100, default 50) to shorten the answer. The names are what get_record_checks needs. Valid topics are listed by get_registry_summary. These are facts read from public records, not a security rating.

Input parameters:

- `limit` (integer): How many names of the page to return, 1 to 100, default 50
- `page` (integer): Page of 500 names, 1 to 200, default 1
- `topic` (string): Topic name from get_registry_summary, for example developer-tools; omit for all servers

### `get_registry_summary` (~86 tokens)

Registry size, snapshot date and topics

Returns how many servers ProtocolProbe holds from the official MCP registry, the registry snapshot date, when the data was generated, the topics with their server counts (the valid values for list_servers_by_topic) and, when the API provides it, how many entries have at least one record check not met (otherwise an explicit unavailable marker). Counted from public records; not a security rating.

### `get_recent_registry_changes` (~108 tokens)

Recent daily registry changes

Returns the counts of what changed in the official MCP registry list on each of the latest days (new servers, new versions, no longer listed, listed again, status changed) with the registry totals. Counts only: no names and no free text. days is 1 to 10, default 3. Source: ProtocolProbe's daily pull of the registry.

Input parameters:

- `days` (integer): How many of the latest days to return, 1 to 10, default 3

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-protocolprobe-protocolprobe-mcp/protocolprobe-mcp#diagnostics

## Score history

- 2026-11-21: 77
- 2026-11-20: 77
- 2026-11-19: 76
- 2026-11-18: 76
- 2026-11-17: 75
- 2026-11-16: 75
- 2026-11-15: 74
- 2026-11-14: 74
- 2026-11-13: 73
- 2026-11-12: 73
- 2026-11-11: 72
- 2026-11-10: 72
- 2026-11-09: 71
- 2026-11-08: 71
- 2026-11-07: 71
- 2026-11-06: 70
- 2026-11-05: 55

## Common questions

### What is the ProtocolProbe MCP server?

ProtocolProbe is an MCP server listed in the public MCP registry as com.protocolprobe/protocolprobe-mcp. Read ProtocolProbe's public facts on MCP registry entries: record checks, topics, daily changes. This page covers its npm package (protocolprobe-mcp).

### Is the ProtocolProbe MCP server safe to use?

ProtocolProbe scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 ProtocolProbe MCP server expose?

ProtocolProbe exposes 4 tools: get_record_checks, list_servers_by_topic, get_registry_summary, get_recent_registry_changes. Their descriptions and schemas cost roughly 523 tokens of context every time the server is loaded.

### Is the ProtocolProbe MCP server still maintained?

ProtocolProbe is still listed as active in the MCP registry. We last reached this channel on 21 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 ProtocolProbe MCP server under?

ProtocolProbe declares the ISC licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the ProtocolProbe MCP server?

VerifyMCP ran 16 checks on ProtocolProbe, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/protocolprobe-mcp
- Socket report: https://socket.dev/npm/package/protocolprobe-mcp
- Repository: https://github.com/protocolprobe/protocolprobe-tools
- Website: https://protocolprobe.com/docs/api
- Changelog RSS feed: https://verifymcp.io/servers/com-protocolprobe-protocolprobe-mcp/protocolprobe-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-protocolprobe-protocolprobe-mcp/protocolprobe-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-protocolprobe-protocolprobe-mcp/protocolprobe-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-protocolprobe-protocolprobe-mcp/protocolprobe-mcp
