insumer MCP server
com.insumermodel/insumerinsumermodel.comstreamable-httpv1.24.0Scanned
Wallet auth: send a wallet and conditions, get a signed boolean across 37 chains.
10 tools: 5 change things and 5 only read.
- Reads private data · 1
- Reads text others write · 10
- Can send data out · 0
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
5 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the insumer MCP server can do
The insumer MCP server is published by insumermodel.com, a domain the MCP Registry verified. It has 10 tools. It can create or change data (5 tools: insumer_attest, insumer_wallet_trust, insumer_batch_wallet_trust, insumer_check_discount and 1 more), but cannot delete data. 5 tools only read.
1 tool reads private data (insumer_list_merchants); 10 tools bring in text other people can write (insumer_attest, insumer_compliance_templates, insumer_wallet_trust and 7 more).
The fixed checks matched 3 findings (base64-blob and annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 13, 2026, version 1.24.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
10 tools
Changes things 5Claude Code: ask
insumer_attestEvaluate 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.Reads text others write2 findings
Why it is in this group
- The description's first verb is "evaluate": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The input schema at properties.conditions.items.properties.agentId.description contains a 42-character base64 string.
What this check looks forMatched text
inputSchema.properties.conditions.items.properties.agentId.description: "...t binding. Registry 0x8004A169FB4a3325136EB29fA0ceB6D2e539a432 on Base; chainId 84..."
- Warn
The input schema at properties.conditions.items.properties.delegationManager.description contains a 42-character base64 string.
What this check looks forMatched text
inputSchema.properties.conditions.items.properties.delegationManager.description: "...se (current default 0xdb9B1e94B5b69Df7e401DDbedE43491141047dB3). chainId 8453 only..."
Description, as the server wrote it 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.
Annotations the server declares
- title: Verify wallet conditions (signed)
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
insumer_batch_wallet_trustGenerate wallet trust fact profiles for up to 10 wallets in a single request.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "generate": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Batch wallet trust profiles (signed)
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
insumer_check_discountCalculate discount for a wallet at a merchant.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check a discount (free)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
insumer_validate_codeValidate an INSR-XXXXX discount code.Reads text others write1 finding
Why it is in this group
- The name "insumer_validate_code" says "validate": a word for reading.
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "insumer_validate_code" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "insumer_validate_code" says "validate": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Validate a discount code
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
insumer_wallet_trustGenerate a signed wallet trust fact profile for an EVM wallet: a curated set of presence checks organized into dimensions (stablecoins, governance, nfts, staking, institutional_sta…Reads text others writeNo findings
Why it is in this group
- The description's first verb is "generate": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Wallet trust profile (signed)
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 5Show 5 read-only tools
insumer_compliance_templatesList the compliance templates available for EAS attestation conditions.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: List compliance templates
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
insumer_get_merchantGet 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 o…Reads text others writeNo findings
Why it is in this group
- The name "insumer_get_merchant" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get a merchant profile
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
insumer_jwksGet 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.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "get" and "web": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get public signing keys
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
insumer_list_merchantsBrowse merchants in the public directory.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "insumer_list_merchants" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "browse" and "directory": it reads files.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
Description, as the server wrote it 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).
Annotations the server declares
- title: List merchants
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
insumer_list_tokensList the tokens and NFT collections listed in the Insumer registry.Reads text others writeNo findings
Why it is in this group
- The name "insumer_list_tokens" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: List registered tokens
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write10
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:40 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 5
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.insumermodel.com/mcp: tools/list returned 10 tools to an anonymous client, including insumer_attest (write), insumer_wallet_trust (write), insumer_batch_wallet_trust (write), insumer_check_discount (write), insumer_validate_code (write)
Findings
Matches of fixed checks, with the text they matched.
- Warninsumer_attest
The input schema at properties.conditions.items.properties.agentId.description contains a 42-character base64 string.
What this check looks forMatched text
inputSchema.properties.conditions.items.properties.agentId.description: "...t binding. Registry 0x8004A169FB4a3325136EB29fA0ceB6D2e539a432 on Base; chainId 84..."
- Warninsumer_attest
The input schema at properties.conditions.items.properties.delegationManager.description contains a 42-character base64 string.
What this check looks forMatched text
inputSchema.properties.conditions.items.properties.delegationManager.description: "...se (current default 0xdb9B1e94B5b69Df7e401DDbedE43491141047dB3). chainId 8453 only..."
The server marks "insumer_validate_code" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "insumer_validate_code" says "validate": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:insumer_attestChanges thingsinputSchema
Tools1 changed.~1 changedView diff
- Changed:insumer_attestChanges thingsinputSchema
Install
Pinned to version 1.24.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http insumer https://api.insumermodel.com/mcpclaude mcp add --transport http insumer https://api.insumermodel.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__insumer__insumer_compliance_templates",
"mcp__insumer__insumer_jwks",
"mcp__insumer__insumer_list_merchants",
"mcp__insumer__insumer_get_merchant",
"mcp__insumer__insumer_list_tokens"
],
"ask": [
"mcp__insumer__insumer_attest",
"mcp__insumer__insumer_wallet_trust",
"mcp__insumer__insumer_batch_wallet_trust",
"mcp__insumer__insumer_check_discount",
"mcp__insumer__insumer_validate_code"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as insumer. Review it before you use it.
Capability tags behind 10 rules
- mcp__insumer__insumer_attest untrusted-input
- mcp__insumer__insumer_compliance_templates untrusted-input
- mcp__insumer__insumer_wallet_trust untrusted-input
- mcp__insumer__insumer_batch_wallet_trust untrusted-input
- mcp__insumer__insumer_jwks untrusted-input
- mcp__insumer__insumer_list_merchants private-data, untrusted-input
- mcp__insumer__insumer_get_merchant untrusted-input
- mcp__insumer__insumer_list_tokens untrusted-input
- mcp__insumer__insumer_check_discount untrusted-input
- mcp__insumer__insumer_validate_code untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.insumermodel/insumer/verify?hash=69ebbd3e8db30219dec489d73c492cb9237e908c68b17bebd881c130a694254e" | jq -e '.changed == false'Pinned hash 69ebbd3e8db3, from Nov 13, 2026, 14:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.insumermodel/insumer/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.insumermodel/insumer)Source: MCP Registry · repository. Synced Nov 13, 2026, 14:17 UTC.
insumer MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the insumer MCP server safe?
- No scan can promise that. What its definitions show: 10 tools, 5 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the insumer MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the insumer MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the insumer MCP server have?
- 10 tools: 5 write, 5 read. insumer_attest, insumer_wallet_trust, insumer_batch_wallet_trust, insumer_check_discount, insumer_validate_code, insumer_compliance_templates, insumer_jwks, insumer_list_merchants and 2 more.
Does the insumer MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the insumer MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the insumer MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.