Agent Spend Guard — owner-set purchasing guardrails
REMOTE · A2AWIRE.COM · SCANNED SEP 25
Free spend guardrails for AI agents: approve/deny/ask_user, caps, dupes.
Available components
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage84
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 53% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
remote · a2awire.com
claude mcp add --transport http com-a2awire-agent-spend-guard 'https://a2awire.com/mcp/connectors/spend-guard/http'
{
"mcpServers": {
"com-a2awire-agent-spend-guard": {
"url": "https://a2awire.com/mcp/connectors/spend-guard/http"
}
}
} {
"servers": {
"com-a2awire-agent-spend-guard": {
"type": "http",
"url": "https://a2awire.com/mcp/connectors/spend-guard/http"
}
}
} [mcp_servers.com-a2awire-agent-spend-guard] url = "https://a2awire.com/mcp/connectors/spend-guard/http"
{
"$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 mcp add com-a2awire-agent-spend-guard --url 'https://a2awire.com/mcp/connectors/spend-guard/http' --transport streamable-http
mcp_servers:
com-a2awire-agent-spend-guard:
url: "https://a2awire.com/mcp/connectors/spend-guard/http" {
"McpServers": {
"com-a2awire-agent-spend-guard": {
"Transport": "http",
"Url": "https://a2awire.com/mcp/connectors/spend-guard/http"
}
}
} assistant mcp add com-a2awire-agent-spend-guard -t streamable-http -u 'https://a2awire.com/mcp/connectors/spend-guard/http'
{
"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.
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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 23 Sept 26 69
First indexed and scored.
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 25 Sept 2026 · Probed https://a2awire.com/mcp/connectors/spend-guard/http
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=a2awire.com | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 12 Jun 2026 | 26 Dec 2026 | RSA 2048 | SHA256-RSA | ceeeab5f7536fc4b9dba79ae6d8ee22 |
| SANs: a2awire.com, *.a2awire.com, a2awire.io, *.a2awire.io | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of a2awire.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| a2awire.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://a2awire.com/mcp/connectors/spend-guard/http | Verified | 200 | |
| http (plaintext) | http://a2awire.com/mcp/connectors/spend-guard/http | HTTPS enforced | 301 | https://a2awire.com/mcp/connectors/spend-guard/http |
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 →
spend_guard_check_purchase ~347
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usd | – | yes | – |
| category | – | – | – |
| currency | string | – | USD only. Kept for forward compatibility; any other value is rejected. |
| description | – | – | – |
| merchant | string | yes | – |
| 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. |
No output schema declared.
No examples provided.
spend_guard_record_purchase ~336
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usd | – | yes | – |
| 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 | yes | – |
| tx_ref | string | yes | Caller idempotency key, unique across your recorded purchases; replays return the original record. |
No output schema declared.
No examples provided.
spend_guard_report ~195
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.
| Name | Type | Req | Description |
|---|---|---|---|
| month | – | – | Optional month filter (YYYY-MM); defaults to the current UTC month. |
No output schema declared.
No examples provided.
spend_guard_set_rules ~280
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.