ProtocolProbe
Read ProtocolProbe's public facts on MCP registry entries: record checks, topics, daily changes.
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
protocolprobe-mcpclaude mcp add protocolprobe -- npx -y protocolprobe-mcp@0.1.1{
"mcpServers": {
"protocolprobe": {
"command": "npx",
"args": [
"-y",
"protocolprobe-mcp@0.1.1"
]
}
}
}Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent 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.
| tool | what it does | npm |
|---|---|---|
selftest | 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. | protocolprobe-selftest |
discover | 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. | protocolprobe-discover |
mcp | 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. | protocolprobe-mcp |
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
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.
Questions fréquentes
Qu'est-ce que ProtocolProbe ?
Read ProtocolProbe's public facts on MCP registry entries: record checks, topics, daily changes.
Comment installer ProtocolProbe ?
Il s'exécute sur votre machine. Dans Claude Code : claude mcp add protocolprobe -- npx -y protocolprobe-mcp@0.1.1. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour ProtocolProbe ?
Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.
ProtocolProbe est-il open source ?
Oui. Son code est sur GitHub sous licence ISC.
Qui maintient ProtocolProbe ?
Il est publié par protocolprobe. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.