Skip to content

Agent Spend Guard — owner-set purchasing guardrails MCP server

com.a2awire/agent-spend-guarda2awire.comstreamable-httpv0.1.1Scanned

Free spend guardrails for AI agents: approve/deny/ask_user, caps, dupes.

4 tools: 2 do something that can't be undone and 2 change things.

Tools: 0 delete, 2 irreversible, 2 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 Agent Spend Guard — owner-set purchasing guardrails MCP server can do

The Agent Spend Guard — owner-set purchasing guardrails MCP server is published by a2awire.com, a domain the MCP Registry verified. It has 4 tools. It can do things that cannot be undone, such as sending, paying or publishing (spend_guard_check_purchase and spend_guard_record_purchase) and create or change data (2 tools: spend_guard_set_rules and spend_guard_report), but cannot delete data. None of its tools only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 8, 2026, version 0.1.1.

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.

4 tools

Can't be undone 2Claude Code: ask
  • spend_guard_check_purchaseHumans: sign up with your email at https://a2awire.com/api-key and create an API key, then hand it to your agent (it sends Authorization: Bearer <key> or X-API-Key with every call)…No findings

    Why it is in this group

    • The name "spend_guard_check_purchase" says "purchase": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    Humans: sign up with your email at https://a2awire.com/api-key and create an API key, then hand it to your agent (it sends Authorization: Bearer <key> or X-API-Key with every call). Agents without an account: a reviewable bootstrap script is served at https://a2awire.com/api/v1/connectors/spend-guard/bootstrap.sh (download it, read it, then run it to mint a key). Call BEFORE checkout. Evaluate a proposed purchase (merchant, amount_usd) against the owner's spend rules and recent ledger. Returns a decision (approve, deny, or ask_user), a plain-English reason, the remaining monthly budget when a cap is set, and a check_id. deny means denylisted merchant or over the monthly cap; ask_user means above the per-purchase threshold or a possible duplicate of a purchase in the last 10 minutes. Optional tx_ref is your idempotency key for this purchase; pass the same value to spend_guard_record_purchase afterwards. Appends a check event; checks never consume budget. USD only (the currency argument is kept for forward compatibility; any other value is rejected). Not guest-callable. REST: POST /api/v1/spend-guard/check.

    Annotations the server declares

    • title: Spend Guard Check Purchase
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • spend_guard_record_purchaseHumans: sign up with your email at https://a2awire.com/api-key and create an API key, then hand it to your agent (it sends Authorization: Bearer <key> or X-API-Key with every call)…No findings

    Why it is in this group

    • The name "spend_guard_record_purchase" says "purchase": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    Humans: sign up with your email at https://a2awire.com/api-key and create an API key, then hand it to your agent (it sends Authorization: Bearer <key> or X-API-Key with every call). Agents without an account: a reviewable bootstrap script is served at https://a2awire.com/api/v1/connectors/spend-guard/bootstrap.sh (download it, read it, then run it to mint a key). Call AFTER checkout. Record a completed purchase in the owner's spend ledger. tx_ref is required and unique per owner: replaying the same tx_ref returns the original record without double counting (recorded_previously is true when the tx_ref was already in your ledger before this call, an idempotent replay; false on first write). Optional check_id links the record to its prior spend_guard_check_purchase; a check_id already recorded returns a conflict error. Returns the recorded event and the month-to-date total. USD only (the currency argument is kept for forward compatibility; any other value is rejected). Not guest-callable. REST: POST /api/v1/spend-guard/record.

    Annotations the server declares

    • title: Spend Guard Record Purchase
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Changes things 2Claude Code: ask
  • spend_guard_reportHumans: sign up with your email at https://a2awire.com/api-key and create an API key, then hand it to your agent (it sends Authorization: Bearer <key> or X-API-Key with every call)…No 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.
    Description, as the server wrote it
    Humans: sign up with your email at https://a2awire.com/api-key and create an API key, then hand it to your agent (it sends Authorization: Bearer <key> or X-API-Key with every call). Agents without an account: a reviewable bootstrap script is served at https://a2awire.com/api/v1/connectors/spend-guard/bootstrap.sh (download it, read it, then run it to mint a key). Month-to-date spend summary for the calling owner: total USD recorded, purchase count, top merchants (up to 5), current rules, and remaining monthly budget when a cap is set. Optional month (YYYY-MM) reads a prior month; defaults to the current UTC month. Not guest-callable. REST: GET /api/v1/spend-guard/report.

    Annotations the server declares

    • title: Spend Guard Report
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • spend_guard_set_rulesHumans: sign up with your email at https://a2awire.com/api-key and create an API key, then hand it to your agent (it sends Authorization: Bearer <key> or X-API-Key with every call)…No findings

    Why it is in this group

    • The name "spend_guard_set_rules" says "set": a word for a change.
    Description, as the server wrote it
    Humans: sign up with your email at https://a2awire.com/api-key and create an API key, then hand it to your agent (it sends Authorization: Bearer <key> or X-API-Key with every call). Agents without an account: a reviewable bootstrap script is served at https://a2awire.com/api/v1/connectors/spend-guard/bootstrap.sh (download it, read it, then run it to mint a key). Set the calling owner's spend-guard rules: an optional monthly cap in USD, an optional per-purchase threshold in USD, and an optional exact-match merchant denylist (case-insensitive). Full declaration: omit or null a field to clear that rule. With no rules every check approves (observation mode) and purchases are still recorded. Returns the effective rules. Not guest-callable. REST: PUT /api/v1/spend-guard/rules.

    Annotations the server declares

    • title: Spend Guard Set Rules
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

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 private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
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.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:22 UTC, unchanged since Nov 20, 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
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://a2awire.com/.well-known/oauth-protected-resource
Authorization servers
https://a2awire.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (2 irreversible, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://a2awire.com/mcp/connectors/spend-guard/http: tools/list returned 4 tools to an anonymous client, including spend_guard_check_purchase (irreversible), spend_guard_record_purchase (irreversible), spend_guard_set_rules (write), spend_guard_report (write)

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • RFC 9728 protected resource metadata: none to https://a2awire.com/.well-known/oauth-protected-resource
    • Authorization servers: none to https://a2awire.com
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. RFC 9728 protected resource metadata: none -> https://a2awire.com/.well-known/oauth-protected-resource; Authorization servers: none -> https://a2awire.com; Dynamic client registration: not observed -> yes (and 1 more…View diff
    • RFC 9728 protected resource metadata: none to https://a2awire.com/.well-known/oauth-protected-resource
    • Authorization servers: none to https://a2awire.com
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no

