Guided first use
Try InsumerAPI MCP
Reviews the InsumerAPI tools that can spend money or credits or change merchant state: verification and trust calls that use credits or pay Follow the three steps below with your own setup — nothing on this page runs on your machine or changes a policy.
Step 1 · Check fit
What this coverage governs
Reviews the InsumerAPI tools that can spend money or credits or change merchant state: verification and trust calls that use credits or pay per call in USDC, payment registrations, API key and merchant creation, merchant configuration, domain verification and the public listing. Read-only lookups keep Guard's usual handling. Off until you turn it on.
External — off until you opt in
This coverage stays off until you explicitly enable it from your Guard workspace controls. Reading this page never changes your policy; activation happens in Guard itself.
Harness support
Not documented yetTwo things have to line up: a client that runs the InsumerAPI MCP server, and a harness Guard supports. The server's README documents Claude Desktop, Cursor and Windsurf, and it runs under any MCP-compatible client. Guard's harness list (https://hol.org/guard/harnesses) includes Cursor and Claude Code among others; Claude Desktop and Windsurf are not on it. So the setups to expect this coverage in are Cursor and Claude Code. What we tried, on 2026-10-10: HOL Guard 3.42.0 on macOS with Claude Code 2.1.281. After hol-guard install claude-code, Guard's hooks stopped Claude Code tool calls before they ran and returned a review decision, so interception in Claude Code is confirmed. What that trial did not reach: enabling this extension and watching Guard stop insumer_attest. Enabling needs Guard's local service and a local-admin confirmation, and the trial ended before that step. What else has been checked: the catalog entry passes the repository's contribution and extension trust tests. Cursor has not been tried.
- Claude Code on macOS: tried on 2026-10-10 with Guard 3.42.0 and Claude Code 2.1.281. Guard intercepted tool calls before they ran. This extension's review of insumer_attest was not reached in that trial.
- Not covered: clients that reach the hosted endpoint at api.insumermodel.com/mcp by URL. That path does not go through npx, so this entry does not apply to it.
- Claude Desktop and Windsurf run the server but are not on Guard's harness list, so this coverage does not apply there.
- Cursor: on Guard's harness list and runs the server over npx. Not tried.
Prerequisites
Not documented yetContributor-supplied prerequisite text is not independently verified. Four things, all ordinary. Node.js with npx, since the server is launched as npx -y mcp-server-insumer. A Guard-supported MCP client that can run a local server: Cursor or Claude Code. A way for the server to pay for metered calls: either an InsumerAPI key in INSUMER_API_KEY (free, created with an email address, 10 free verifications plus 100 requests a day) or, for x402 pay-per-call, a throwaway Base wallet holding a few dollars of USDC in INSUMER_PAYMENT_KEY; never a wallet with meaningful funds. And HOL Guard installed, with local-admin rights in your workspace, because this extension is opt-in and only a local admin can enable it.
- Node.js with npx: the server launches as npx -y mcp-server-insumer.
- A Guard-supported MCP client that runs local servers: Cursor or Claude Code.
- INSUMER_API_KEY (free, created with an email address at POST https://api.insumermodel.com/v1/keys/create) or, for x402 pay-per-call, INSUMER_PAYMENT_KEY set to a throwaway Base wallet holding a few dollars of USDC.
- HOL Guard installed, and local-admin rights in your Guard workspace to enable this opt-in extension.
- Know the scope before you install: in our trial on macOS (Guard 3.42.0), installing Guard for Claude Code added its hooks to the user-level Claude Code settings, so Guard reviews every Claude Code session on the machine, not one project.
- Just want to try InsumerAPI first, with no key? Connect the hosted endpoint at https://api.insumermodel.com/mcp in any client that takes an MCP server URL. It needs no key and is free within a shared daily allowance, with ten of the tools including insumer_attest and insumer_wallet_trust. This Guard coverage applies to the local npx server only, not to the hosted endpoint.
Known limitations
Reviewed as supportedLimitations are copied from the reviewed catalog facts. Contributor-supplied limitation notes are not independently verified. Guard reviews whether a covered call may proceed. It does not inspect the price, the conditions or the wallet in the call, and it does not cap spending; the server's own cap (INSUMER_MAX_PAYMENT_USDC for x402 pay-per-call) and InsumerAPI's credit balance do that. Only the 18 tool names in the catalog entry are reviewed. The read-only lookups, and any tool added in a later server release, inherit Guard's usual handling. The entry maps the npx launch only; the hosted endpoint at api.insumermodel.com/mcp, reached by URL, is outside it.
- Coverage is limited to the reviewed operations and the surrounding Guard policy.
- A maintainer profile is not a security certification or an official upstream endorsement.
- Guard reviews the call, not the price or the conditions in it. Spending caps live in the server (INSUMER_MAX_PAYMENT_USDC for x402 pay-per-call) and in InsumerAPI's credit balance.
- Only the 18 listed tool names are reviewed. Read-only lookups and any tool added in a later mcp-server-insumer release inherit Guard's usual handling until the entry is updated.
- The npx launch only. The hosted endpoint at api.insumermodel.com/mcp is reached by URL and is not covered.
- Coverage is limited to the reviewed operations and the surrounding Guard policy.
- A maintainer profile is not a security certification or an official upstream endorsement.
Catalog version 1.0.0 · source snapshot f0b7ce7c8e
Step 2 · Set up
Install and activate
New to Guard? Start with Install Guard. Already installed? Skip install — this coverage stays off until you enable it from your workspace controls.
Activation happens in your Guard workspace. This page links to it; it never enables the coverage for you.
Install
Contributor-supplied install guidance is not independently verified because an exact reviewed argv contract is unavailable. Installing the server is one config entry in your MCP client; enabling the Guard coverage is a separate step a local admin takes in Guard. The steps below are the documented path from the server's README (https://github.com/insumerapi/mcp-server-insumer#readme). Nothing here is run for you.
- 1
Get a key, or skip to step 2 for pay-per-call. One request creates a free key: POST https://api.insumermodel.com/v1/keys/create with a JSON body of {"email": "[email protected]", "appName": "MCP Server", "tier": "free"}. The response carries an insr_live_... key. One free key per email; 10 free verifications plus 100 requests a day.
Self-reported guidance — not verified against a reviewed source.
- 2
Add the server to your MCP client. In Cursor's MCP settings, or in Claude Code's MCP configuration, add a server named insumer with command npx, args ["-y", "mcp-server-insumer"], and env INSUMER_API_KEY set to your key. That runs the latest release, which is where fixes and hardening arrive. If your policy requires pinning, use [email protected] instead; either way, a tool added in a later release inherits Guard's usual handling until this entry is updated, so read the release notes when you move. For x402 pay-per-call, set INSUMER_PAYMENT_KEY to a throwaway Base wallet's private key instead of a key; USDC only, no ETH needed, and optionally INSUMER_MAX_PAYMENT_USDC to lower the $3.00 per-call cap.
Self-reported guidance — not verified against a reviewed source.
- 3
Restart the client and confirm the insumer server lists its 27 tools, each signed answer carrying both an ES256 (ECDSA) signature and a post-quantum ML-DSA-65 signature you can check against https://insumermodel.com/.well-known/jwks.json. A read-only lookup such as fetching those signing keys needs no credit and proves the connection.
Self-reported guidance — not verified against a reviewed source.
- 4
Install HOL Guard if it is not already running (https://hol.org/guard), then continue to Activation to enable this coverage; it stays off until a local admin turns it on.
Self-reported guidance — not verified against a reviewed source.
Activation
Contributor-supplied activation guidance is not independently verified because an exact reviewed argv contract is unavailable. The catalog declares this coverage external and opt-in. Installing the server does not turn it on, and this page cannot turn it on. A local admin enables mcp.insumer from the Guard workspace controls; review for the 18 listed tools applies only after that local-admin enable, never from a signed-cloud enable. You know it is active when a covered call, such as insumer_attest, stops at Guard's review prompt instead of going straight through, and Guard's activity view records the decision.
- 1
As a local admin, open your Guard workspace controls and find the MCP coverage for mcp.insumer (Guard enforcement ID command.mcp-insumer). Enable it. Guard's own guide for enabling external extensions is at https://github.com/hashgraph-online/hol-guard/blob/main/docs/guard/extensions/README.md.
Self-reported guidance — not verified against a reviewed source.
- 2
Confirm the 18 listed tools now show Review in Guard's policy view for this extension, and that the other entry still reads Inherit policy. No tool should read Allow.
Self-reported guidance — not verified against a reviewed source.
- 3
To stop: disable the extension from the same controls. The server keeps working; its calls simply return to Guard's usual handling. Removing the mcpServers entry from your client removes the server itself.
Self-reported guidance — not verified against a reviewed source.
Step 3 · Verify the result
Run a safe test and compare
Safe fixture inputs
Contributor-supplied safe fixture input guidance is not independently verified because an exact reviewed argv contract is unavailable. The safe trial uses a free key and a wallet you control, so the most it can cost is one of the key's 10 free verifications, and it changes nothing anywhere. It runs one read-only lookup (passes through) and one covered call (should stop for review). Do not use a merchant tool, a buy tool or insumer_setup for the trial; those change state or register payments.
- 1
Ask your agent to fetch InsumerAPI's signing keys through the insumer server. This is a read-only lookup: it costs nothing and is not in the reviewed list, so Guard should let it through without a prompt.
Self-reported guidance — not verified against a reviewed source.
- 2
Ask your agent to run insumer_attest for a wallet address you control with one condition: type token_balance, chainId 8453 (Base), contractAddress 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 (USDC), operator gte, threshold "1" as a string. Whether the wallet holds a dollar of USDC does not matter; a signed no is as good a result as a signed yes.
Self-reported guidance — not verified against a reviewed source.
- 3
When Guard's review prompt appears for insumer_attest, approve it once. Then open Guard's activity view and find the recorded decision for command.mcp-insumer.
Self-reported guidance — not verified against a reviewed source.
Expected outcome
Not documented yetContributor-supplied expected-outcome text is not independently verified. Three things, in order. The signing-keys lookup returns the published JWKS with no Guard prompt. The insumer_attest call stops at Guard's review prompt before anything is sent; nothing is spent while it waits. After approval the call completes and the agent receives a signed attestation: an id starting ATST-, pass true or false, one result per condition with the block it was read at, an ES256 signature (kid insumer-attest-v2) and a post-quantum ML-DSA-65 signature (pqKid insumer-attest-pq1), and an expiresAt 30 minutes out. The key's free verifications drop by one. Guard's activity view shows one Review decision for command.mcp-insumer with the approval recorded. If the attest call went through with no prompt, the extension is not enabled; go back to Activation.
- Signing-keys lookup: returns the JWKS, no Guard prompt.
- insumer_attest: Guard review prompt first; after approval, a signed attestation (ATST- id, pass true or false, per-condition result with block number, ES256 plus ML-DSA-65 signatures, expiresAt 30 minutes out).
- Guard activity view: one Review decision for command.mcp-insumer, approved. No prompt at all means the extension is not enabled yet.
Did it work?
Sign in to record an honest self-report. It is stored as your report — never as a verified evaluation.
Sign in to reportTurn it off or recover
Not documented yetContributor-supplied disable/remove guidance is not independently verified because an exact reviewed argv contract is unavailable. Two separate things can be turned off. Disabling the coverage in Guard stops the review prompts; the server keeps working and its calls go back to Guard's usual handling. Removing the server's entry from your MCP client removes the server. Neither step touches anything at InsumerAPI: your key, its remaining credits, any merchant you created and any payment you registered stay exactly as they were, and any attestation already returned stays valid until its own expiresAt.