Insumer MCP Server
MCP for condition-based access checks: signed boolean attestations across 37 chains without exposing balances.
- Sato Score81
- ChainsMultichain
Insumer MCP Server is an open-source MCP server, with last code activity on 2026-10-13 (Active). Latest release on 2026-10-13. Sato Score 81/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-15. How the score works →
See how to install Insumer MCP Server →Last commit Sep 21, 2026 · Last release Oct 13, 2026 (v1.21.1) · ★ 1
Listed from github.com/douglasborthwick-crypto/mcp-server-insumer on 2026-07-13. Install: reproduced by Sato Hub on 2026-07-21. Evidence →
Next step
Watch Insumer MCP Server
One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpRun Sato Hub Preflight on douglasborthwick-crypto/mcp-server-insumer before I use it.Your project?
Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.
Claim this listing →Overview
Insumer's MCP server lets an agent verify onchain conditions (for example, that a wallet meets a holding threshold) as signed boolean attestations across 37 chains, without revealing the underlying balances. An agent builder plugs it in for token-gating and eligibility checks where the agent needs a yes/no proof rather than raw wallet data. MIT-licensed; small early-stage project.
Sato Score
81/100· HighHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 35/35
- Code transparency
- 17/20
- Interface verifiability
- 8/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 12/15
- Independent verification
- 3/10
Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety).
Sato Check
v1.21.1 · as of 2026-10-14- Does it take your key?
- No key read found
- Does your key leave?
- Not yet run
- Can it move funds on its own?
- Unknown
A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".
Evidence — listed vs checked · what the words mean
Listed from github.com/douglasborthwick-crypto/mcp-server-insumer on 2026-07-13. Install: reproduced by Sato Hub on 2026-07-21.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Multichain | self-reported | github.com/douglasborthwick-crypto/mcp-server-insumer | as of 2026-10-15 |
| Verification status | Unverified — not independently reviewed | self-reported | github.com/douglasborthwick-crypto/mcp-server-insumer | as of 2026-10-15 |
| Recent activity | last release 2026-10-13 · last commit 2026-09-21 | observed | github.com/douglasborthwick-crypto/mcp-server-insumer | 2026-10-15 |
| Install works | reproduced — install and entry both completedshows the install path works as written; not a statement about runtime behaviour | ✓ reproduced | github.com/douglasborthwick-crypto/mcp-server-insumer | 2026-07-21 |
| Website answers | answered (HTTP 301) | observed | github.com/douglasborthwick-crypto/mcp-server-insumer | 2026-10-15 |
| Daily check record | 90 of 90 daily checks since 2026-07-17 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-14 |
| Takes your key | no private-key read found in what we read | traced | satohub.ai | 2026-10-14 |
| Key leaves the machine | not yet run with planted test keysthe sandbox lane has not run on this version | observed | satohub.ai | not dated |
| Moves funds on its own | unknown — could not read what it exposes | traced | satohub.ai | 2026-10-14 |
| Creator profile | https://github.com/douglasborthwick-cryptoconfidence 0.70 | self-reported | github.com/douglasborthwick-crypto/mcp-server-insumer | as of 2026-07-14 |
| Deploys as | npmconfidence 0.85 | self-reported | github.com/douglasborthwick-crypto/mcp-server-insumer | as of 2026-07-14 |
| Works with | Claude Desktop, Cursor, Windsurf, LangChain, ElizaOS, OpenAI GPTconfidence 0.85 | self-reported | github.com/douglasborthwick-crypto/mcp-server-insumer | as of 2026-07-14 |
| Sato Score | 81/100 (High)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-10-15 |
Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.
Install — reproduced in a container Jul 21, 2026
Runtime: Node.js
npm install npm run build npx @modelcontextprotocol/inspector node build/index.js (test); npx -y mcp-server-insumer (client config)
You supply: INSUMER_API_KEY (free tier available, no signup required for a generated key; 100 reads/day, 10 verification credits)
claude mcp add satohub-insumer-mcp -- npx -y mcp-server-insumer
A local server: your client runs this command on your machine. Installing runs third-party software under your own credentials. Sato Hub publishes the documented invocation and, where the harness reproduced it, the date it did — neither is a safety review.
Read from the project’s own docs as of 2026-07-21. What a deploy spec is →
Observed record — 91 daily checks since 2026-07-17
- Succeeded
- 91
- Failed
- 0
- Their error
- 0
- Unattributed
- 0
This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 46 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.
Last 30 days — to 2026-10-15, one point per UTC day
A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.
Details
- Chains
- Multichain
- Agent types
- MCP Server, Data Provider
- Open source
- Yes
- Deploys as
- npm
- Works with
- Claude Desktop, Cursor, Windsurf, LangChain, ElizaOS, OpenAI GPT
- Last checked
- 2026-10-15
Marketplace Signals
No marketplace signals recorded for this resource yet.
Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.
Where Insumer MCP Server fits
Related concepts: How Agents Use Wallets, What Are Onchain Agents?, What Are MCPs? The Standard Way to Give Agents Tools
Recent Activity
All news →Releases and posts from Insumer MCP Server, pulled from its GitHub and X.
mcp-server-insumer 1.21.1
insumer_attest describes itself as the one operation it is. A list of 1 to 10 conditions goes in and one signed attestation comes out, with conditions of different kinds and on different chains combined in a single call. The description states that the attestation is signed twice (ES256 and a post-quantum ML-DSA-65 signature) and when it expires. What each kind of condition takes is on the input f
mcp-server-insumer 1.21.0
Hosted deployments state the price to the caller. A new hostedPricing option, on in the HTTP runner ( node build/http.js ) and on the hosted endpoint, is for a deployment on a shared key, where the caller pays nothing. A successful insumer_attest , insumer_wallet_trust or insumer_batch_wallet_trust result there no longer reports the shared key's charge ( meta.creditsCharged ), which models read as
mcp-server-insumer v1.20.3
README and SKILL.md state the free tier as 10 free verifications plus 100 requests a day, list USDT-TRC20 among the credit payments, and give the Merkle proof coverage (27 of the 31 EVM chains). insumer_confirm_payment accepts exactly the chains the API accepts for it (the seven EVM payment chains and Solana, USDC only), so a Tron chain ID is refused before any request is sent, and the README stat
mcp-server-insumer v1.20.2
Tool descriptions, README and SKILL.md state what a caller observes: insumer_batch_wallet_trust is faster than sequential calls, and evm_view_call , ratio_to_amount and ratio_to_supply run on EVM chains ( ratio_to_supply on ERC-20 tokens). No tool name, input or output changes.
mcp-server-insumer 1.17.1
insumer_configure_tokens carries alsoOn on partner tokens and the own token: the same token on up to 9 other networks (EVM chains and Solana; not the XRP Ledger, not a native coin). The store decides which deployments count as the same token. Each network's balance is read in that token's own decimals there, the balances are added exactly, and the tier is awarded once. A read that fails on any lis
mcp-server-insumer 1.17.0
Prove the wallet for a discount. insumer_verify , insumer_acp_discount and insumer_ucp_discount take an optional walletProof ( { message, signature } ): an EIP-4361 message signed by the EVM wallet, with URI https://api.insumermodel.com/v1/merchants/{merchantId} . The field's description carries the exact message to sign. A proven wallet gets the store's full discount with no daily limit, and the
Listing History
Recorded changes to Insumer MCP Server's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Oct 13, 2026New release published
- Oct 8, 2026New release published
- Oct 3, 20264 releases trackedShowing the 2 most recent. Full release history is retained in the listing record.
- Sep 1, 2026Sato Score tier: Medium → HighScore 68 → 71.
- Aug 27, 2026Sato Score tier: High → MediumScore 78 → 68.
- Jul 28, 2026Sato Score tier: Medium → HighScore 67 → 78.
- Jul 21, 2026Verified: deploy spec
- Jul 18, 2026Sato Hub began tracking this listing
- Jul 14, 2026Enriched: creator profile url
- Jul 14, 2026Auto-enriched: deployment options, supported integrations
Compared with
Appears in
Related Resources
Coinbase AgentKit
ActiveCoinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.
Hyperliquid
ActiveOnchain perpetual futures and spot DEX running on its own L1 with an HyperEVM smart-contract layer.
Model Context Protocol (MCP)
ActiveAnthropic's open standard for connecting AI systems to external tools and data sources.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about Insumer MCP Server
- Is Insumer MCP Server open source?
- Yes. Insumer MCP Server is open source under the MIT license; the repository is https://github.com/douglasborthwick-crypto/mcp-server-insumer. Checked as of 2026-10-15.
- Which chains does Insumer MCP Server support?
- Insumer MCP Server lists support for Multichain as of 2026-10-15.
- Is Insumer MCP Server still maintained?
- The most recent code activity Sato Hub observed was on 2026-10-13 (last commit 2026-09-21, last release 2026-10-13), which Sato Hub labels "Active". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
- How do I install or run Insumer MCP Server?
- Node.js. Install: npm install && npm run build. Entry: npx @modelcontextprotocol/inspector node build/index.js (test); npx -y mcp-server-insumer (client config). Sato Hub reproduced this install in a container on 2026-07-21. It runs as an MCP server (npx -y mcp-server-insumer (stdio)).
- Is Insumer MCP Server verified on Sato Hub?
- Sato Hub holds one earned check for Insumer MCP Server: Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety). Its Sato Score is 81 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "Insumer MCP Server — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/insumer-mcpData last refreshed 2026-10-15; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.
Join the Sato Hub Briefing
Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.