rezearcher/greyridge-x402-tools

Vet an MCP server before your agent trusts it: static tool-poisoning / prompt-injection scan (OWASP…

Before you install: no copy-paste command · license MIT · link reachable

First step: npx mcpscan https://mcp.deepwiki.com/mcp

no SECURITY.md

View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site

Install & config

Client config (built from the install command this repo gives)

{
  "mcpServers": {
    "rezearcher-greyridge-x402-tools": {
      "command": "npx",
      "args": ["mcpscan"]
    }
  }
}

Parsed from the README we fetched on 2026-10-26; we have not executed it.

command/args come from the install command the repository states. When it is ambiguous, the project README wins.

VS Code (.vscode/mcp.json - the key is servers)

{
  "servers": {
    "rezearcher-greyridge-x402-tools": {
      "command": "npx",
      "args": ["mcpscan"]
    }
  }
}

Same server, but VS Code keeps it under <code>servers</code>.

Claude Code (command line)

claude mcp add --transport stdio rezearcher-greyridge-x402-tools -- npx mcpscan

Claude Code does not read a config file; add the server with this command.

Key names differ by client: Clients & CLI

Star count: 0 ★ · rezearcher/greyridge-x402-tools · read from the GitHub search API · (checked 2026-11-13 20:00:50)
Source: read directly from its GitHub page · type: open-source project
Harvest history: first seen 2026-10-22 · last seen 2026-11-14 · seen 27× · listed by 1 sources
Score: score 103 · 1 sources · repo
Install: npx mcpscan

FAQ (answers come from our records)

How do I install it?

The repository provides this install command: npx mcpscan. It comes from the repository itself; we cannot guarantee it runs as-is in your client.

Who is it for?

We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.

Who maintains it?

repository rezearcher/greyridge-x402-tools；first catalogued 2026-10-22；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.

# 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

Listed badge (optional)

Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.

[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/en/s/rezearcher-greyridge-x402-tools/)

Source: github · https://github.com/rezearcher/greyridge-x402-tools
Browse by field: Open source
added: today
Security policy: no SECURITY.md at the repository root (which does not mean it is unsafe)

More like this

tedix-hq/tedixOpen-source project hashgraph-online/hol-guardOpen-source project linny006/trending-claude-skillsOpen-source project

All 1,671 →

Filed under

Open source1,671 entries Open-source repo2,514 From GitHub2,437

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index