Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
The MCP server that vets MCP servers: identity, risk grade and per-tool risk before you install.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://api.policylayer.com/mcp在终端中运行这条命令
claude mcp add --transport http registry https://api.policylayer.com/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"registry": {
"url": "https://api.policylayer.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"registry": {
"type": "http",
"url": "https://api.policylayer.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://api.policylayer.com/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 policylayer.com 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.1)于4个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Signoff
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ 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.
Five gates that make an agent's 'done' provable: run them, read the verdict, audit the record.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
The MCP server that vets MCP servers.
Connect your agent to the PolicyLayer registry and it can ask one question before installing or allowing any MCP server: *is this safe?* The answer is the published registry record: verified identity with the evidence, an A to F risk grade, probed auth posture and every tool's risk classification.
https://api.policylayer.com/mcp (Streamable HTTP)Claude Code
claude mcp add --transport http policylayer https://api.policylayer.com/mcp
Claude (desktop / web)
Settings → Connectors → Add custom connector → URL https://api.policylayer.com/mcp
Cursor / Windsurf / VS Code
{ "mcpServers": {
"policylayer": { "url": "https://api.policylayer.com/mcp" } } }
Then tell your agent: *"check any MCP server against PolicyLayer before installing it."* Add it to your team's agent instructions and every install gets vetted.
| Tool | What it returns | Tier |
|---|---|---|
check_mcp_server | Full record for one server: identity + evidence, risk grade, posture, tools riskiest-first. Unknown servers are queued for scanning by the lookup itself. | Free |
search_registry | Published servers matching a name, slug or package substring, with grade and verification on every match. | Free |
check_tool | One tool's full classification: risk analysis and evidence, OWASP classes, parameters, recommended policy default. | Free |
get_change_events | The ordered change feed: drift, posture flips, impostor flags. Cursor-based, with severity filters. | Licence |
Ask your agent *"is the github MCP server safe to install?"* and it calls:
{ "name": "check_mcp_server", "arguments": { "server": "github" } }
and gets back the published record (trimmed):
{
"slug": "github", "riskGrade": "D", "identity": { "verification": "official", "confidence": "verified" }, "posture": { "auth": "gated", "rateLimited": false }, "toolCount": 86, "tools": [ { "name": "delete_file", "category": "Destructive", "severity": "High", "recommendedPolicy": { "action": "deny" } } ] }
get_change_events needs a Registry Licence key (plr_...), self-serve at policylayer.com/registry/pricing.
--header "Authorization: Bearer plr_..." to the command above"headers": { "Authorization": "Bearer plr_..." } inside the server entryEverything about a single server is free and complete: the full record, every tool, the whole classification. A Registry Licence adds breadth across the catalogue: the change feed above, plus bulk snapshots, keyset paging and webhooks on the /v1 API.
The connect kit for a hosted service. The server runs at api.policylayer.com; there is no code to run from here. server.json is the listing published to the official MCP Registry as com.policylayer/registry. The MIT licence covers the contents of this repository only; the hosted service and the registry data are licensed separately.