Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.insumermodel/insumer

REMOTE · API.INSUMERMODEL.COM · 2 COMPONENTS · SCANNED OCT 10

Wallet auth: send a wallet and conditions, get a signed boolean across 37 chains.

+2 this week 76 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security83
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3253 tokens (~325/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the com.insumermodel/insumer MCP server?

com.insumermodel/insumer is a hosted endpoint at https://api.insumermodel.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.insumermodel.com

# add to Claude Code
claude mcp add --transport http com-insumermodel-insumer 'https://api.insumermodel.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-insumermodel-insumer": {
      "url": "https://api.insumermodel.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-insumermodel-insumer": {
      "type": "http",
      "url": "https://api.insumermodel.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-insumermodel-insumer]
url = "https://api.insumermodel.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-insumermodel-insumer": {
      "type": "remote",
      "url": "https://api.insumermodel.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-insumermodel-insumer --url 'https://api.insumermodel.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-insumermodel-insumer:
    url: "https://api.insumermodel.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-insumermodel-insumer": {
      "Transport": "http",
      "Url": "https://api.insumermodel.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-insumermodel-insumer -t streamable-http -u 'https://api.insumermodel.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-insumermodel-insumer": {
      "type": "http",
      "url": "https://api.insumermodel.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 10 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Oct 26 +1
    • Tool “insumer_wallet_trust” rewrote its description, which is the text the model reads security
    • Tool “insumer_list_tokens” rewrote its description, which is the text the model reads security
    • Tool “insumer_attest” rewrote its description, which is the text the model reads security
    • Tool “insumer_batch_wallet_trust” rewrote its description, which is the text the model reads security
    • Schema quality: 212 → 325 ▼ functional
    • Server version: 1.18.0 → 1.21.0 functional
    • “insumer_batch_wallet_trust” added an optional parameter “detail” cosmetic
    • “insumer_wallet_trust” reworded the description of “proof” cosmetic
    • “insumer_attest” reworded the description of “proof” cosmetic
    • “insumer_attest” reworded the description of “stellarWallet” cosmetic
  • 3 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
    • Tool “insumer_attest” now declares an output schema ▲ functional
    • Tool “insumer_batch_wallet_trust” now declares an output schema ▲ functional
    • Tool “insumer_check_discount” now declares an output schema ▲ functional
    • Tool “insumer_compliance_templates” now declares an output schema ▲ functional
    • Tool “insumer_get_merchant” now declares an output schema ▲ functional
    • Tool “insumer_jwks” now declares an output schema ▲ functional
    • Tool “insumer_list_merchants” now declares an output schema ▲ functional
    • Tool “insumer_list_tokens” now declares an output schema ▲ functional
    • Tool “insumer_validate_code” now declares an output schema ▲ functional
    • Tool “insumer_wallet_trust” now declares an output schema ▲ functional
    • First check of Tool coverage: 100 functional
    • Server version: 1.15.0 → 1.16.0 functional
    • Tool “insumer_attest” changed its title: Verify wallet conditions (signed) cosmetic
    • Tool “insumer_batch_wallet_trust” changed its title: Batch wallet trust profiles (signed) cosmetic
    • Tool “insumer_check_discount” changed its title: Check a discount (free) cosmetic
    • Tool “insumer_compliance_templates” changed its title: List compliance templates cosmetic
    • Tool “insumer_get_merchant” changed its title: Get a merchant profile cosmetic
    • Tool “insumer_jwks” changed its title: Get public signing keys cosmetic
    • Tool “insumer_list_merchants” changed its title: List merchants cosmetic
    • Tool “insumer_list_tokens” changed its title: List registered tokens cosmetic
    • Tool “insumer_validate_code” changed its title: Validate a discount code cosmetic
    • Tool “insumer_wallet_trust” changed its title: Wallet trust profile (signed) cosmetic
  • 2 Oct 26 73

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 10 Oct 2026 · Probed https://api.insumermodel.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=insumermodel.com CN=WE1,O=Google Trust Services,C=US 24 Aug 2026 22 Nov 2026 ECDSA 256 ECDSA-SHA256 98b55d42aa051bbf1311468bbbb9ffe7
SANs: insumermodel.com, api.insumermodel.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of api.insumermodel.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
insumermodel.com. present 2371 13 Verified
api.insumermodel.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.insumermodel.com/mcp Verified 200
http (plaintext) http://api.insumermodel.com/mcp HTTPS enforced 301 https://api.insumermodel.com/mcp
MCP tools · 10 exposed · ~3,253 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
insumer_attest ~1,192

Verify 1-10 on-chain conditions for a wallet and return a signed yes or no for each, never the balance. Condition types: token_balance, nft_ownership, eas_attestation (raw schemaId or a compliance template such as Coinbase Verifications or Gitcoin Passport), farcaster_id (IdRegistry on Optimism), evm_view_call (a single-address-argument view function returning bool), ratio_to_amount (balance >= multiple * amount), ratio_to_supply (balance / totalSupply >= minFraction, ERC-20 only), erc8004_agent (registered ERC-8004 agent on Base), erc7710_delegation (a signed MetaMask-framework delegation from principal to agent is currently valid on Base; spend, target and call limits are reported as declaredLimits, not simulated), and account_code (the code state of the wallet address itself at the anchored block on an EVM chain: expect '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). Chains: EVM chains plus Solana, XRPL, Bitcoin, Tron, Stellar and Sui; Bitcoin, Tron, Stellar and Sui support token_balance only. Responses are ECDSA-signed with a kid identifying the key and carry a post-quantum companion signature; each result includes evaluatedCondition, a SHA-256 conditionHash, and the block (EVM), ledger (XRPL, Stellar) or checkpoint (Sui) it was read at. proof: 'merkle' adds EIP-1186 proofs on supported EVM chains: a balance-slot storage proof for token_balance and ratio_to_amount (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. Attestations with a delegation condition expire in 5 minutes instead of 30; a failed delegation result carries failReason. Costs 1 credit (2 with proof). An rpc_failure error (503) means a read did not complete…

NameTypeReqDescription
bitcoinWalletstring–Bitcoin address (P2PKH, P2SH, bech32, or Taproot). For verifying native BTC balance. Use chainId 'bitcoin' with contractAddress 'native'.
conditionsarrayyes1-10 on-chain conditions to verify
declaredLimitsstring–Set to 'omit' to leave decoded caveat limits out of the signed results of erc7710_delegation conditions, so a forwarded attestation does not carry the principal's spending ceiling. met, delegationHas…
formatstring–Set to 'jwt' to include a Wallet Auth by InsumerAPI token (ES256-signed JWT) in the response, with its ML-DSA-65 sibling pqJwt beside it. The jwt is verifiable by any standard JWT library using JWKS…
proofstring–Set to 'merkle' for EIP-1186 Merkle proofs (2 credits, refunded to 1 when no proof is delivered). For token_balance or ratio_to_amount against an ERC-20, a storage proof of the balance slot (no subje…
solanaWalletstring–Solana wallet address (base58)
stellarWalletstring–Stellar wallet address (G-prefixed). For verifying XLM or trustline assets (USDC, BENJI, etc.). Use chainId 'stellar' with the asset issuer's G-address as contractAddress and pass assetCode (e.g. 'US…
suiWalletstring–Sui wallet address (0x + 64 hex chars). For verifying SUI or other Sui coins (e.g. USDC). Use chainId 'sui' with the Sui coin type as contractAddress: '0x2::sui::SUI' for native SUI, or the full coin…
tronWalletstring–Tron wallet address (T-prefixed, base58). For verifying TRX or TRC20 tokens (USDT-TRC20). Use chainId 'tron'.
walletstring–EVM wallet address (0x...)
xrplWalletstring–XRPL wallet address (r-address). For verifying XRP, trust line tokens (RLUSD, USDC), or NFTs on XRP Ledger.
NameTypeReqDescription
data––The endpoint's payload: a signed attestation, trust profile, discount, merchant or token records
error––Error details when ok is false
itemsarray–The result when the endpoint returns a JSON array
keysarray–JWKS entries (insumer_jwks)
message––A plain-text result (insumer_setup), or a message from the API
meta––Response metadata such as version and timestamp
okboolean–true when the API call succeeded

No examples provided.

insumer_batch_wallet_trust ~578

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.

NameTypeReqDescription
detailstring–'summary' (default): the text is a short summary per wallet and the complete signed profiles are in structuredContent. 'full': the complete signed profiles as text too, tens of thousands of character…
proofstring–Set to 'merkle' for EIP-1186 Merkle storage proofs on all wallets (6 credits/wallet).
walletsarrayyes1-10 wallet entries to profile
NameTypeReqDescription
data––The endpoint's payload: a signed attestation, trust profile, discount, merchant or token records
error––Error details when ok is false
itemsarray–The result when the endpoint returns a JSON array
keysarray–JWKS entries (insumer_jwks)
message––A plain-text result (insumer_setup), or a message from the API
meta––Response metadata such as version and timestamp
okboolean–true when the API call succeeded

No examples provided.

insumer_check_discount ~179

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.

NameTypeReqDescription
merchantstringyesMerchant ID
solanaWalletstring–Solana wallet address (base58)
walletstring–EVM wallet address (0x...)
xrplWalletstring–XRPL wallet address (r-address)
NameTypeReqDescription
data––The endpoint's payload: a signed attestation, trust profile, discount, merchant or token records
error––Error details when ok is false
itemsarray–The result when the endpoint returns a JSON array
keysarray–JWKS entries (insumer_jwks)
message––A plain-text result (insumer_setup), or a message from the API
meta––Response metadata such as version and timestamp
okboolean–true when the API call succeeded

No examples provided.

insumer_compliance_templates ~81

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
data––The endpoint's payload: a signed attestation, trust profile, discount, merchant or token records
error––Error details when ok is false
itemsarray–The result when the endpoint returns a JSON array
keysarray–JWKS entries (insumer_jwks)
message––A plain-text result (insumer_setup), or a message from the API
meta––Response metadata such as version and timestamp
okboolean–true when the API call succeeded

No examples provided.

insumer_get_merchant ~67

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.

NameTypeReqDescription
idstringyesMerchant ID
NameTypeReqDescription
data––The endpoint's payload: a signed attestation, trust profile, discount, merchant or token records
error––Error details when ok is false
itemsarray–The result when the endpoint returns a JSON array
keysarray–JWKS entries (insumer_jwks)
message––A plain-text result (insumer_setup), or a message from the API
meta––Response metadata such as version and timestamp
okboolean–true when the API call succeeded

No examples provided.

insumer_jwks ~111

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
data––The endpoint's payload: a signed attestation, trust profile, discount, merchant or token records
error––Error details when ok is false
itemsarray–The result when the endpoint returns a JSON array
keysarray–JWKS entries (insumer_jwks)
message––A plain-text result (insumer_setup), or a message from the API
meta––Response metadata such as version and timestamp
okboolean–true when the API call succeeded

No examples provided.

insumer_list_merchants ~115

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).

NameTypeReqDescription
limitinteger–Results per page (default 50, max 200)
offsetinteger–Pagination offset (default 0)
tokenstring–Filter by accepted token symbol, e.g. 'UNI'
verifiedstring–Filter by domain verification status
NameTypeReqDescription
data––The endpoint's payload: a signed attestation, trust profile, discount, merchant or token records
error––Error details when ok is false
itemsarray–The result when the endpoint returns a JSON array
keysarray–JWKS entries (insumer_jwks)
message––A plain-text result (insumer_setup), or a message from the API
meta––Response metadata such as version and timestamp
okboolean–true when the API call succeeded

No examples provided.

insumer_list_tokens ~127

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.

NameTypeReqDescription
chain––Filter by chain ID
symbolstring–Filter by token symbol
typestring–Filter by asset type
NameTypeReqDescription
data––The endpoint's payload: a signed attestation, trust profile, discount, merchant or token records
error––Error details when ok is false
itemsarray–The result when the endpoint returns a JSON array
keysarray–JWKS entries (insumer_jwks)
message––A plain-text result (insumer_setup), or a message from the API
meta––Response metadata such as version and timestamp
okboolean–true when the API call succeeded

No examples provided.

insumer_validate_code ~97

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.

NameTypeReqDescription
codestringyesDiscount code in INSR-XXXXX format
NameTypeReqDescription
data––The endpoint's payload: a signed attestation, trust profile, discount, merchant or token records
error––Error details when ok is false
itemsarray–The result when the endpoint returns a JSON array
keysarray–JWKS entries (insumer_jwks)
message––A plain-text result (insumer_setup), or a message from the API
meta––Response metadata such as version and timestamp
okboolean–true when the API call succeeded

No examples provided.

insumer_wallet_trust ~706

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.

NameTypeReqDescription
bitcoinWalletstring–Bitcoin address. If provided, adds the Bitcoin dimension (native BTC presence).
proofstring–Set to 'merkle' for EIP-1186 Merkle storage proofs on EVM token checks (6 credits). Rows whose balance is computed rather than stored (Aave aTokens, BUIDL), NFT/non-EVM rows and the account rows are…
solanaWalletstring–Solana wallet address (base58). If provided, adds the Solana dimension and lets the institutional rows on Solana evaluate.
stellarWalletstring–Stellar wallet address (G-prefixed). If provided, lets the institutional rows on Stellar evaluate (classic trustlines). Adds no dimension.
suiWalletstring–Sui wallet address (0x + 64 hex). If provided, lets the rows on Sui evaluate. Adds no dimension.
tronWalletstring–Tron wallet address (T-prefixed). If provided, adds the Tron dimension.
walletstringyesEVM wallet address (0x...) to profile
xrplWalletstring–XRPL wallet address (r-address). If provided, adds the XRPL dimension and lets the institutional row on XRPL evaluate.
NameTypeReqDescription
data––The endpoint's payload: a signed attestation, trust profile, discount, merchant or token records
error––Error details when ok is false
itemsarray–The result when the endpoint returns a JSON array
keysarray–JWKS entries (insumer_jwks)
message––A plain-text result (insumer_setup), or a message from the API
meta––Response metadata such as version and timestamp
okboolean–true when the API call succeeded

No examples provided.

Common questions

What is the com.insumermodel/insumer MCP server?

com.insumermodel/insumer is an MCP server listed in the public MCP registry as com.insumermodel/insumer. Wallet auth: send a wallet and conditions, get a signed boolean across 37 chains. This page covers its hosted endpoint (https://api.insumermodel.com/mcp).

Is the com.insumermodel/insumer MCP server safe to use?

com.insumermodel/insumer scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the com.insumermodel/insumer MCP server expose?

com.insumermodel/insumer exposes 10 tools: insumer_attest, insumer_compliance_templates, insumer_wallet_trust, insumer_batch_wallet_trust, insumer_jwks, and 5 more. Their descriptions and schemas cost roughly 3,253 tokens of context every time the server is loaded.

Does the com.insumermodel/insumer MCP server require authentication?

No. We connected to com.insumermodel/insumer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.insumermodel/insumer MCP server still maintained?

com.insumermodel/insumer is still listed as active in the MCP registry. We last reached this channel on 10 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.