広告掲載
MCP.so
ログイン

InsumerAPI MCP Server認証済み注目

@InsumerAPI

リポジトリホームページドキュメント

基本情報

トランスポート

Streamable HTTP

認証方式

不要

カテゴリ

AI とエージェント

作者

InsumerAPI

投稿者

Douglas Borthwick

InsumerAPI MCP Server について

AI エージェントのためのウォレット認証：ブロックチェーンのウォレットと条件を送ると、37 のチェーンにわたって署名付きの「はい」か「いいえ」が返り、残高は決して返しません。https://api.insumermodel.com/mcp でキー不要でホスト（10 ツール）、または npx -y mcp-server-insumer でローカル実行（27 ツール）。

#wallet-auth#blockchain#web3#attestation#ai-agents#erc-8004#verification

接続情報

https://api.insumermodel.com/mcp

セットアップ

claude mcp add insumer --transport http https://api.insumermodel.com/mcp

InsumerAPI MCP Server のツール

10

Evaluate 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

よくある質問

1

InsumerAPI のリモート MCP サーバーとは何ですか?

InsumerAPI のリモート MCP サーバーは、https://api.insumermodel.com/mcp にホストされた Model Context Protocol エンドポイントです。AI アシスタントはローカルに何もインストール・実行することなく接続できます。

2

InsumerAPI の MCP サーバーにはどう接続しますか?

エンドポイント https://api.insumermodel.com/mcp を Claude Code、Cursor、VS Code など任意の MCP 対応クライアントに追加してください。このページのセットアップ手順で各クライアントを一度に設定できます。

3

InsumerAPI の MCP サーバーは認証が必要ですか?

いいえ。InsumerAPI の MCP サーバーは認証不要です——エンドポイント URL で直接接続できます。

4

InsumerAPI の MCP サーバーはどのトランスポートを使用しますか?

InsumerAPI は Streamable HTTP エンドポイントを公開しており、これはリモート MCP サーバーで広く使われ、主要な MCP クライアントがサポートするトランスポートです。

コメント

他のリモート MCP サーバー

Adobe for creativity

Ideate, create, and deliver with Adobe pro tools

AIsa

AIsa is one key for 950+ data APIs across SEO and AI visibility, finance, social, web search, sales and agent mail — the go-to-market data stack behind prospecting, competitor research and brand monitoring. Five tools ra

A

AI-Ready Webpage Extractor (Apify)

Convert web pages to clean Markdown and retrieval-ready chunks with browser rendering support.

AdaptlyPost

AdaptlyPost: Schedule and publish social posts to Instagram, TikTok, YouTube, X, Facebook, LinkedIn, Pinterest, Threads, and Bluesky from any MCP client.

A

AIS Gateway

CVE prioritization using exploitation signals, plus agent heartbeat monitoring and state capsules. Some tools use API-key or x402 access.

広告掲載