暗号学的に署名されたアテステーション(証明)を使用することで、AIエージェントが37のブロックチェーンネットワークにわたるオンチェーン条件やウォレットの真正性を検証できるようにします。
別名 insumerapi/mcp-server-insumer, mcp-server-insumer
- スター
- 2
- ツール
- 27
- ダウンロード数(30日間)
- —
- 最新バージョン
- 1.24.0
- 最終コミット
- 2026年11月13日
- ライセンス
- MIT
Insumer MCPとは
InsumerはMCPサーバーです。 暗号学的に署名されたアテステーション(証明)を使用することで、AIエージェントが37のブロックチェーンネットワークにわたるオンチェーン条件やウォレットの真正性を検証できるようにします。. 27個のツールを提供しており、insumer_setup, insumer_jwks, insumer_attestなどがあります。
プロジェクトのREADMEから生成された概要
Insumer MCP server について
Insumerは、AIエージェントが37の異なるブロックチェーンネットワークにわたるオンチェーン条件やウォレットの真正性を検証するための特化型インフラストラクチャを提供します。機密性の高い残高情報を公開する代わりに、このMCP serverは特定の条件が満たされているかを確認する、暗号学的に署名された真偽値(boolean)のアテステーションを返します。これにより、開発者は身元を明かしたりプライベートデータを露出させたりすることなく、コマース、加盟店検索、割引コード生成などの条件ベースのアクセスワークフローを構築できます。
ユーザーはAPIキーを提供することで、Claude Desktop、Cursor、Windsurfなどのクライアントからnpx経由でこのサーバーをローカルに実行できます。また、npmパッケージを実行できないプラットフォーム向けに、ホストされたエンドポイントとしても利用可能です。システムは、標準的なAPIキー、またはx402を使用してUSDCがチャージされたBaseウォレットを使用する従量課金モデルの2つの主要な認証方法をサポートしています。すべての結果には、長期的なセキュリティと完全性を確保するため、従来のECDSAと耐量子計算機暗号であるML-DSA-65の両方の署名が含まれています。
できること
- 1ウォレットの所有権と残高の検証AIエージェントが、特定のウォレットがブロックチェーン上の必要なトークン残高の閾値を満たしているかを確認できます。
- 2条件ベースのコマースアクセスの実装開発者はこのサーバーを使用して、ユーザーの割引適用資格の確認など、エージェントによるコマースワークフローに信頼性のチェックを追加できます。
- 3JWTによる安全なユーザー認証エージェントがJWT形式のアテステーションをリクエストすることで、標準的なミドルウェアがユーザーのオンチェーンステータスを検証できるようになります。
- 4APIキーの自動生成AIエージェントがメールアドレスのみを使用して無料のAPIキーを生成し、自身をセットアップできます。
プロジェクトの README から作成されています。すべてのユースケースは、その引用と照らし合わせて確認されています。
Insumer MCPのインストール方法
フォーマット検証日 2026年11月10日Cursor に追加Gooseに追加Claude CodeにInsumer MCPをインストール
$ claude mcp add --env 'INSUMER_API_KEY=<YOUR_INSUMER_API_KEY>' --env 'INSUMER_PAYMENT_KEY=<YOUR_INSUMER_PAYMENT_KEY>' mcp-server-insumer -- npx -y mcp-server-insumerCursorにInsumer MCPをインストール
~/.cursor/mcp.json
{
"mcpServers": {
"mcp-server-insumer": {
"command": "npx",
"args": [
"-y",
"mcp-server-insumer"
],
"env": {
"INSUMER_API_KEY": "<YOUR_INSUMER_API_KEY>",
"INSUMER_PAYMENT_KEY": "<YOUR_INSUMER_PAYMENT_KEY>"
}
}
}
}VS CodeにInsumer MCPをインストール
.vscode/mcp.json
{
"servers": {
"mcp-server-insumer": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mcp-server-insumer"
],
"env": {
"INSUMER_API_KEY": "<YOUR_INSUMER_API_KEY>",
"INSUMER_PAYMENT_KEY": "<YOUR_INSUMER_PAYMENT_KEY>"
}
}
}
}VS Code CLIにInsumer MCPをインストール
$ code --add-mcp '{"name":"mcp-server-insumer","type":"stdio","command":"npx","args":["-y","mcp-server-insumer"],"env":{"INSUMER_API_KEY":"<YOUR_INSUMER_API_KEY>","INSUMER_PAYMENT_KEY":"<YOUR_INSUMER_PAYMENT_KEY>"}}'Claude DesktopにInsumer MCPをインストール
claude_desktop_config.json
{
"mcpServers": {
"mcp-server-insumer": {
"command": "npx",
"args": [
"-y",
"mcp-server-insumer"
],
"env": {
"INSUMER_API_KEY": "<YOUR_INSUMER_API_KEY>",
"INSUMER_PAYMENT_KEY": "<YOUR_INSUMER_PAYMENT_KEY>"
}
}
}
}CodexにInsumer MCPをインストール
$ codex mcp add mcp-server-insumer --env 'INSUMER_API_KEY=<YOUR_INSUMER_API_KEY>' --env 'INSUMER_PAYMENT_KEY=<YOUR_INSUMER_PAYMENT_KEY>' -- npx -y mcp-server-insumerCodex config.tomlにInsumer MCPをインストール
~/.codex/config.toml
[mcp_servers.mcp-server-insumer] command = "npx" args = ["-y", "mcp-server-insumer"] [mcp_servers.mcp-server-insumer.env] INSUMER_API_KEY = "<YOUR_INSUMER_API_KEY>" INSUMER_PAYMENT_KEY = "<YOUR_INSUMER_PAYMENT_KEY>"
Gemini CLIにInsumer MCPをインストール
$ gemini mcp add -s user -e 'INSUMER_API_KEY=<YOUR_INSUMER_API_KEY>' -e 'INSUMER_PAYMENT_KEY=<YOUR_INSUMER_PAYMENT_KEY>' mcp-server-insumer npx -- -y mcp-server-insumerGemini settings.jsonにInsumer MCPをインストール
~/.gemini/settings.json
{
"mcpServers": {
"mcp-server-insumer": {
"command": "npx",
"args": [
"-y",
"mcp-server-insumer"
],
"env": {
"INSUMER_API_KEY": "<YOUR_INSUMER_API_KEY>",
"INSUMER_PAYMENT_KEY": "<YOUR_INSUMER_PAYMENT_KEY>"
}
}
}
}Insumer MCPツール 27
READMEから検出insumer_setupinsumer_jwksinsumer_attestinsumer_compliance_templatesinsumer_wallet_trustinsumer_batch_wallet_trustinsumer_verifyinsumer_list_merchantsinsumer_get_merchantinsumer_list_tokensinsumer_check_discountinsumer_buy_key
| insumer_setup | — | |
| insumer_jwks | — | |
| insumer_attest | — | |
| insumer_compliance_templates | — | |
| insumer_wallet_trust | — | |
| insumer_batch_wallet_trust | — | |
| insumer_verify | — | |
| insumer_list_merchants | — | |
| insumer_get_merchant | — | |
| insumer_list_tokens | — | |
| insumer_check_discount | — | |
| insumer_buy_key | — |
27個のツールをすべて表示ツールを折りたたむ
insumer_creditsinsumer_buy_creditsinsumer_confirm_paymentinsumer_create_merchantinsumer_merchant_statusinsumer_configure_tokensinsumer_configure_nftsinsumer_configure_settingsinsumer_publish_directoryinsumer_buy_merchant_creditsinsumer_request_domain_verificationinsumer_verify_domaininsumer_acp_discountinsumer_ucp_discountinsumer_validate_code
| insumer_credits | — | |
| insumer_buy_credits | — | |
| insumer_confirm_payment | — | |
| insumer_create_merchant | — | |
| insumer_merchant_status | — | |
| insumer_configure_tokens | — | |
| insumer_configure_nfts | — | |
| insumer_configure_settings | — | |
| insumer_publish_directory | — | |
| insumer_buy_merchant_credits | — | |
| insumer_request_domain_verification | — | |
| insumer_verify_domain | — | |
| insumer_acp_discount | — | |
| insumer_ucp_discount | — | |
| insumer_validate_code | — |
設定
INSUMER_API_KEYシークレットInsumerAPI key (starts with insr_live_). Either this or INSUMER_PAYMENT_KEY.
INSUMER_PAYMENT_KEYシークレットPrivate key of a throwaway Base wallet holding a little USDC, for pay-per-call via x402 when no API key is set. Each quote is checked before signing.
INSUMER_MAX_PAYMENT_USDCMost USDC the server will pay for one call in pay-per-call mode (default 3).
| 名前 | 説明 | 種類 |
|---|---|---|
| INSUMER_API_KEY | InsumerAPI key (starts with insr_live_). Either this or INSUMER_PAYMENT_KEY. | シークレット |
| INSUMER_PAYMENT_KEY | Private key of a throwaway Base wallet holding a little USDC, for pay-per-call via x402 when no API key is set. Each quote is checked before signing. | シークレット |
| INSUMER_MAX_PAYMENT_USDC | Most USDC the server will pay for one call in pay-per-call mode (default 3). |
自動チェック
実行日 2026年11月12日完全なレポート →自動チェックに合格しました。これはセキュリティ監査ではありません。コードを読み、サーバーに必要最小限のアクセス権を与えてください。 チェックの仕組み
- ソースリポジトリがリンクされており、アクセス可能合格
- オープンソースライセンス (OSI)合格
- 過去1年以内にコミットまたはリリースあり合格
- パッケージ名が有名なパッケージに酷似していない合格
- リモートエンドポイントがHTTPSを使用合格
- 破壊的なツールがラベル付けされている合格
- モデルへの隠れた指示がない合格
- パッケージおよびその依存関係に重大な勧告なし合格
README
GitHubで見るmcp-server-insumer
MCP server for InsumerAPI: condition-based access infrastructure. Send a wallet and conditions, get a signed boolean across 37 chains. No balances exposed, no identity required. Every result is signed and checkable offline against the published keys, and on EVM chains an optional Merkle proof lets the verifier check the balance against the block header without trusting the API.
Enables AI agents (Claude Desktop, Cursor, Windsurf, and any MCP-compatible client) to add condition-based access to any workflow: verify on-chain conditions, discover merchants, generate signed discount codes, and onboard new merchants.
In production: AsterPay, a non-custodial payments orchestrator settling through licensed EU partners, uses InsumerAPI attestations in its live ERC-8183 agentic-commerce trust checks. Case study.
Also available as: LangChain (26 tools, PyPI) | ElizaOS (10 actions, npm) | OpenAI GPT (GPT Store) | insumer-verify (client-side verification, npm)
Full AI Agent Verification API guide: covers all 37 chains, trust profiles, commerce protocols, and signature verification.
Quick Start
Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"insumer": {
"command": "npx",
"args": ["-y", "mcp-server-insumer"],
"env": {
"INSUMER_API_KEY": "insr_live_..."
}
}
}
}
Cursor / Windsurf
Add to your MCP settings:
{
"insumer": {
"command": "npx",
"args": ["-y", "mcp-server-insumer"],
"env": {
"INSUMER_API_KEY": "insr_live_..."
}
}
}
Get a key: just an email, no dashboard, no password
Three paths, all give you a working insr_live_... key in seconds with 10 free verifications plus 100 requests a day. One free key per email.
Option A: let your agent do it. Start the server without a key. Your AI agent can call the insumer_setup tool with your email to generate a free key instantly. Add it to your config and restart.
Option B: terminal.
curl -s -X POST https://api.insumermodel.com/v1/keys/create \
-H "Content-Type: application/json" \
-d '{"email": "you@example.com", "appName": "MCP Server", "tier": "free"}'
Option C: browser. Enter your email on insumermodel.com and the key appears inline.
Set it as INSUMER_API_KEY in your config.
Already have a key? Manage usage, top up, or upgrade at insumermodel.com/developers/account/.
Option D: pay per call with x402 (no key at all)
Instead of a key, set INSUMER_PAYMENT_KEY to a throwaway Base wallet funded with a few dollars of USDC. Metered calls (insumer_attest, insumer_wallet_trust, insumer_batch_wallet_trust) are then paid inline via x402: the server requests a price, signs an EIP-3009 USDC authorization on Base, and retries. No signup, no credits, no dashboard.
{
"mcpServers": {
"insumer": {
"command": "npx",
"args": ["-y", "mcp-server-insumer"],
"env": { "INSUMER_PAYMENT_KEY": "0x<throwaway-wallet-private-key>" }
}
}
}
- Base USDC only; the wallet needs USDC but no ETH (settlement is gasless).
- Each call spends a few cents (attest $0.05, trust $0.15). Use a dedicated throwaway wallet funded with a small amount, never a wallet holding meaningful funds.
- Every quote is checked before the wallet signs. The server pays only InsumerAPI's own receiving address (
0xee432065474D2C852700f74e3fD81e2Bcc16a3D4, or the address it quoted before 2026-10-19,0xAd982CB19aCCa2923Df8F687C0614a7700255a23), only in USDC on Base, and never more than the cap: $3.00 per call by default, the price of the largest call today (a 10-wallet trust batch with Merkle proofs). Anything else is refused and nothing is signed. SetINSUMER_MAX_PAYMENT_USDCto change the cap, e.g."0.25"if you only attest. The cheapest call is $0.05, so a cap below that refuses every paid call (the server warns at startup). A malformed value turns pay-per-call off rather than falling back to the default. - If both
INSUMER_API_KEYandINSUMER_PAYMENT_KEYare set, the key (credits) is used.
Hosted endpoint (no install)
The same server runs at https://api.insumermodel.com/mcp over MCP streamable HTTP, for clients that connect by URL: ChatGPT plugins and developer-mode connectors, claude.ai custom connectors, and hosted agent platforms that cannot run an npm package. Paste the URL; there is nothing to configure.
It is shared and anonymous, so it serves the ten tools that make sense without a caller identity (HOSTED_TOOLS: signing keys, attest, compliance templates, wallet trust and batch trust, the merchant and token directories, the free discount check, code validation), and the metered tools share one free daily allowance. Past it, a call is refused with a pointer here. For your own allowance, key and credit management, or the merchant tools, run the package locally with your key as above.
To host the server yourself, build it and run node build/http.js with INSUMER_API_KEY set (PORT, INSUMER_HOSTED_TOOLS and INSUMER_DAILY_CAP are optional), or embed it: createInsumerServer(options) from the package root returns a configured server for any transport.
What You Get Back
When your agent calls insumer_attest, you get an ECDSA-signed attestation:
{
"ok": true,
"data": {
"attestation": {
"id": "ATST-A7C3E1B2D4F56789",
"pass": true,
"results": [
{
"condition": 0,
"met": true,
"label": "USDC >= 1000 on Ethereum",
"type": "token_balance",
"chainId": 1,
"evaluatedCondition": {
"chainId": 1,
"contractAddress": "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48",
"operator": "gte",
"threshold": "1000",
"type": "token_balance"
},
"conditionHash": "0x8a3b...",
"blockNumber": "0x1799043",
"blockTimestamp": "2026-03-26T20:04:23.000Z"
}
],
"passCount": 1,
"failCount": 0,
"attestedAt": "2026-02-28T12:34:57.000Z",
"expiresAt": "2026-02-28T13:04:57.000Z"
},
"sig": "NgA7BO8SAildiTrgIQY2UyXsBrySZknkP85pT2Zqv8Hq0KsCsB8DRFVMkXgnXtCXrbb726Is6k4LyyBYU+f/Pw==",
"kid": "insumer-attest-v2",
"pqSig": "<base64 ML-DSA-65 signature>",
"pqKid": "insumer-attest-pq1"
},
"meta": {
"version": "1.0",
"timestamp": "2026-02-28T12:34:57.000Z",
"creditsRemaining": 99,
"creditsCharged": 1
}
}
The sig is an ECDSA P-256 signature (base64, P1363 r||s, 88 characters). The kid identifies the key and selects the signed bytes: insumer-attest-v2 signs "insumer.attestation.v2\n" + canonical_json({v: 2, id, pass, results, attestedAt}) (keys sorted at every level); insumer-attest-v1 signs the bare JSON.stringify of {id, pass, results, attestedAt} in insertion order. Every attest and trust response is signed twice: ES256 and a post-quantum ML-DSA-65 signature, pqSig and pqKid (over the post-quantum domain tag plus the same classical preimage the kid selects; pqJwt beside jwt), added beside sig and kid without changing them. The conditionHash is a SHA-256 of the exact condition logic that was evaluated.
No balances. No amounts. Just a cryptographically signed true/false.
For XRPL conditions, results include ledgerIndex, ledgerHash (validated ledger hash), and trustLineState: { frozen: boolean } instead of blockNumber/blockTimestamp. Native XRP conditions include ledgerIndex and ledgerHash but not trustLineState. Frozen trust lines cause met: false.
Wallet Auth (JWT)
Add format: "jwt" to the insumer_attest tool parameters to receive the attestation as a standard JWT bearer token:
{
"wallet": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
"conditions": [ ... ],
"format": "jwt"
}
The response includes an additional jwt field containing an ES256-signed JWT, and beside it a pqJwt sibling (a compact JWS with alg ML-DSA-65 carrying the same claims, signed under insumer-attest-pq1). The jwt token is verifiable by any standard JWT library via the JWKS endpoint at GET /v1/jwks, which makes it compatible with Kong, Nginx, Cloudflare Access, AWS API Gateway, and other middleware that accepts JWT bearer tokens.
Verify the Response
Your agent gets the attestation. Your application should verify it. Install insumer-verify (also on PyPI for Python: pip install insumer-verify, same checks, same 27 published test vectors):
npm install insumer-verify
import { verifyAttestation } from "insumer-verify";
// attestationResponse = the full API envelope {ok, data: {attestation, sig, kid, pqSig, pqKid}, meta}
// Do NOT pass attestationResponse.data; the function expects the outer envelope
const result = await verifyAttestation(attestationResponse, {
jwksUrl: "https://insumermodel.com/.well-known/jwks.json",
maxAge: 120, // reject if block data is older than 2 minutes
});
if (result.valid) {
// Signature verified, condition hashes match, not expired
const pass = attestationResponse.data.attestation.pass;
console.log(`Attestation ${pass ? "passed" : "failed"} all conditions`);
} else {
console.log("Verification failed:", result.checks);
}
This reports five independent verdicts: ECDSA signature, condition hash integrity, block freshness, attestation expiry, and the post-quantum signature (insumer-verify 1.8.1+ reports it as verified, refuted, absent, or unverifiable). Zero runtime dependencies, uses Web Crypto API.
Tools (27)
Setup (free, no auth)
| Tool | Description |
|---|---|
insumer_setup |
Generate a free API key instantly. Takes an email, returns an insr_live_... key with 10 free verifications plus 100 requests a day. No credit card required. |
Key Discovery (free)
| Tool | Description |
|---|---|
insumer_jwks |
Get the JWKS: five entries over two keys. The ECDSA P-256 key under insumer-attest-v1, insumer-attest-v2, and insumer-trust-v2, followed by the ML-DSA-65 post-quantum key under two RFC 9964 AKP entries, insumer-attest-pq1 and insumer-trust-pq1. Match by the kid (or pqKid) on the response, never by position. |
On-Chain Verification (cost credits)
token_balancethresholds are decimal strings. Passthresholdas"100", not100. Keys created from 2026-06-10 sign withkid: insumer-attest-v2, which preserves full precision and rejects a JSON number with a400. Theinsumer_attesttool accepts a number or string and coerces to the canonical string; olderinsumer-attest-v1keys accept either.
| Tool | Description |
|---|---|
insumer_attest |
Verify on-chain conditions (token balances, NFT ownership, EAS attestations, Farcaster identity, evm_view_call for arbitrary boolean view functions, ratio_to_amount for self-scaling agent-spend limits and ratio_to_supply for share-of-supply rules; all three EVM only, plus erc8004_agent for ERC-8004 agent registration and erc7710_delegation for MetaMask-framework delegation validity, both on Base, and account_code for the code state of the wallet address itself on an EVM chain: expect is none for a plain key account, eip7702 for an EIP-7702 delegation designator, optionally to a given delegate, or contract for any other code; the answer is met or not met, and the code and the delegation target are never returned). Returns ECDSA-signed boolean with kid, evaluatedCondition, conditionHash (SHA-256), and blockNumber/blockTimestamp. 1 credit. Optional proof: "merkle" for EIP-1186 Merkle proofs (2 credits): a balance-slot storage proof for token balances, an account proof (subject account_balance) for the native coin, an account proof (subject account_code) for account_code, and a revocation-slot proof (subject delegation_revocation) for erc7710_delegation. |
insumer_compliance_templates |
List available EAS compliance templates (Coinbase Verifications on Base, Gitcoin Passport on Optimism). Free. |
insumer_wallet_trust |
Generate ECDSA-signed wallet trust fact profile. 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 optional Solana, XRPL, Bitcoin, and Tron wallets (Stellar and Sui wallets switch on rows inside the base dimensions). Every check is a presence check; the account dimension's two rows per chain (contract code, EIP-7702 delegation, on Ethereum, Base, Arbitrum, Optimism and Polygon) are present or not present. Dimensions arrive in a fixed order: the base dimensions as listed, then any of solana, xrpl, bitcoin and tron that were switched on. The signed conditionSetVersion (currently 2026-10-08) names the check list; log it, never reject on it. 3 credits (6 with merkle; the premium is refunded whenever no proof is delivered). |
insumer_batch_wallet_trust |
Batch trust profiles for up to 10 wallets. Each wallet object supports optional solanaWallet, xrplWallet, bitcoinWallet, tronWallet, stellarWallet, and suiWallet. Faster than sequential calls. Partial success supported. 3 credits/wallet (6 with merkle). The text is a per-wallet summary by default (dimensions in their fixed order, identical for every wallet; the account dimension's checks are present rather than held) and the complete signed profiles are in structuredContent; detail: "full" puts them in the text too (set it on the call: profiles cannot be fetched again). |
insumer_verify |
Create signed discount code (INSR-XXXXX, 30-min expiry) for a wallet at a merchant. A code that carries a discount costs 1 credit from the API key that owns the store; a 0% result is free. A caller using another key is not charged. Optional walletProof proves you control the EVM wallet: full discount, no daily limit. |
Discovery (free)
| Tool | Description |
|---|---|
insumer_list_merchants |
Browse the merchant directory. Filter by token, verification status. |
insumer_get_merchant |
Get full public merchant profile. |
insumer_list_tokens |
List the tokens and NFTs listed in the Insumer registry. Filter by chain, symbol, type. A directory, not the list of what can be checked: an attestation checks any token on a supported chain, and NFTs on EVM chains, Solana and XRPL. |
insumer_check_discount |
Calculate discount for a wallet at a merchant. |
Credits & Keys
| Tool | Description |
|---|---|
insumer_buy_key |
Buy a new API key with USDC (no auth required). Agent-friendly: no email needed, the sending wallet becomes the key's identity and signs a fixed text naming the payment (senderSignature; a call without it returns the text). One key per wallet. amount required, minimum $5. Volume discounts: $0.04–$0.02/call. Supported chains: Ethereum, Base, Polygon, Arbitrum, Optimism, BNB Chain, Avalanche, Solana. Non-refundable. |
insumer_credits |
Check credit balance and tier. |
insumer_buy_credits |
Buy verification credits with USDC. amount required, minimum $5. Volume discounts: $0.04–$0.02/call. Supported chains: Ethereum, Base, Polygon, Arbitrum, Optimism, BNB Chain, Avalanche, Solana. Non-refundable. First purchase registers the sending wallet; subsequent purchases must come from it or include updateWallet: true. Registering or replacing the wallet takes senderSignature from the wallet that sent the payment. |
insumer_confirm_payment |
Confirm USDC payment for a discount code. |
Merchant Onboarding (owner-only)
| Tool | Description |
|---|---|
insumer_create_merchant |
Create new merchant, owned by the key that creates it. No balance of its own: that key pays for its codes, scans and taps. |
insumer_merchant_status |
Get full private merchant details. |
insumer_configure_tokens |
Set token discount tiers. Tier discounts are whole numbers from 1 to 50. Tokens can carry a display name and logo; the own token takes enabled. |
insumer_configure_nfts |
Set NFT collections: a whole-number discount from 1 to 50, or benefitType: "recognition" for recognition only. enabled: false keeps a collection switched off. |
insumer_configure_settings |
Set discount mode, cap, the terms for wallets without proof of control, USDC payments. |
insumer_publish_directory |
Publish merchant to public directory. |
insumer_buy_merchant_credits |
Kept for compatibility. A store has no balance of its own: a USDC payment submitted here adds regular credits to the API key that owns the store, at a flat 25 credits per $1 (insumer_buy_credits has the volume tiers). amount required, minimum $5. Owner only. Non-refundable. First purchase registers the sending wallet; subsequent purchases must come from it or include updateWallet: true. Registering or replacing the wallet takes senderSignature from the wallet that sent the payment. |
Domain Verification (owner-only)
| Tool | Description |
|---|---|
insumer_request_domain_verification |
Request a verification token for a merchant's domain. Returns token and 3 methods (DNS TXT, meta tag, file upload). |
insumer_verify_domain |
Complete domain verification after placing the token. Verified merchants get a trust badge. |
Commerce Protocol Integration
| Tool | Description |
|---|---|
insumer_acp_discount |
Check discount eligibility in OpenAI/Stripe ACP format. Returns coupon objects and per-item allocations. A code that carries a discount costs the store's owner key 1 credit; a 0% result is free. A caller using another key is not charged. |
insumer_ucp_discount |
Check discount eligibility in Google UCP format. Returns title, extension field, and applied array. A code that carries a discount costs the store's owner key 1 credit; a 0% result is free. A caller using another key is not charged. |
insumer_validate_code |
Validate an INSR-XXXXX discount code. Returns validity, discount percent, expiry. Free, no auth. |
Pricing
Tiers: Free (10 free verifications plus 100 requests a day) | Pro $29/mo (1,000 credits/mo, 10,000/day) | Enterprise $99/mo (5,000 credits/mo, 100,000/day)
Volume discounts: $5–$99 = $0.04/call (25 credits/$1) · $100–$499 = $0.03 (33/$1, 25% off) · $500+ = $0.02 (50/$1, 50% off)
Key and credit purchases are paid in USDC only. Receiving addresses:
- USDC on Ethereum, Base, Polygon, Arbitrum, Optimism or Avalanche:
0xee432065474D2C852700f74e3fD81e2Bcc16a3D4 - USDC on BNB Chain:
0xAd982CB19aCCa2923Df8F687C0614a7700255a23(USDC sent to it on the other EVM chains is also accepted during the changeover) - USDC on Solana:
8fyEGM5tRjMocKQWaVXyM2XvvnTxR3sWdrYtug2zeLX4(USDC sent to6a1mLjefhvSJX1sEX8PTnionbE9DqoYjU6F6bNkT4Ydris also accepted during the changeover)
Supported payment chains: Ethereum, Base, Polygon, Arbitrum, Optimism, BNB Chain, Avalanche, Solana. USDT and other tokens are refused and not credited; tokens sent on unsupported chains cannot be recovered. All purchases are final and non-refundable. Full pricing →
Sender signature. A purchase that binds a key to a wallet (every key purchase, a credit purchase on a key with no registered wallet, or updateWallet: true from a different wallet) takes senderSignature: the wallet that sent the payment signs this exact text, five lines joined by \n with no trailing newline:
api.insumermodel.com
Confirm the wallet that sent this payment.
Purpose: key purchase
Chain: eip155:8453
Transaction: 0x<transaction hash, lowercase hex>
Purpose is credit purchase for a credit purchase; Chain is eip155:<chainId> on an EVM chain or solana (with the Solana signature as given). Call once without senderSignature and the 400 returns the exact text. EVM wallets sign with personal_sign (EIP-191, 0x hex; smart wallets are checked with ERC-1271); Solana wallets sign with signMessage (ed25519, base58 or base64). A 403 means the signature is not from the wallet that sent the payment; a 503 means a smart-wallet check could not complete and the payment was not used.
Handling rpc_failure Errors
If the API cannot reach one or more blockchain data sources after retries, insumer_attest, insumer_wallet_trust, insumer_verify, insumer_acp_discount, insumer_ucp_discount and insumer_check_discount return ok: false with error code rpc_failure. No signature, no JWT, no credits charged. insumer_batch_wallet_trust answers normally and carries an error entry for any wallet whose reads did not complete, beside the wallets that were signed. This is a retryable error: the MCP client should retry after a short delay (2-5 seconds).
Important: rpc_failure is NOT a verification failure. Do not treat it as pass: false. It means the data source was temporarily unavailable and the API refused to sign an unverified result.
Supported Chains (37)
31 EVM chains + Solana + XRP Ledger + Bitcoin + Tron + Stellar + Sui. Includes Ethereum, Base, Polygon, Arbitrum, Optimism, BNB Chain, Avalanche, XDC, Robinhood Chain, Arc, and 21 more EVM. Full list →
Also Available As
- Claude Code Skill:
git clone https://github.com/insumerapi/insumer-skill.git ~/.claude/skills/insumer(GitHub · Smithery), for writing wallet auth into your own projects from inside Claude Code. This MCP server gives an agent runtime access to the API; insumer-skill helps developers author integration code at build time. Different surfaces, same primitive. - ElizaOS Plugin:
@insumermodel/plugin-eliza(npm) - LangChain (Python):
pip install langchain-insumer(PyPI) - OpenAI GPT: InsumerAPI Wallet Auth (GPT Store)
- Verifier (offline JWKS):
npm install insumer-verify(npm, source)
Development
npm install
npm run build
# Test with MCP Inspector
npx @modelcontextprotocol/inspector node build/index.js
License
MIT
Insumer MCPのよくある質問
Insumer MCPをClaude Codeに追加するには
ターミナルでclaude mcp add --env 'INSUMER_API_KEY=<YOUR_INSUMER_API_KEY>' --env 'INSUMER_PAYMENT_KEY=<YOUR_INSUMER_PAYMENT_KEY>' mcp-server-insumer -- npx -y mcp-server-insumerを実行します。すべてのプロジェクトで利用するには--scope userを追加します。
Insumer MCPをCursorに追加するには
~/.cursor/mcp.jsonを開き、上記のインストールセクションに示すCursor設定を使ってmcpServersの下にサーバーを追加します。
Insumer MCPが提供するツールは
27個のツールを提供しており、insumer_setup, insumer_jwks, insumer_attest, insumer_compliance_templates, insumer_wallet_trustなどがあります。
APIキーはどのように取得できますか?
insumer_setupツールを使用してメールアドレスから即座に無料キーを生成するか、curlコマンド、またはInsumerのウェブサイトから取得できます。
APIキーなしで使用できますか?
はい、INSUMER_PAYMENT_KEY環境変数を使用してUSDCがチャージされたBaseウォレットを用意すれば、x402による従量課金制で利用可能です。
対応しているチェーンの数は?
本サービスは37種類の異なるブロックチェーンネットワークでの検証をサポートしています。