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.
npx agentmods add mcp/vdappdev2/verusidx-mcp/address-sendgit clone --depth 1 https://github.com/vdappdev2/verusidx-mcpWrote 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/vdappdev2/verusidx-mcp/address-send)<a href="https://agentmods.dev/mcp/vdappdev2/verusidx-mcp/address-send"><img src="https://agentmods.dev/badge/mcp/vdappdev2/verusidx-mcp/address-send.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
send 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 3d 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
{
"send": {
"command": "npx",
"args": [
"-y",
"@verusidx/send-mcp"
],
"env": {}
}
}What else server.json configures
This page is one entry in a file that holds 7. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 3d ago First seen · 10 lines scan A 69d5381a8514
send is an MCP server published in the GitHub repository vdappdev2/verusidx-mcp (2 stars, last pushed 3mo 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
cabal-hunter
MCP server "cabal-hunter", hosted remotely at api.cabal-hunter.com, as configured in paulf280-ui/solana-safe-sniper-mcp-template.
coingecko-mcp-server
Crypto market data via CoinGecko — prices, markets, history, trending, and deep coin metadata. Runs locally from the @cyanheads/coingecko-mcp-server npm package. Needs 2 environment variables to run.
agentwallet
Wallet infrastructure for Ai agents. EVM + Solana. x402 payments. No KYC. Runs locally from the agentwallet-mcp npm package. Needs 1 environment variable to run.
flario
MCP server for Flare Network. FTSO price feeds, FDC cross-chain attestations with local proof verification, FAssets state, and x402 agent payments with chain-verified receipts. Works with Claude, Cursor, and any MCP client. Runs locally from the flario npm package. Needs 4 environment variables to run.
bvcc-agent-wallet
Non-custodial BVCC Agent Wallet on-chain for AI agents: balances, transfers, approvals, swaps. Runs locally from the @bvcc/agent-mcp npm package. Needs 6 environment variables to run.
cryptodata-mcp
CryptoData MCP Server - Real-time crypto market data, DeFi analytics, and on-chain intelligence... Runs locally from the cryptodata-mcp npm package.