English Français العربية

ProtocolProbe

Official registry Other

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

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package protocolprobe-mcp
Claude Code 
claude mcp add protocolprobe -- npx -y protocolprobe-mcp@0.1.1
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "protocolprobe": {
            "command": "npx",
            "args": [
                "-y",
                "protocolprobe-mcp@0.1.1"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

ProtocolProbe tools

Three small tools from ProtocolProbe, a directory of dated facts about MCP (Model Context Protocol) servers, with tools for the people who run them. The first two run on your own machine and send nothing to ProtocolProbe; the third is an MCP server that reads ProtocolProbe's public API. All three are published on npm under the ISC licence.

toolwhat it doesnpm
selftestRuns ProtocolProbe's MCP security checks against an MCP server you run: a local stdio server, or your own Streamable HTTP server after it proves you control that exact URL. Results stay on your machine.protocolprobe-selftest
discoverLists the MCP servers configured on this machine and, offline, which ones are in the official MCP registry. Reads config files only, sends nothing anywhere, never prints secrets.protocolprobe-discover
mcpA read-only MCP server over ProtocolProbe's public API, for an AI client: the nine record checks of a registry server, server names by topic, the registry size and the daily registry changes. No key. The names you ask about are sent to protocolprobe.com. Facts from public records, not a rating.protocolprobe-mcp
npx protocolprobe-discover
npx protocolprobe-selftest --i-own-this-server --stdio node ./dist/server.js

The MCP server is added to an MCP client's server list (where that list lives depends on the client):

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

Read each tool's own README before running it. selftest is dual-use (two of its checks are off unless you turn them on) and only for servers you own: see selftest/DISCLOSURE.

Questions, ideas, problems

  • Questions and ideas: Discussions
  • A bug or a wrong result: open an issue (say the tool, its version, your Node version and what you ran; never paste tokens, keys or the one-time proof value)
  • A security problem in these tools: see SECURITY.md

About this repository

This repository holds the published source of the three tools, copied from ProtocolProbe's main (private) repository at each release. The tools' tests live with the rest of the engine there, so they are not in this copy. Pull requests are welcome; a change accepted here is carried back by the maintainers.

The directory, the data and the research behind it are at protocolprobe.com.

Frequently asked questions

What is ProtocolProbe?

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

How do I install ProtocolProbe?

It runs on your machine. In Claude Code: claude mcp add protocolprobe -- npx -y protocolprobe-mcp@0.1.1. For other clients, paste the JSON configuration from this page into their MCP settings.

Does ProtocolProbe need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is ProtocolProbe open source?

Yes. Its code is on GitHub under the ISC license.

Who maintains ProtocolProbe?

It is published by protocolprobe. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.