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.

io.github.figuard/figuard-mcp

NPM · FIGUARD-MCP · SCANNED SEP 20

Pre-flight spend authorization for AI agents. Set a budget, enforce limits, audit every decision.

Available components

0 this week 81 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 95 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3118 tokens (~194/item across 16 items; 16 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 Management90
  • Stability observed for 27 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
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "figuard_revoke_delegation_token" implies "revoke" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 16 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 io.github.figuard/figuard-mcp server?

io.github.figuard/figuard-mcp runs locally as an npm package, launched with npx -y figuard-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · figuard-mcp

# add to Claude Code
claude mcp add figuard-figuard-mcp -- npx -y figuard-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "figuard-figuard-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "figuard-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "figuard-figuard-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "figuard-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add figuard-figuard-mcp -- npx -y figuard-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "figuard-figuard-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "figuard-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add figuard-figuard-mcp --command npx --arg -y --arg figuard-mcp
# ~/.hermes/config.yaml
mcp_servers:
  figuard-figuard-mcp:
    command: "npx"
    args: ["-y", "figuard-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "figuard-figuard-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "figuard-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add figuard-figuard-mcp -t stdio -c npx -a -y figuard-mcp
// mcp.json
{
  "mcpServers": {
    "figuard-figuard-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "figuard-mcp"
      ]
    }
  }
}
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.

  • 19 Sept 26 +1

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

  • 17 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 15 Sept 26 +1

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

  • 12 Sept 26 +1

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

  • 10 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 9 Sept 26 0
    • Stability: 0.97 → pass security
  • 8 Sept 26 +1

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

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 20 Sept 2026 · Analysed npm/figuard-mcp@1.2.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 16 exposed · ~3,118 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
figuard_authorize ~579

Pre-flight authorization — ask FiGuard if a spend is permitted before taking any action. Returns AUTHORIZED (with event_id) or DENIED (with denial_reason). Always call this before spending. Only proceed if the result is AUTHORIZED. The idempotency_key must be unique per logical spend intent — reuse the same key on retries so the same spend is never double-authorized. After the action succeeds call figuard_confirm; if it fails call figuard_fail. IMPORTANT: When the budget has allocations, pass the exact category string from the budget's allocation_categories field — do not use synonyms or plural forms (e.g. use 'flight' not 'flights').

