Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/rpc-edge/rpcedge-toolkitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/rpc-edge/rpcedge-toolkit/rpcedge)<a href="https://agentmods.dev/mcp/rpc-edge/rpcedge-toolkit/rpcedge"><img src="https://agentmods.dev/badge/mcp/rpc-edge/rpcedge-toolkit/rpcedge.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
rpcedge scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"rpcedge": {
"command": "npx",
"args": [
"-y",
"rpcedge-mcp@latest"
],
"env": {}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 10 lines scan A 01b47e5ebe46
rpcedge is an MCP server published in the GitHub repository rpc-edge/rpcedge-toolkit (1 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
polymarket-toolkit
Read-only Polymarket data tools for AI agents: profiles, PnL, market scans. No keys, no orders. Runs locally from the polymarket-toolkit-mcp npm package.
indodax-cli
Command-line interface for the Indodax cryptocurrency exchange. Runs locally from the @ibidathoillah/indodax-cli npm package.
toreva
Policy-checked Solana wallet actions. Users set the limits. Toreva reads, simulates, prepares unsigned transactions, explains, and receipts every outcome. Runs locally from the @toreva/mcp npm package. Needs 1 environment variable to run.
kit
Policy-checked Solana wallet actions with user-set limits, unsigned transactions, and receipts. Runs locally from the @toreva/mcp npm package.
agent-kit
MCP server "agent-kit" as configured in sendaifun/solana-agent-kit. Runs /absolute/path/to/build/index.js with node. Needs 3 environment variables to run.
pipefy
MCP server that exposes Pipefy's GraphQL API. Runs locally from the pipefy-mcp-server Python package.