About safe4
safe4 is a hosted MCP server that evaluates whether an agent’s proposed payment serves its assigned task, in addition to checking budgets, categories, and counterparties. Each paid authorization returns an allow or deny result with reasons and a tamper-evident audit entry.
Key features
- 01Check payment against the assigned task
- 02Enforce budget and transaction caps
- 03Validate service categories and counterparties
- 04Return decisions with reason codes
- 05Append hash-chained audit entries
Use cases
- 01Review an agent’s purchase before payment
- 02Reject purchases unrelated to the assigned task
- 03Enforce permitted payees and categories
- 04Inspect the record of payment decisions
MCP support
Exposes `safe4_price` and `safe4_authorize` to MCP clients over Streamable HTTP. Authorization calls are paid per call in USDC via x402; connecting and listing tools are free.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://api.safe4.ai/mcp/claude mcp add --transport http ai-safe4-safe4 https://api.safe4.ai/mcp/{"mcpServers":{"ai-safe4-safe4":{"type":"http","url":"https://api.safe4.ai/mcp/"}}}Open in Cursor{"servers":{"ai-safe4-safe4":{"type":"http","url":"https://api.safe4.ai/mcp/"}}}Open in VS Code{"mcpServers":{"ai-safe4-safe4":{"type":"http","url":"https://api.safe4.ai/mcp/"}}}{"mcpServers":{"ai-safe4-safe4":{"serverUrl":"https://api.safe4.ai/mcp/"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
2This tool takes no parameters.
Details
From the project READMESafe4 — the payment firewall for AI agents, as an MCP server
Safe4 decides whether an AI agent's proposed payment should be allowed, by testing the purchase against the task the agent was actually given.
The case it exists for is the one budget limits miss: a payment that is inside every budget, in an allowed category, and to an approved counterparty — and is still the wrong purchase, because it does not serve the task.
This repository is the public manifest and client example for the hosted MCP
server. The service itself runs at api.safe4.ai; there is no server to
install.
Connect
Streamable HTTP, no installation:
{
"mcpServers": {
"safe4": {
"type": "http",
"url": "https://api.safe4.ai/mcp/"
}
}
}
Connecting and listing tools are free. Only safe4_authorize is paid.
Tools
safe4_price — free
Returns the current price and the payment networks the endpoint accepts, so an agent can see the cost before committing to a paid call.
safe4_authorize — paid, settled per call in USDC over x402
Returns an ALLOW or DENY decision for a proposed payment, with a reason
code, the concepts it matched, and a hash-chained audit entry.
Called without a payment it returns the x402 challenge instead of a decision.
An x402-aware client pays and calls again with the resulting payload in the
payment argument.
Arguments:
| Argument | Meaning |
|---|---|
task | The task the agent was given, as stated by its principal |
purchase | What is being bought |
purchase_purpose | Why this purchase serves the task |
amount, currency | The proposed payment |
counterparty | Who would receive it |
service_category | Category of the thing being bought |
allowed_service_categories | Categories the principal permits |
allowed_counterparties | Optional. Payees the principal permits |
task_id | Optional. Echoed into the audit entry |
payment | An x402 payment payload. Omit to receive the price list |
The task and the two allow-lists are the principal's constraints, not the
agent's — they are what the purchase is tested against, so an agent that writes
its own task is grading its own homework. Safe4 records every field it was
given and marks the task context as request-supplied, so a substituted
constraint is visible in the audit entry afterwards.
Try it without paying
The example runs the entire free surface — connect, list tools, read the price,
fetch the challenge — and stops before signing anything. It needs only httpx:
no key, no funded wallet.
python examples/mcp_buyer_demo.py https://api.safe4.ai --dry-run
Drop --dry-run and set SAFE4_BUYER_PRIVATE_KEY to buy a real decision. That
signs an EIP-3009 authorisation for exactly the amount and payee the server
advertised, and nothing else; the script holds no custody and Safe4 never sees
the key.
What a decision rests on
Four checks, in order, and a purchase must clear all of them:
- Budget and caps — per-transaction, daily, and agent-scoped limits.
- Service category — the purchase's category must be one the principal permitted.
- Counterparty — when the task declares
allowed_counterparties, payment to anyone else is refused. This is the only check that sees a swapped payee; task text and category are identical in that attack. - Task-to-purchase match — the task must account for what the purchase says it is buying, not merely share a word or two with it.
Every decision is appended to a hash-chained audit log. Each entry carries the previous entry's hash, so the record is tamper-evident and continuous across restarts and redeploys.
Payment
Priced per call in USDC over x402. The endpoint advertises
its terms in the 402 challenge; buyers pay on whichever advertised network
suits them. Safe4 holds no wallet key and takes no custody of buyer funds.
Links
- API documentation — https://api.safe4.ai/docs
- OpenAPI schema — https://api.safe4.ai/openapi.json
- x402 discovery — https://api.safe4.ai/.well-known/x402
- Site — https://safe4.ai
Security
Reporting instructions are in SECURITY.md. Please do not open a public issue containing exploit details.
License
The manifest and client examples in this repository are MIT licensed. The hosted service they describe is a separate commercial product.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.