R
rezearcher/greyridge-x402-tools
Vet an MCP server before your agent trusts it: static tool-poisoning / prompt-injection scan (OWASP…
无 SECURITY.md
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
安装与配置
客户端配置（取自该仓库的安装命令）
{
"mcpServers": {
"rezearcher-greyridge-x402-tools": {
"command": "npx",
"args": ["mcpscan"]
}
}
}解析自我们于 2026-10-26 抓取的该仓库 README；我们未执行过。
command/args 来自仓库写明的安装命令；不确定时请以该项目 README 为准。
VS Code（.vscode/mcp.json —— 键名是 servers）
{
"servers": {
"rezearcher-greyridge-x402-tools": {
"command": "npx",
"args": ["mcpscan"]
}
}
}VS Code 顶层键是 <code>servers</code>，其余与上面那份相同。
Claude Code（命令行）
claude mcp add --transport stdio rezearcher-greyridge-x402-tools -- npx mcpscan
Claude Code 不收 JSON 文件，用这条命令直接加。
配置项的键名以你的客户端为准：客户端与 CLI
- ★ 数取值
- 0 ★ · rezearcher/greyridge-x402-tools · 取自 GitHub 搜索 API · （2026-11-13 20:00:50 核对）
- 来源明细
- 从该仓库的 GitHub 页面直接读取 · 条目类型：开源项目
- 收录与活跃
- 收录于 2026-10-22 · 最近见到 2026-11-14 · 共见到 27 次 · 被 1 个来源列出
- 评分构成
- 综合分 103 · 1 个来源 · repo
- 安装
npx mcpscan
常见问题（答案都来自我们的记录）
怎么安装？
该仓库给出的安装命令是
npx mcpscan。我们的记录里它是仓库自己提供的；不保证在你的客户端上直接可用。它适合谁 / 用来做什么？
我们把它归在这些标签下: 开源项目。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
仓库
rezearcher/greyridge-x402-tools；我们收录于 2026-10-22；最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。# greyridge-x402-tools
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
Two safety gates for AI agents, backed by a keyless x402 API (USDC per call on Base, free previews, no account):
1. mcpscan — vet an MCP server's advertised tools for prompt-injection / tool-poisoning before your agent trusts it.
2. rugcheck / swap-gate — honeypot and pre-trade safety checks for Base tokens.
## mcpscan — vet an MCP server before your agent trusts it
Every tool an MCP server advertises runs inside your agent's context — its name, description and JSON schema are read by the model, so a poisoned or injection-laden tool can steer the agent before it ever calls anything. Scan any server in one command, no key:
npx mcpscan https://mcp.deepwiki.com/mcp
or pin a reproducible build straight from the release tag, no install:
npx -y github:rezearcher/greyridge-x402-tools#v0.3.1 mcpscan https://mcp.deepwiki.com/mcp
Prints tools scanned, issue counts by severity, risk score, and a verdict (clear / review / block). Exit code 2 on block, so it drops straight into CI as a gate before you wire a new server to an agent. Static analysis of advertised tool metadata only — it never invokes your tools. Checks cover OWASP LLM01/LLM08 patterns: hidden instructions, conceal-from-user directives, data-exfiltration hints, cross-tool shadowing, and invisible-unicode payloads. Itemized findings with evidence and OWASP mapping: paid /scan/mcp ($0.05 USDC, x402 on Base).
Scanning a private or local server (nothing leaves your machine except the tool list):
npx github:rezearcher/greyridge-x402-tools mcpscan --from-egress egress.json
### Offline — audit an mcp-egress run with no network
If you already record a server with mcp-egress, score its egress.json fully offline — nothing leaves the machine:
bash
mcp-egress run --calls calls.json --out egress.json -- uvx some-mcp-server
npx -y github:rezearcher/greyridge-x402-tools#v0.3.1 mcpscan --from-egress egress.json # reads .tools[], exits 2 on block
Reads the recorded .tools[] (name/title/description/annotations) and applies the same tool-poisoning rules locally — no second connection to the server, no payment. Exit 0 clear / 1 review / 2 block. The one-liner is pinned to the v0.3.1 release tag so a CI admission gate gets a fixed, reproducible artifact.
### Continuous monitoring — catch a server that turns hostile after you trust it
A one-time scan tells you a server is clean today. The real supply-chain risk is a server you already trust quietly changing its tool definitions later — a rug-pull on an approved dependency. Grey Ridge monitors your servers on a schedule and alerts you when a tool's description, schema or risk verdict changes:
$9.99/mo — continuous monitoring with drift alerts, full itemized findings, and OWASP LLM01/LLM08 mapping for every server you track: https://x402-data-api.sigrunner.workers.dev/pricing
The CLI and Action above stay free forever for point-in-time scans.
### Badge for your MCP server's README
Live shields.io badge showing the scan verdict for any public MCP server (free, cached 6h):
markdown
Replace YOURMCPURL with your URL-encoded server endpoint (e.g. https%3A%2F%2Fmcp.deepwiki.com%2Fmcp).
### As a GitHub Action — admission gate for MCP servers
1. mcpscan — vet an MCP server's advertised tools for prompt-injection / tool-poisoning before your agent trusts it.
2. rugcheck / swap-gate — honeypot and pre-trade safety checks for Base tokens.
## mcpscan — vet an MCP server before your agent trusts it
Every tool an MCP server advertises runs inside your agent's context — its name, description and JSON schema are read by the model, so a poisoned or injection-laden tool can steer the agent before it ever calls anything. Scan any server in one command, no key:
npx mcpscan https://mcp.deepwiki.com/mcp
or pin a reproducible build straight from the release tag, no install:
npx -y github:rezearcher/greyridge-x402-tools#v0.3.1 mcpscan https://mcp.deepwiki.com/mcp
Prints tools scanned, issue counts by severity, risk score, and a verdict (clear / review / block). Exit code 2 on block, so it drops straight into CI as a gate before you wire a new server to an agent. Static analysis of advertised tool metadata only — it never invokes your tools. Checks cover OWASP LLM01/LLM08 patterns: hidden instructions, conceal-from-user directives, data-exfiltration hints, cross-tool shadowing, and invisible-unicode payloads. Itemized findings with evidence and OWASP mapping: paid /scan/mcp ($0.05 USDC, x402 on Base).
Scanning a private or local server (nothing leaves your machine except the tool list):
npx github:rezearcher/greyridge-x402-tools mcpscan --from-egress egress.json
### Offline — audit an mcp-egress run with no network
If you already record a server with mcp-egress, score its egress.json fully offline — nothing leaves the machine:
bash
mcp-egress run --calls calls.json --out egress.json -- uvx some-mcp-server
npx -y github:rezearcher/greyridge-x402-tools#v0.3.1 mcpscan --from-egress egress.json # reads .tools[], exits 2 on block
Reads the recorded .tools[] (name/title/description/annotations) and applies the same tool-poisoning rules locally — no second connection to the server, no payment. Exit 0 clear / 1 review / 2 block. The one-liner is pinned to the v0.3.1 release tag so a CI admission gate gets a fixed, reproducible artifact.
### Continuous monitoring — catch a server that turns hostile after you trust it
A one-time scan tells you a server is clean today. The real supply-chain risk is a server you already trust quietly changing its tool definitions later — a rug-pull on an approved dependency. Grey Ridge monitors your servers on a schedule and alerts you when a tool's description, schema or risk verdict changes:
$9.99/mo — continuous monitoring with drift alerts, full itemized findings, and OWASP LLM01/LLM08 mapping for every server you track: https://x402-data-api.sigrunner.workers.dev/pricing
The CLI and Action above stay free forever for point-in-time scans.
### Badge for your MCP server's README
Live shields.io badge showing the scan verdict for any public MCP server (free, cached 6h):
markdown
Replace YOURMCPURL with your URL-encoded server endpoint (e.g. https%3A%2F%2Fmcp.deepwiki.com%2Fmcp).
### As a GitHub Action — admission gate for MCP servers
收录徽章（可选）
想把收录标记放进 README 就复制这行，可选，不影响收录。
[](https://anclum.com/zh/s/rezearcher-greyridge-x402-tools/)
- 来源
- github · https://github.com/rezearcher/greyridge-x402-tools
- 按领域浏览
- 开源项目
- 收录于
- 今天
- 安全策略
- 我们没在该仓库根目录找到
SECURITY.md（这不代表不安全）
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。