Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
MCP security trust layer: scan packages, inspect repos, check exposure, monitor changes.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"agentscore": {
"command": "npx",
"args": [
"-y",
"@agentscore-xyz/mcp-server"
]
}
}
}在终端中运行这条命令
claude mcp add agentscore -- npx -y @agentscore-xyz/mcp-server粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"agentscore": {
"command": "npx",
"args": [
"-y",
"@agentscore-xyz/mcp-server"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"agentscore": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@agentscore-xyz/mcp-server"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 Thezenmonster 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(2.2.0)于7个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Rystic
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ 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.
Start, seed, clock, inspect and diff Rystic API simulators from your agent.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
MCP security trust layer. Scan packages, get trust verdicts, inspect repo-wide MCP dependencies, generate Policy Gate setup, install the CI workflow directly, check incident exposure, and query the abuse database. Eight tools for MCP security decisions. No API key, zero config.
Scan any MCP package for security issues: agentscores.xyz
Add to your claude_desktop_config.json:
{
"mcpServers": { "agentscore": { "command": "npx", "args": ["-y", "@agentscore-xyz/mcp-server"] } } }
npx @agentscore-xyz/mcp-server
Your AI can now make security decisions about MCP packages:
You: "Is exa-mcp-server safe to install?"
Claude: *calls get_verdict* "Verdict: ALLOW. Score 90/100, LOW risk. No provenance attestations (published by personal account). 9 tools exposed including web_search_exa and crawling_exa."
You: "The axios package was compromised. Which MCP servers are affected?"
Claude: *calls check_exposure* "Multiple monitored MCP servers depend on axios, including exa-mcp-server, tavily-mcp, and figma-mcp."
You: "Scan @azure-devops/mcp for security issues"
Claude: *calls scan_package* "Score 75/100, MODERATE risk. Found: preinstall script modifying npm registry config. No provenance attestations."
You: "Check this repo for MCP dependencies"
Claude: *calls check_my_repo* "MCP dependencies found: 5. Two are warnings. Run generate_policy_gate_setup to turn these checks into a CI gate."
You: "Set up AgentScore Policy Gate for this repo"
Claude: *calls install_policy_gate* "The workflow file is written to
.github/workflows/agentscore-policy-gate.yml. Commit and push. GitHub OIDC will auto-provision the repo on first run."
| Tool | What it does |
|---|---|
scan_package | Full security scan: install scripts, prompt injection, source code patterns, provenance posture, MCP tool extraction |
get_verdict | Trust decision: allow, warn, or block based on scan findings. Also reports monitoring status and publisher posture. |
check_my_repo | Inspect the current repo for MCP dependencies and summarise verdicts for every package detected locally. |
generate_policy_gate_setup | Generate the exact OIDC-based GitHub Actions workflow needed to enforce Policy Gate in CI. |
install_policy_gate | Write .github/workflows/agentscore-policy-gate.yml directly into the repo so the gate is ready to commit. |
check_exposure | Incident response: which monitored MCP servers depend on a given package? |
check_abuse | Query the KYA abuse database for reported packages or agents |
monitor_status | Check if a package is under continuous monitoring and get scan history |
The MCP server now bridges one-off package checks into the sticky product:
check_my_repo to see every MCP package used in a repo.generate_policy_gate_setup to preview the OIDC-based GitHub Actions workflow.install_policy_gate to write the workflow file directly into the repo.That turns "is this package safe?" into "this repo now enforces MCP dependency policy on every PR."
| Score | Risk | Meaning |
|---|---|---|
| 85-100 | LOW | Clean or minor issues only |
| 70-84 | MODERATE | Some findings, review recommended |
| 50-69 | ELEVATED | Significant findings, use with caution |
| 30-49 | HIGH | Serious issues, not recommended |
| 0-29 | CRITICAL | Do not use |
AgentScore continuously monitors hundreds of MCP packages. The check_exposure and monitor_status tools use this live dataset. When a package like axios gets compromised, you can instantly find which MCP servers are affected.
MIT