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/hyperledger-iroha/irohaWrote 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/hyperledger-iroha/iroha/iroha-iroha-taira)<a href="https://agentmods.dev/mcp/hyperledger-iroha/iroha/iroha-iroha-taira"><img src="https://agentmods.dev/badge/mcp/hyperledger-iroha/iroha/iroha-iroha-taira/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/hyperledger-iroha/iroha/iroha-iroha-taira"><img src="https://agentmods.dev/badge/mcp/hyperledger-iroha/iroha/iroha-iroha-taira.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
iroha-taira 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
{
"iroha-taira": {
"type": "http",
"url": "https://taira.sora.org/v1/mcp",
"note": "Current primary public Taira MCP endpoint. If your deployment or operator gives you a different public Torii root, override it in local Codex config instead of editing the repo copy."
}
}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 · 7 lines scan A 5339fbefb30d
iroha-taira is an MCP server published in the GitHub repository hyperledger-iroha/iroha (488 stars, last pushed yesterday), licensed Apache-2.0. 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-09-03.
Other mcp servers, from other repositories
3D-AI-Agent-Avatar
3D AI Agent Avatar — render any GLB, give it a Solana wallet, a voice, and pump.fun powers. Runs locally from the @three-ws/avatar-agent npm package. Needs 11 environment variables to run.
three-token-mcp
Price, hold, and burn $THREE on Solana — the first MCP server whose actions burn a token. Runs locally from the @three-ws/three-token-mcp npm package. Needs 5 environment variables to run.
threews-agent
Give your AI agent an x402 wallet: discover and pay for services in USDC, or earn from your own. Remote server at three.ws.
threews-pumpfun
Free pump.fun and Solana token discovery and on-chain analysis tools, by three.ws. Remote server at three.ws.
bsv-wallet
MCP server "bsv-wallet" as configured in Calhooon/bsv-wallet-cli. Launched with cargo run --release --manifest-path mcp/Cargo.toml. Needs 1 environment variable 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.