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-broadcastWrote 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-broadcast/mcp-broadcast)<a href="https://agentmods.dev/mcp/cryptoapis-io/cryptoapis-mcp-broadcast/mcp-broadcast"><img src="https://agentmods.dev/badge/mcp/cryptoapis-io/cryptoapis-mcp-broadcast/mcp-broadcast/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/cryptoapis-io/cryptoapis-mcp-broadcast/mcp-broadcast"><img src="https://agentmods.dev/badge/mcp/cryptoapis-io/cryptoapis-mcp-broadcast/mcp-broadcast.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-broadcast 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 2mo 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
{
"mcp-broadcast": {
"command": "npx",
"args": [
"-y",
"@cryptoapis-io/mcp-broadcast"
],
"env": {
"CRYPTOAPIS_API_KEY": ""
}
}
}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.
- 2mo ago First seen · 12 lines scan A 9fcfcef76732
mcp-broadcast is an MCP server published in the GitHub repository CryptoAPIs-io/cryptoapis-mcp-broadcast (0 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
mcp-signer
Local transaction signing for EVM, UTXO, Tron, XRP, Kaspa, Solana and Tezos — no API calls. Runs locally from the @cryptoapis-io/mcp-signer npm package.
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-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.