Side-by-Side Model Context Protocol Comparison
Blockrun MCP vs Octodamus Core
In-depth architectural comparison of the Blockrun MCP and Octodamus Core MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Blockrun MCP
Aggregators · Local stdio
Quality: 67/100 (Great) | Auth: other
Octodamus Core
Aggregators · Local stdio
Quality: 63/100 (Good) | Auth: API Key required
Verdict Summary: Choose Blockrun MCP if you need specialized Aggregators tools running via a local process. Choose Octodamus Core if your workspace requires Aggregators integration with local subprocess execution. Both servers can be configured concurrently in your client's
mcpServers manifest.Which MCP Server Should You Choose?
Choose Blockrun MCP when:
- You need dedicated capabilities in the Aggregators domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: other (Free / Open Source).
- Primary tools included: blockrun_wallet, blockrun_chat, blockrun_models.
Choose Octodamus Core when:
- You need dedicated capabilities in the Aggregators domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: API Key required (Freemium).
- Primary tools included: get_agent_signal, get_market_brief, get_polymarket_edge.
Feature & Specification Comparison
Tools & Capabilities Breakdown
Blockrun MCP Tools (20)
blockrun_wallet
Call this tool to manage the BlockRun payment wallet and control agent spending budgets.
Call this FIRST if any other blockrun_* tool returns a payment/balance error.
Call this to check your current USDC balance before expensive operations.
Call this to set spending limits before spawning child agents.
The server holds TWO wallets — one on Base, one on Solana — but pays on ONE
active chain at a time. status shows both addresses/balances and which is active.
Default chain is Base.
To pay on Solana (no env vars, no file editing, no restart):
1. action:"chain" chain:"solana" → provisions + activates the Solana wallet
2. action:"setup" → Solana address + funding QR (send USDC SPL on Solana)
Switch back with action:"chain" chain:"base". Base-only — these ignore Solana and
need Base: blockrun_music, blockrun_speech, blockrun_video, blockrun_realface,
paid blockrun_price, blockrun_chat routing:"smart", and native Anthropic
(claude-*). blockrun_image pays on either chain.
Actions:
- status (default): Both wallet addresses + USDC balances, active chain, session spending
- deposit: Buy USDC with a card — mints a one-time Coinbase Onramp link and opens it in the browser (Base only; funds settle into your own wallet). Paid tools auto-open this on an out-of-funds failure; call it directly to fund up front.
- setup: Get funding instructions + QR code for the ACTIVE chain (call this when balance is 0)
- qr: Open QR code (active chain) in system viewer
- chain + chain:"base"|"solana": Switch the active payment chain (omit chain: to just see the current one)
Budget controls:
- budget + budget_action:"set" + budget_amount:1.00 → Set global spend cap
- budget + budget_action:"clear" → Remove global spend cap
Multi-agent orchestration:
- delegate + agent_id:"research" + agent_limit:2.00 → Allocate $2 to a child agent
- revoke + agent_id:"research" → Remove a child agent's budget
- report → See per-agent spending breakdown
Usage pattern for multi-agent systems:
1. blockrun_wallet action:"delegate" agent_id:"worker-1" agent_limit:1.00
2. Pass agent_id:"worker-1" to all blockrun_chat/search/etc calls for that agent
3. blockrun_wallet action:"report" to audit spending
Do NOT call this for actual AI queries — use blockrun_chat for that.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Blockrun MCP Configuration
Octodamus Core Configuration