Install

Pinned to version 0.1.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http agent-spend-guard https://a2awire.com/mcp/connectors/spend-guard/http
claude mcp add --transport http agent-spend-guard https://a2awire.com/mcp/connectors/spend-guard/http

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

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__agent-spend-guard__spend_guard_check_purchase",
      "mcp__agent-spend-guard__spend_guard_record_purchase",
      "mcp__agent-spend-guard__spend_guard_set_rules",
      "mcp__agent-spend-guard__spend_guard_report"
    ],
    "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 agent-spend-guard. Review it before you use it.

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.a2awire/agent-spend-guard/verify?hash=4e881ff2f55da5bf9c58c8408a233d8659488dba5f82e8b4a3780dc59393dfbb" | jq -e '.changed == false'

Pinned hash 4e881ff2f55d, from Nov 8, 2026, 16:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.a2awire/agent-spend-guard/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.a2awire/agent-spend-guard
[![Anlyon Radar](https://radar.anlyon.com/badge/com.a2awire/agent-spend-guard.svg)](https://radar.anlyon.com/servers/com.a2awire/agent-spend-guard)

Source: MCP Registry · repository. Synced Nov 8, 2026, 17:17 UTC.

Agent Spend Guard — owner-set purchasing guardrails MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Agent Spend Guard — owner-set purchasing guardrails MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 4 of which can change, send or delete something, and 0 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 Agent Spend Guard — owner-set purchasing guardrails MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Agent Spend Guard — owner-set purchasing guardrails MCP server do things that cannot be undone?

Yes. 2 tools can send, pay, publish or merge: spend_guard_check_purchase and spend_guard_record_purchase.

What tools does the Agent Spend Guard — owner-set purchasing guardrails MCP server have?

4 tools: 2 irreversible, 2 write. spend_guard_check_purchase, spend_guard_record_purchase, spend_guard_set_rules and spend_guard_report.

Does the Agent Spend Guard — owner-set purchasing guardrails MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Agent Spend Guard — owner-set purchasing guardrails MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Agent Spend Guard — owner-set purchasing guardrails MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.