Insumer
Verify on-chain claims with ECDSA-signed boolean checks across 32 chains before you ship crypto features or compliance flows.
Overview
Insumer is a MCP server for the Ship phase that provides read-first, ECDSA-signed boolean blockchain verification across 32 chains through 26 stdio tools.
What is this MCP server?
- Read-first blockchain verification returning ECDSA-signed boolean results
- Coverage across 32 chains with 26 dedicated MCP tools
- npm package mcp-server-insumer v1.8.3 using stdio transport
- Requires INSUMER_API_KEY (insr_live_ prefix) as a secret environment variable
- 32 blockchains supported
- 26 MCP verification tools
- ECDSA-signed boolean response model
What problem does it solve?
Agents and scripts assert on-chain facts without cryptographic proof, inviting shipping vulnerabilities and false compliance claims.
Who is it for?
Indie Web3 builders who need agent-callable verification gates across many chains during security review and launch prep.
Skip if: Non-crypto products, teams unwilling to manage Insumer API keys, or workflows needing custody, trading, or unsigned exploratory chain queries only.
What do I get? / Deliverables
You get reproducible, ECDSA-signed boolean verifications across 32 chains via MCP before you merge or launch crypto-facing features.
- Agent-callable signed boolean verification results across 32 blockchains
- Repeatable pre-ship checks for on-chain assumptions in crypto features
Recommended MCP Servers
Journey fit
How it compares
Signed on-chain verification MCP—not a wallet, DEX, or generic block explorer chat skill.
Common Questions / FAQ
Who is Insumer for?
Solo developers and security-minded teams building multi-chain products who want MCP tools that return ECDSA-signed boolean verification results.
When should I use Insumer?
Use it in Ship when you validate addresses, states, or policies on-chain and need signed booleans before release, audits, or automated agent checkpoints.
How do I add Insumer to my agent?
Install mcp-server-insumer from npm, set INSUMER_API_KEY to your insr_live_ key in the MCP env config, register stdio transport in Claude Code or Cursor, and enable the 26 verification tools.