Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ProtocolProbe

NPM · PROTOCOLPROBE-MCP

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

Available components

+3 this week 77 Trust /100

Last scanned (20 hours ago)

Scores higher than 56% of npm servers

Category Search and Retrieval

Trust breakdown (7 categories)

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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • 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 (ISC).Pass
  • Actively maintained (last published 15 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +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.

  • 18 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.

  • 16 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.

  • 14 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.

  • 12 Nov 26 +1
    • Security disclosure: unverified → pass ▲ functional
  • 11 Nov 26 0
    • Security disclosure: pass → unverified ▼ functional
  • 10 Nov 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.

  • 7 Nov 26 +1
    • Stability: unverified → 0.07 ▲ functional
Diagnostics

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 21 Nov 2026 · Analysed npm/protocolprobe-mcp@0.1.1

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 →

Dependencies 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~523 tokens

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 →

Tool Tokens
get_recent_registry_changes ~108

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.

NameTypeReqDescription
daysinteger–How many of the latest days to return, 1 to 10, default 3

No output schema declared.

No examples provided.

get_record_checks ~167

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.

NameTypeReqDescription
namestringyesServer name, the part after the slash
namespacestringyesRegistry namespace, the part of the server name before the slash, for example io.github.example

No output schema declared.

No examples provided.

get_registry_summary ~86

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_servers_by_topic ~162

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.

NameTypeReqDescription
limitinteger–How many names of the page to return, 1 to 100, default 50
pageinteger–Page of 500 names, 1 to 200, default 1
topicstring–Topic name from get_registry_summary, for example developer-tools; omit for all servers

No output schema declared.

No examples provided.

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.

npm · protocolprobe-mcp

# add to Claude Code
claude mcp add com-protocolprobe-protocolprobe-mcp -- npx -y protocolprobe-mcp
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.