
A small MCP server that lets an AI client read ProtocolProbe's public facts about servers in the
A small MCP server that lets an AI client read ProtocolProbe's public facts about servers in the official MCP registry. It has four tools. It reads the public ProtocolProbe API (https://protocolprobe.com/api/v1) and nothing else.
·
A small MCP server that lets an AI client read ProtocolProbe's public facts about servers in the official MCP registry. It has four tools. It reads the public ProtocolProbe API (https://protocolprobe.com/api/v1) and nothing else.
The facts are read from public records (the registry, npm or PyPI, GitHub) on the dates the answers show. They are facts, not a rating.
Needs Node 18 or newer. Add this to your MCP client's server list (the standard mcpServers form):
{
"mcpServers": {
"protocolprobe": {
"command": "npx",
"args": ["-y", "protocolprobe-mcp"]
}
}
}Where that list lives differs from client to client. Look it up in your client's own documentation.
All four are read-only and return one text block of JSON. On any failure they return an error sentence and do not throw.
| Tool | Input | Returns |
|---|---|---|
get_record_checks | namespace, name (the exact registry name, for example io.github.example and my-server) | The nine record checks for one server: each check's state (met, not met, does not apply, not checked), a short detail and, when the API gives one, a help object (kind, text and a link to the official documentation). Also the server page, the version and the date checked. |
list_servers_by_topic | topic (optional), page (1 to 200, default 1), limit (1 to 100, default 50) | Exact server names for a topic, in name order. Also the total number of matching servers and the number of pages. |
get_registry_summary | none | How many servers ProtocolProbe holds, the registry snapshot date, when the data was generated, the topics with their counts, and, when the API provides it, how many entries have at least one record check not met (otherwise an explicit unavailable marker). |
get_recent_registry_changes | days (1 to 10, default 3) | Counts of what changed in the registry list on each of the latest days, with the registry totals. Counts only, no free text. |
list_servers_by_topic to find a name, then get_record_checks.limit only shortens what you get back from one page. hasMore comes from the API's own page count.truncated: true).Retry-After (at most 10 seconds) or 1 s then 3 s. If the API still says 429, the tool returns an error sentence; try again later.listChanged: false).PROTOCOLPROBE_API can replace the API address only with an https://protocolprobe.com... address (or a localhost address for tests). Anything else stops the server at start.The server names, topics and pages you ask about are sent to protocolprobe.com, as ordinary HTTPS requests with the user agent protocolprobe-mcp/<version>. Nothing else is sent: no key, no account, no telemetry, no files.
The privacy page says that our network provider (Cloudflare) and our host (Vercel) process your IP address and browser details to deliver pages and protect against abuse. It does not describe API requests separately. Read it before you use this package.
The data is under CC BY 4.0. Attribution line:
ProtocolProbe (https://protocolprobe.com), CC BY 4.0: credit it with a link to the server page and the date checked
Every answer carries this line. Text that ProtocolProbe quotes from others (for example a publisher's description) is not ours to license; the API's licence notice lists what is excluded: https://protocolprobe.com/api/v1/meta.
Record checks count what public records say on a given date. They are not a security rating, they do not say a server is good or bad, and "not met" means only that the record does not show it. Method: https://protocolprobe.com/docs/record-checks
Version 0.1.1. The facts in this README (tool names, inputs, limits, the privacy page and the repository address) were checked on 2026-11-03.
Issues and questions: https://github.com/protocolprobe/protocolprobe-tools/issues (this package is the mcp/ folder of https://github.com/protocolprobe/protocolprobe-tools).
Pick your client and paste the snippet. Each one is the same server, written the way that client expects it.
claude mcp add protocolprobe -- npx -y protocolprobe-mcp{
"mcpServers": {
"protocolprobe": {
"args": [
"-y",
"protocolprobe-mcp"
],
"command": "npx"
}
}
}code --add-mcp '{"name":"protocolprobe","args":["-y","protocolprobe-mcp"],"command":"npx"}'[mcp_servers.protocolprobe]
command = "npx"
args = ["-y", "protocolprobe-mcp"]Runs locally on your device. Your client starts the server itself, so nothing has to be hosted.
Paste this prompt into your agent. It reads this page and does the setup for you.
Read https://aiagentslisting.com/mcp/mcp-12 to learn what the "Mcp" MCP server does and how to install it. Add it to my coding agent's MCP configuration as documented on that page, then confirm the server connects and list the tools it exposes.Agents can also browse this directory over MCP at https://aiagentslisting.com/api/mcp
| Name | What it does |
|---|---|
get_record_checks | 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 |
list_servers_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 |
get_registry_summary | 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_ser |
get_recent_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. Co |
Read live from the server on November 9, 2026.
Maintain this server? Claiming proves you own the listing and earns the last 4 points.
Claim this listingPaste this line near the top of your repository's README. The badge always renders the current score.
[](https://aiagentslisting.com/mcp/mcp-12)Nothing comparable is listed yet.
mcp-v0.1.0protocolprobe-mcp 0.1.0Release notesConnect to the AI Agents Listing MCP server at https://aiagentslisting.com/api/mcp using the HTTP transport and complete the sign-in when it asks. Then call the submit_review tool for the listing "mcp-12" with a rating from 1 to 5 and a short note on what worked and what did not.No reviews yet
Be the first to share your experience with this tool.
One email a week. New agents, MCP servers and skills, and what is actually getting traction.