Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Read ProtocolProbe's public facts on MCP registry entries: record checks, topics, daily changes.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"protocolprobe": {
"command": "npx",
"args": [
"-y",
"protocolprobe-mcp"
]
}
}
}在终端中运行这条命令
claude mcp add protocolprobe -- npx -y protocolprobe-mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"protocolprobe": {
"command": "npx",
"args": [
"-y",
"protocolprobe-mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"protocolprobe": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"protocolprobe-mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过域名 protocolprobe.com 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.1)于昨天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Intervals MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Remote MCP server for intervals.icu run data and analysis
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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/ . 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).