# Agent Spend Guard — owner-set purchasing guardrails (remote · a2awire.com)

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

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `a2awire.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/com-a2awire-agent-spend-guard/mcp-connectors-spend-guard-http.md), [page](https://verifymcp.io/servers/com-a2awire-agent-spend-guard/mcp-connectors-spend-guard-http)

## Channel facts

- Endpoint: `https://a2awire.com/mcp/connectors/spend-guard/http`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1498 tokens (~374/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 84/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 53% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Agent Spend Guard — owner-set purchasing guardrails MCP server?

Agent Spend Guard — owner-set purchasing guardrails is a hosted endpoint at https://a2awire.com/mcp/connectors/spend-guard/http, 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.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "com-a2awire-agent-spend-guard": {
      "url": "https://a2awire.com/mcp/connectors/spend-guard/http"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-a2awire-agent-spend-guard": {
      "type": "http",
      "url": "https://a2awire.com/mcp/connectors/spend-guard/http"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-a2awire-agent-spend-guard]
url = "https://a2awire.com/mcp/connectors/spend-guard/http"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-a2awire-agent-spend-guard": {
      "type": "remote",
      "url": "https://a2awire.com/mcp/connectors/spend-guard/http",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-a2awire-agent-spend-guard --url 'https://a2awire.com/mcp/connectors/spend-guard/http' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-a2awire-agent-spend-guard:
    url: "https://a2awire.com/mcp/connectors/spend-guard/http"
```

### Netclaw

```json
{
  "McpServers": {
    "com-a2awire-agent-spend-guard": {
      "Transport": "http",
      "Url": "https://a2awire.com/mcp/connectors/spend-guard/http"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-a2awire-agent-spend-guard -t streamable-http -u 'https://a2awire.com/mcp/connectors/spend-guard/http'
```

### Other

```json
{
  "mcpServers": {
    "com-a2awire-agent-spend-guard": {
      "type": "http",
      "url": "https://a2awire.com/mcp/connectors/spend-guard/http"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 70, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 70, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-23 (score 69)

First indexed and scored.

## MCP tools (4)

### `spend_guard_check_purchase` (~347 tokens)

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.

Input parameters:

- `amount_usd` (required)
- `category`
- `currency` (string): USD only. Kept for forward compatibility; any other value is rejected.
- `description`
- `merchant` (string, required)
- `tx_ref`: Optional idempotency key for this purchase; pass the same value to the record call afterwards. Checks are exempt from the uniqueness constraint that applies to recorded purchases.

### `spend_guard_record_purchase` (~336 tokens)

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.

Input parameters:

- `amount_usd` (required)
- `category`
- `check_id`: Optional id from spend_guard_check_purchase; at most one record may consume each check.
- `currency` (string): USD only. Kept for forward compatibility; any other value is rejected.
- `description`
- `merchant` (string, required)
- `tx_ref` (string, required): Caller idempotency key, unique across your recorded purchases; replays return the original record.

### `spend_guard_set_rules` (~280 tokens)

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.

Input parameters:

- `merchant_denylist`: Exact-match merchant names (case-insensitive) whose purchases are denied, up to 100 entries. Null clears the list.
- `monthly_cap_usd`: Cumulative recorded spend per UTC calendar month at or above which checks deny. Null clears the cap.
- `per_purchase_threshold_usd`: A single purchase strictly above this amount asks the user first. Null clears the threshold.

### `spend_guard_report` (~195 tokens)

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.

Input parameters:

- `month`: Optional month filter (YYYY-MM); defaults to the current UTC month.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-a2awire-agent-spend-guard/mcp-connectors-spend-guard-http#diagnostics

## Score history

- 2026-09-25: 70
- 2026-09-24: 70
- 2026-09-23: 69

## Common questions

### What is the Agent Spend Guard — owner-set purchasing guardrails MCP server?

Agent Spend Guard — owner-set purchasing guardrails is an MCP server listed in the public MCP registry as com.a2awire/agent-spend-guard. Free spend guardrails for AI agents: approve/deny/ask_user, caps, dupes. This page covers its hosted endpoint (https://a2awire.com/mcp/connectors/spend-guard/http).

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

Agent Spend Guard — owner-set purchasing guardrails scores 70 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 Agent Spend Guard — owner-set purchasing guardrails MCP server expose?

Agent Spend Guard — owner-set purchasing guardrails exposes 4 tools: spend_guard_check_purchase, spend_guard_record_purchase, spend_guard_set_rules, spend_guard_report. Their descriptions and schemas cost roughly 1,158 tokens of context every time the server is loaded.

### Does the Agent Spend Guard — owner-set purchasing guardrails MCP server require authentication?

No. We connected to Agent Spend Guard — owner-set purchasing guardrails without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Agent Spend Guard — owner-set purchasing guardrails MCP server still maintained?

Agent Spend Guard — owner-set purchasing guardrails is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://a2awire.com/mcp/connectors/spend-guard/http
- Repository: https://github.com/ee324/a2awire
- Website: https://a2awire.com/spend-guard
- Changelog RSS feed: https://verifymcp.io/servers/com-a2awire-agent-spend-guard/mcp-connectors-spend-guard-http.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-a2awire-agent-spend-guard/mcp-connectors-spend-guard-http.json
- HTML version of this page: https://verifymcp.io/servers/com-a2awire-agent-spend-guard/mcp-connectors-spend-guard-http