InsumerAPI 远程 MCP 服务器是什么?
InsumerAPI 的远程 MCP 服务器是一个托管的 Model Context Protocol 端点,地址是 https://api.insumermodel.com/mcp,AI 助手无需在本地安装或运行任何东西即可连接。
InsumerAPI MCP Server已验证已精选
@InsumerAPI
基本信息
关于 InsumerAPI MCP Server
面向 AI 智能体的钱包认证：发送一个区块链钱包和条件，即可在 37 条链上获得签名的“是”或“否”，从不返回余额。托管于 https://api.insumermodel.com/mcp，无需密钥（10 个工具），或用 npx -y mcp-server-insumer 在本地运行（27 个工具）。
连接信息
https://api.insumermodel.com/mcp接入方式
claude mcp add insumer --transport http https://api.insumermodel.com/mcpInsumerAPI MCP Server 工具
10Evaluate a list of 1 to 10 conditions against a wallet's on-chain state and return one signed attestation: a yes or no for each condition, never the balance. One call reads the chain for every condition in the list and returns a single attestation covering all of them, so conditions of different kinds and on different chains are combined in one signed result. A condition states what must be true of the wallet, such as a minimum token balance, ownership of an NFT, an attestation held or a registered agent ID; the type field on each condition lists the kinds available and the fields each one takes. Chains: EVM chains plus Solana, XRPL, Bitcoin, Tron, Stellar and Sui; Bitcoin, Tron, Stellar and Sui support token_balance only. The attestation is signed twice: ES256, with a kid identifying the key, and a post-quantum ML-DSA-65 signature (pqSig, pqKid). Each result includes evaluatedCondition, a SHA-256 conditionHash, and the block (EVM), ledger (XRPL, Stellar) or checkpoint (Sui) it was read at. An attestation expires 30 minutes after it is signed, or 5 minutes when it includes a delegation condition. Costs 1 credit (2 with proof: 'merkle'). An rpc_failure error (503) means a read did not complete and nothing was signed: retry, and never treat it as a no. Current chain and check counts: https://insumermodel.com/llms.txt On this hosted endpoint the call is paid from a shared daily allowance, so the caller is not charged; the credit cost above applies on the caller's own API key, and each result states the price on a key and by x402 pay-per-call.
List the compliance templates available for EAS attestation conditions. Each template carries pre-configured schema IDs, attester addresses, and decoder contracts for a KYC or identity provider (Coinbase Verifications on Base, Gitcoin Passport on Optimism), so a condition can name the template instead of raw EAS parameters. No authentication or credits required.
Generate a signed wallet trust fact profile for an EVM wallet: a curated set of presence checks organized into dimensions (stablecoins, governance, nfts, staking, institutional_stablecoins, tokenized_treasuries, stablecoin_deposits, wrapped_bitcoin, names, account): 155 base checks across 27 chains in 10 dimensions. Optional Solana, XRPL, Bitcoin and Tron wallets add their own dimensions, up to 176 checks across 29 chains in 14 dimensions; optional Stellar and Sui wallets let rows inside existing dimensions evaluate. Dimensions arrive in a fixed order: the base dimensions as listed, then any of solana, xrpl, bitcoin and tron that were switched on, in that order. The account dimension holds two rows per chain on Ethereum, Base, Arbitrum, Optimism and Polygon: contract code at the wallet address, and an EIP-7702 delegation there; a plain key reads false on both, and which contract is never named. Rows on a chain whose wallet is not supplied stay in the signed profile with evaluated: false. Every check is held or not held (present or not present in the account dimension), never a balance. The signed conditionSetVersion (currently 2026-10-08) names the check list that was run; log it, never reject on it. Returns per-dimension pass/fail counts and an overall summary: no score, no opinion. Designed for AI agent-to-agent trust decisions. Costs 3 credits (6 with proof: 'merkle'). An rpc_failure error (503) means a read did not complete and nothing was signed: retry, and never treat it as a no. Current chain and check counts: https://insumermodel.com/llms.txt On this hosted endpoint the call is paid from a shared daily allowance, so the caller is not charged; the credit cost above applies on the caller's own API key, and each result states the price on a key and by x402 pay-per-call.
Generate wallet trust fact profiles for up to 10 wallets in a single request. Faster than sequential calls. Each wallet gets an independently signed profile with its own TRST-XXXXX ID: 155 base checks across 27 chains in 10 dimensions (stablecoins, governance, nfts, staking, institutional_stablecoins, tokenized_treasuries, stablecoin_deposits, wrapped_bitcoin, names, account), up to 176 checks across 29 chains in 14 dimensions with the optional Solana, XRPL, Bitcoin and Tron wallets; the signed conditionSetVersion (currently 2026-10-08) names the check list. Dimensions arrive in a fixed order, identical for every wallet in the batch: the base dimensions as listed, then any of solana, xrpl, bitcoin and tron that were switched on, in that order. Supports partial success: failed wallets get error entries while successful ones return full profiles. Costs 3 credits per successful wallet (6 with proof: 'merkle'); credits are charged only for successful profiles, while a pay-per-call (x402) payment covers every wallet in the request. A wallet whose reads did not complete gets an error entry and no signed profile: retry that wallet, and never treat the entry as a no. Each profile lists every check, so the response is large; by default the text is a summary per wallet (profile ID, held / not held / not evaluated counts, and the checks held in each dimension, in the fixed dimension order; the account dimension's checks are present rather than held), and the complete signed profiles are returned unchanged as structuredContent. Set detail to 'full' on the call to get the complete signed profiles as text too. Profiles cannot be fetched again, so a later call signs fresh profiles and is charged again. On this hosted endpoint the call is paid from a shared daily allowance, so the caller is not charged; the credit cost above applies on the caller's own API key, and each result states the price on a key and by x402 pay-per-call.
Get InsumerAPI's public signing keys as a JWKS (JSON Web Key Set): an ECDSA P-256 key under its kids, followed by the ML-DSA-65 post-quantum key as RFC 9964 AKP entries. Signatures on attestation and trust responses verify against these keys. Match an entry by the kid (or pqKid) on the response, never by position; an unknown kid is unverifiable, not refuted. No authentication required.
Browse merchants in the public directory. Filter by accepted token, verification status. Returns company name, website, tokens accepted, discount info, and walletTerms (the store's terms with and without proof of wallet control).
Get full public merchant profile including token tiers, NFT collections, discount mode, verification status, and walletTerms: what the store gives a wallet with and without proof of control, so you can decide whether to sign before creating a code.
List the tokens and NFT collections listed in the Insumer registry. Filter by chain, symbol, or asset type. The registry is a directory, not the list of what can be checked: an attestation can check any token on a supported chain, and NFTs on EVM chains, Solana and XRPL, whether listed or not. An empty result means nothing is listed under that filter, not that the token is unsupported.
Calculate discount for a wallet at a merchant. Checks on-chain balances and returns tier and discount percentage per token, never raw balance amounts. Free: does not consume credits. Takes an EVM, Solana or XRPL wallet. An rpc_failure error (503) means a read did not complete: retry, and never treat it as not eligible. The check carries no proof of wallet control, so totalDiscount is what an unproven wallet gets; walletTerms gives the store's terms, and discountIfProven (when present) is what signing would get.
Validate an INSR-XXXXX discount code. For merchant backends during ACP/UCP checkout to confirm code validity, discount percent, and expiry. Returns valid/invalid status with reason, and walletProven (whether the code went to a caller that proved control of the wallet). No authentication required, no credits consumed. Does not expose wallet or token data.
概览
InsumerAPI: wallet auth for AI agents
InsumerAPI answers one question about a blockchain wallet with a signed yes or no: does this wallet satisfy this condition right now? Send a wallet address and up to ten conditions, get back a boolean for each, signed and verifiable offline against published keys. The balance itself is never returned.
What you can ask
- "Check if this wallet holds at least 100 USDC on Base."
- "Does this wallet own an NFT from this collection?"
- "Is this wallet a registered ERC-8004 agent on Base?"
- "Build a trust profile for this wallet."
- "List the signing keys and tell me how to verify an attestation offline."
Coverage
Token balances, NFT ownership, EAS attestations (including Coinbase Verifications and Gitcoin Passport templates), Farcaster IDs, ERC-8004 agent registration and ERC-7710 delegations, across 37 chains: 31 EVM chains plus Solana, XRP Ledger, Bitcoin, Tron, Stellar and Sui. A wallet trust profile runs 145 checks across 27 chains in nine dimensions and reports what is held or not held, with no score and no opinion.
Every answer is signed
Each response carries an ECDSA signature and a post-quantum companion signature (ML-DSA-65), a hash of the evaluated condition, and the block it was read at. Anyone can check a result offline with the open-source insumer-verify package (npm and PyPI).
Two ways to use it
Hosted (no install, no key): connect to https://api.insumermodel.com/mcp over MCP streamable HTTP. Ten tools: insumer_jwks, insumer_attest, insumer_compliance_templates, insumer_wallet_trust, insumer_batch_wallet_trust, insumer_list_merchants, insumer_get_merchant, insumer_list_tokens, insumer_check_discount, insumer_validate_code. The hosted server is shared, so the tools that produce signed results are rate limited per day.
Local (all 27 tools, your own key):
{
"mcpServers": {
"insumer": {
"command": "npx",
"args": ["-y", "mcp-server-insumer"],
"env": { "INSUMER_API_KEY": "insr_live_..." }
}
}
}
What it does not do
It only reads public on-chain state. It does not return exact balances, prices or portfolio values, and it never sends transactions or moves assets. InsumerAPI holds no secrets, requires no identity, and stores no wallet addresses or conditions from verification requests.
Links
- Docs: https://insumermodel.com/developers/
- Source (MIT): https://github.com/insumerapi/mcp-server-insumer
- npm: https://www.npmjs.com/package/mcp-server-insumer
- MCP Registry:
com.insumermodel/insumer
常见问题
怎么连接 InsumerAPI 的 MCP 服务器?
把端点 https://api.insumermodel.com/mcp 添加到任意支持 MCP 的客户端,比如 Claude Code、Cursor 或 VS Code。本页的接入代码块可以一步配置好每个客户端。
InsumerAPI 的 MCP 服务器需要认证吗?
不需要。InsumerAPI 的 MCP 服务器不需要认证——直接用端点地址连接即可。
InsumerAPI 的 MCP 服务器用的是哪种传输方式?
InsumerAPI 暴露的是 Streamable HTTP 端点,这是远程 MCP 服务器普遍使用、主流客户端都支持的传输方式。
更多远程 MCP 服务器
2pr.io
Write, schedule and publish LinkedIn posts in your own voice, reply to comments and read your analytics, all from your AI assistant. Remote MCP server with OAuth sign-in.
%20-%20Sarah%20Xu.svg){kind=icon}
Adobe Experience Manager
Manage your Adobe Experience Manager content
AWS Marketplace
Discover, evaluate, and buy solutions for the cloud
AOI — Environmental Intelligence
AOI is a commercial environmental-intelligence gateway that gives AI agents programmatic access to 38 real-world intelligence capabilities — climate risk, satellite monitoring, methane detection, water & soil, vegetation
AdaptlyPost
AdaptlyPost: Schedule and publish social posts to Instagram, TikTok, YouTube, X, Facebook, LinkedIn, Pinterest, Threads, and Bluesky from any MCP client.
评论