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/CryptoAPIs-io/cryptoapis-mcp-simulateWrote 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/cryptoapis-io/cryptoapis-mcp-simulate/mcp-simulate)<a href="https://agentmods.dev/mcp/cryptoapis-io/cryptoapis-mcp-simulate/mcp-simulate"><img src="https://agentmods.dev/badge/mcp/cryptoapis-io/cryptoapis-mcp-simulate/mcp-simulate.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
mcp-simulate 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 12 lines scan A 7e1c1afcda28
mcp-simulate is an MCP server published in the GitHub repository CryptoAPIs-io/cryptoapis-mcp-simulate (0 stars, last pushed 1mo ago), with no licence file. 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
mcp-hd-wallet
MCP server for HD wallet management, balance, and sync on EVM, UTXO, XRP via Crypto APIs. Runs locally from the @cryptoapis-io/mcp-hd-wallet npm package. Needs 1 environment variable to run.
mcp-prepare-transactions
MCP server for building unsigned transactions on EVM, Tezos, Solana, Kaspa, XRP, UTXO, Tron. Runs locally from the @cryptoapis-io/mcp-prepare-transactions npm package. Needs 1 environment variable to run.
mcp-address-latest
MCP server for current balance and state of EVM, UTXO, Solana, XRP, Kaspa addresses via Crypto APIs. Runs locally from the @cryptoapis-io/mcp-address-latest npm package. Needs 1 environment variable to run.
mcp-block-data
MCP server for retrieving block-level data from EVM, UTXO, and XRP blockchains via Crypto APIs. Runs locally from the @cryptoapis-io/mcp-block-data npm package. Needs 1 environment variable to run.
mcp-blockchain-events
MCP server for subscribing to and managing on-chain event webhooks via Crypto APIs. Runs locally from the @cryptoapis-io/mcp-blockchain-events npm package. Needs 1 environment variable to run.
mcp-blockchain-fees
MCP server for fee recommendations and gas estimation on EVM, UTXO, XRP, Tezos, Solana. Runs locally from the @cryptoapis-io/mcp-blockchain-fees npm package. Needs 1 environment variable to run.