protocolprobe-mcp
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
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.
tool | what it does | npm |
Runs 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. | ||
Lists 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. | ||
A 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. |
npx protocolprobe-discover
npx protocolprobe-selftest --i-own-this-server --stdio node ./dist/server.jsThe 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
Related MCP server: sealchat-agent-mcp
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.
This server cannot be deployed
Maintenance
Related MCP Connectors
Read-only MCP server for The Quiet Protocol's engines, benchmarks, proof, and business data.
Trending/new/changed MCP servers: a liveness-probed freshness index + x402-paid change-data API
Trust, freshness, policy, and discovery layer for public MCP servers.
Independent trust scores, tool surfaces and change history for MCP servers.
Related MCP Servers
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server that provides tools to query the official MCP Registry.440 npm3MIT
- AlicenseNot gradedqualityDmaintenanceRead-only MCP server that provides tools to fetch SealChat public protocol docs, manifest, channel counts, and chat messages via the HTTP Agent API, without write access or database access.MIT
- AlicenseAqualityDmaintenanceRead-only MCP server exposing a W3C PROV knowledge graph of verified facts with provenance, enabling AI agents to list, search, and check facts while enforcing that writes remain CLI-only.5MIT
- AlicenseNot gradedqualityFmaintenanceRead-only MCP server exposing one Muninn Minecraft backend's capabilities via safe, capability-aware tools. Broadly covers server status, CoreProtect lookups, Paper, CMI, and WorldGuard queries.MIT