NameTypeReqDescription
action_typestringyesType of action being authorized (e.g. 'PURCHASE', 'REFUND', 'LLM_CALL', 'API_CALL').
agent_idstringyesIdentifier for the agent making this request (e.g. 'booking-agent', 'refund-agent').
claimed_categorystringCategory of this spend (e.g. 'flight', 'hotel'). Required when the budget has allocations.
claimed_item_typestringSpecific item type (e.g. 'economy_ticket', 'hotel_room'). Used for STRICT enforcement mode.
descriptionstringyesHuman-readable description of what the agent is about to do (e.g. 'Book NYC to LAX flight').
dry_runbooleanWhen true, runs all enforcement checks and returns AUTHORIZED/DENIED but writes nothing to the ledger. Use for testing.
idempotency_keystringOptional. Unique key for this spend intent. Use a UUID or stable identifier. Reuse on retries — never generate a new key for the same logical spend. When omitted, the SDK auto-generates a UUID v4 (sa…
parent_event_idstringevent_id of the parent spend if this is a sub-agent call. Used to build the causal chain. The parent event must be in AUTHORIZED or CONFIRMED state — passing a DENIED or VOIDED parent_event_id will r…
requested_quantitynumberyesAmount to reserve. For USD budgets this is dollars. For token budgets this is the token count.
reservebooleanOptional (default true). Set false for an orchestrator/coordinator spend-tree root that should hold NO capacity and have no confirmation timeout — sub-agents authorize against the budget directly. Us…
session_tokenstringyesThe session_token returned by figuard_create_budget. Never expose this in logs.
trace_idstringOptional run ID to link all events from a single agent run together for debugging.

No output schema declared.

No examples provided.

figuard_cancel_batch ~126

Cancel one or more budgets. Use this to cancel a single budget (pass one ID) or up to 100 at once. This is the correct tool when the user asks to cancel, close, void, or abandon a budget — not figuard_void (which only cancels individual spend events, not budgets). Already-terminal budgets (EXPIRED, CANCELLED, EXHAUSTED) are included in the response without an error — the call is idempotent per budget.

NameTypeReqDescription
budget_idsarrayyesList of budget IDs to cancel. Maximum 100.

No output schema declared.

No examples provided.

figuard_confirm ~127

Confirm a previously authorized spend after the action succeeds. Pass the actual amount spent — it may differ from the authorized amount (e.g. authorized $340, flight cost $337.50). This releases the difference back to the budget. Always confirm after a successful action.

NameTypeReqDescription
confirmed_quantitynumberyesActual amount consumed. May be less than the authorized amount.
event_idstringyesThe event_id returned by figuard_authorize.
external_transaction_idstringOptional reference from your payment processor (e.g. Stripe charge ID) for audit purposes.

No output schema declared.

No examples provided.

figuard_create_budget ~687

Create a new FiGuard budget for an agent session. Returns a session_token that must be passed to figuard_authorize. The session_token is only returned once — store it for the duration of the agent session. Use currency (e.g. 'USD') for monetary budgets. Use unit (e.g. 'tokens') for resource budgets. Optionally add allocations to ring-fence spend by category (e.g. separate limits for flights and hotels). Pass external_reference to make this call idempotent: if a live budget with that reference already exists it is returned (HTTP 200) instead of creating a duplicate. If the reference exists but with a different configuration, a 409 is returned. Use this to safely handle orchestrator restarts.

NameTypeReqDescription
allocationsarrayOptional category-level caps. Each allocation is an independent maximum — flights capped at $300 means flights can never exceed $300, regardless of what other categories spend. Allocation limits must…
anomaly_detection_enabledbooleanWhen true, FiGuard monitors spend requests for statistical anomalies. Recommended for production.
auto_pause_on_anomalybooleanControls anomaly response mode. When true (default), an anomalous request pauses the budget — no further spend until a human resumes it. When false (advisory mode), the anomalous request is still den…
currencystringISO 4217 currency code (e.g. 'USD', 'EUR'). Required for monetary budgets. Omit for resource budgets.
expires_instringHow long the budget is valid. Accepts '24h', '7d', '30m', or a number of seconds. Defaults to '24h'.
external_referencestringOptional stable identifier for this budget (e.g. 'run-abc-123', 'order-456'). When provided, re-calling figuard_create_budget with the same external_reference returns the existing live budget instead…
intent_contextstringOptional human-readable description of what this budget is for (e.g. 'Book travel to NYC for user_123').
total_limitnumberyesMaximum total amount the agent is allowed to spend. For USD budgets this is dollars, not cents.
unitstringResource unit label (e.g. 'tokens', 'api_calls'). Required for resource budgets. Omit for monetary budgets.
user_idstringyesIdentifier for the user or agent session this budget belongs to.
velocity_max_amount_per_hournumberMax total requestedQuantity per rolling 1-hour window.
velocity_max_per_daynumberMax authorize attempts per rolling 24-hour window.
velocity_max_per_minutenumberMax authorize attempts per rolling 1-minute window. Denied with VELOCITY_LIMIT_EXCEEDED when exceeded.

No output schema declared.

No examples provided.

figuard_create_delegation_token ~181

Create a scoped delegation token for a fleet budget. Each sub-agent (e.g. per-customer refund agent) gets its own token with per-category spend caps. The sub-agent calls figuard_authorize with this token exactly as it would with a normal session token — FiGuard enforces both the per-token caps and the fleet-level allocations transparently. The session_token is returned once — hand it to the sub-agent immediately and store it securely.

NameTypeReqDescription
budget_idstringyesThe fleet budget ID to delegate from.
capsarrayyesPer-category spend caps for this sub-agent. Only listed categories are cap-enforced at the delegation level. Categories not listed pass through to the fleet allocation only.
labelstringyesHuman-readable label for this token, e.g. 'refund-agent-order-123'.

No output schema declared.

No examples provided.

figuard_extend_budget ~169

Extend a budget's expiry window. Use this to keep a long-running agent alive past its original expiry. The new expiry must be later than the current one and at most 24 hours from now. Can be called repeatedly (e.g. extend by 2 hours every 2 hours for a 6-hour task). Returns 409 if the budget is CANCELLED or EXHAUSTED. Returns 400 if the new expiry is earlier than the current one.

NameTypeReqDescription
budget_idstringyesThe budget ID to extend.
expires_atstringAbsolute ISO 8601 expiry timestamp. Mutually exclusive with expires_in.
expires_instringRelative duration from now (e.g. '2h', '30m'). Mutually exclusive with expires_at.

No output schema declared.

No examples provided.

figuard_fail ~116

Mark an authorized spend as failed when the action did not succeed (e.g. payment processor declined, API error). This releases the reserved funds back to the budget so they can be used again.

NameTypeReqDescription
error_messagestringOptional human-readable error detail for the audit log.
event_idstringyesThe event_id returned by figuard_authorize.
reasonstringyesShort reason code for the failure (e.g. 'PAYMENT_DECLINED', 'API_ERROR', 'TOOL_ERROR').

No output schema declared.

No examples provided.

figuard_fund_budget ~191

Adjust a budget's totalLimit in-place without creating a new session. Use CREDIT to top up a nearly-exhausted budget mid-run, DEBIT to reduce it, RESET to set a new absolute limit, or RESET_SPENT to start a fresh billing period (zeroes quantitySpent and reactivates EXHAUSTED budgets). Returns the budget state before and after the operation.

NameTypeReqDescription
amountnumberyesAmount to apply. Must be positive.
budget_idstringyesID of the budget to fund.
operationstringyesCREDIT: add amount to totalLimit. DEBIT: subtract amount (rejected if result < quantitySpent). RESET: set totalLimit to exactly amount. RESET_SPENT: zero quantitySpent, set new totalLimit, reactivate…
reasonstringOptional note recorded in the response for audit purposes.

No output schema declared.

No examples provided.

figuard_get_budget ~69

Get the current state of a budget — total limit, amount spent, amount reserved, amount available, status, and per-category allocations. Use this to check remaining budget before planning an agent's actions.

NameTypeReqDescription
budget_idstringyesThe budget ID (starts with 'bgt_').

No output schema declared.

No examples provided.

figuard_get_delegation_token ~56

Get the current state of a delegation token — label, status, per-category cap usage. The raw session_token is never returned, only the prefix.

NameTypeReqDescription
token_idstringyesThe delegation token ID.

No output schema declared.

No examples provided.

figuard_get_ledger ~149

Query the authorization ledger for a budget — returns a paginated list of spend events (authorized, confirmed, denied, voided, failed). Use this to review what an agent has spent or to debug a denial.

NameTypeReqDescription
budget_idstringyesThe budget ID (starts with 'bgt_').
decisionstringFilter by event decision. Omit to return all events.
pagenumberPage number, zero-indexed. Defaults to 0.
sizenumberEvents per page. Defaults to 20, max 100.
trace_idstringFilter by trace ID to see only events from a specific agent run.

No output schema declared.

No examples provided.

figuard_get_spend_tree ~80

Get the hierarchical spend tree for a budget — every event and its causal children (parent → child chains). Use to inspect what an agent (and its sub-agents) actually spent, including denied attempts. Returns roots and a total event count.

NameTypeReqDescription
budget_idstringyesThe budget ID (starts with 'bgt_').

No output schema declared.

No examples provided.

figuard_resume_budget ~159

Resume a budget that was paused by anomaly detection or manually. A budget is paused when a spend request is statistically unusual (autoPauseOnAnomaly=true) or via PATCH /budgets/{id}. A human must review and provide an override reason before the budget can be used again. Requires override_reason explaining why the pause was reviewed and cleared.

NameTypeReqDescription
budget_idstringyesThe budget ID (starts with 'bgt_').
override_bystringOptional identifier for the operator or system performing the override (e.g. 'ops-team', 'user_456').
override_reasonstringyesRequired explanation for why the budget is being resumed (e.g. 'Reviewed — legitimate bulk purchase approved by ops team').

No output schema declared.

No examples provided.

figuard_revoke_delegation_token ~77

Revoke a delegation token immediately. Any subsequent figuard_authorize call using this token will be rejected with INVALID_SESSION_TOKEN. Already-authorized events are not affected. Fires DELEGATION_TOKEN_REVOKED webhook. Idempotent.

NameTypeReqDescription
token_idstringyesThe delegation token ID to revoke.

No output schema declared.

No examples provided.

figuard_update_budget ~234

Update an existing budget's settings: total limit, velocity caps, expiry, trust mode, or status. Use trust_mode='FULL_ENFORCEMENT' to leave shadow mode and start blocking, or 'SHADOW' to observe without blocking. For crediting/debiting funds with audit semantics, prefer figuard_fund_budget instead.

NameTypeReqDescription
budget_idstringyesThe budget ID (starts with 'bgt_').
expires_atstringNew absolute ISO 8601 expiry (e.g. '2026-12-31T23:59:59Z').
statusstringBudget status override (advanced).
total_limitnumberNew total spend limit.
trust_modestring'SHADOW' (run all checks, block nothing) or 'FULL_ENFORCEMENT' (block denied spends).
velocity_max_amount_per_hournumberNew per-hour amount cap.
velocity_max_per_daynumberNew per-day authorize cap.
velocity_max_per_minutenumberNew per-minute authorize cap.

No output schema declared.

No examples provided.

figuard_void ~118

Cancel an authorized reservation that was never used. Use this when the agent decides not to proceed with an action after authorizing it (e.g. user cancelled, better option found).

NameTypeReqDescription
event_idstringyesThe event_id returned by figuard_authorize.
reasonstringyesShort reason for voiding (e.g. 'USER_CANCELLED', 'BETTER_OPTION_FOUND', 'PLAN_CHANGED').
void_child_eventsbooleanWhen true, also void child events in the causal chain. Defaults to false.

No output schema declared.

No examples provided.

Common questions

What is the io.github.figuard/figuard-mcp server?

io.github.figuard/figuard-mcp is listed in the public MCP registry as io.github.figuard/figuard-mcp. Pre-flight spend authorization for AI agents. Set a budget, enforce limits, audit every decision. This page covers its npm package (figuard-mcp).

Is the io.github.figuard/figuard-mcp server safe to use?

io.github.figuard/figuard-mcp scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.figuard/figuard-mcp server expose?

io.github.figuard/figuard-mcp exposes 16 tools: figuard_create_budget, figuard_authorize, figuard_confirm, figuard_fail, figuard_void, and 11 more. Their descriptions and schemas cost roughly 3,118 tokens of context every time the server is loaded.

Is the io.github.figuard/figuard-mcp server still maintained?

io.github.figuard/figuard-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.figuard/figuard-mcp server under?

io.github.figuard/figuard-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.