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/ExpertVagabond/ordinals-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/expertvagabond/ordinals-mcp/ordinals)<a href="https://agentmods.dev/mcp/expertvagabond/ordinals-mcp/ordinals"><img src="https://agentmods.dev/badge/mcp/expertvagabond/ordinals-mcp/ordinals/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/expertvagabond/ordinals-mcp/ordinals"><img src="https://agentmods.dev/badge/mcp/expertvagabond/ordinals-mcp/ordinals.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ordinals 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 12d 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
{
"ordinals": {
"command": "npx",
"args": [
"-y",
"ordinals-mcp"
],
"env": {
"HIRO_API_KEY": "",
"ORDISCAN_API_KEY": "",
"MAGIC_EDEN_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.
- 12d ago First seen · 14 lines scan A be4942c4a070
ordinals is an MCP server published in the GitHub repository ExpertVagabond/ordinals-mcp (2 stars, last pushed 4d 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
otskit-mcp
Stamp, upgrade, and verify Bitcoin timestamps via AI agents. No API keys required. Runs locally from the @otskit/mcp npm package.
sui-mcp
Read-only Sui blockchain analytics: 59 tools, protocol-aware tx decoding, no API keys or wallet. Runs locally from the sui-analytics-mcp npm package. Needs 6 environment variables to run.
solana
Solana MCP server for wallet, transactions & programs. Runs locally from the solana-mcp-server npm package.
sui-mcp-server
53-tool MCP server for Sui blockchain — wallets, DeFi, Move contracts, staking, SuiNS, analytics. Runs locally from the sui-mcp-server npm package.
orphograph
MCP server "orphograph" as configured in Orphograph/Orphograph. Launched with https://github.com/Orphograph/Orphograph/releases/download/mcp-v0.1.1/orphograph. Needs 2 environment variables to run.
coinpaprika
Real-time crypto market data: prices, tickers, exchanges, OHLCV candles, and metadata. Remote server at mcp.coinpaprika.com.