X402 Payment Safety is answering right now. Last checked 4 min ago. It exposes 1 tools. Last commit 24 Oct 2026.
Authorize x402 payments before signing with request-bound, signed safety decisions.
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 16 August 2026. No other catalogue keeps this.
We read the source, 1 h ago · tools taken from the live server · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
path = os.path.join(OUT, f"sweep_{ax}.json")
os.system(f"{sys.executable} -m pip install -q openai")
env = dict(os.environ)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.
claude mcp add x402-payment-safety --transport http https://agent-guild-5d5r.onrender.com/mcp/payment-safety/
https://agent-guild-5d5r.onrender.com/mcp/payment-safety/
[mcp_servers.x402-payment-safety]
url = "https://agent-guild-5d5r.onrender.com/mcp/payment-safety/"
{
"mcpServers": {
"x402-payment-safety": {
"url": "https://agent-guild-5d5r.onrender.com/mcp/payment-safety/"
}
}
}
{
"servers": {
"x402-payment-safety": {
"type": "http",
"url": "https://agent-guild-5d5r.onrender.com/mcp/payment-safety/"
}
}
}
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
guild_x402_payment_safety
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://agent-guild-5d5r.onrender.com/mcp/payment-safety/ | streamable-http | answering | 627 ms | 4 min ago |
Pre-payment safety gate for x402 agents: PII screening, spend policy, replay checks before signing.
Policy decision point for agent payments — allow, ask, or veto before signing
x402 payment-request parser with a limited token list. Does not sign, approve or judge payments.
Spending control for AI agents: approved budgets, a decision before each payment, signed receipts.
Allow, ask, or veto — a policy decision point your agent consults before signing any payment
Authorize and prove autonomous x402/AP2 agent payments with cryptographic receipts.
Kilawatt Cloud MCP server: request GPU compute with account or x402 payments.
Pre-payment checks for AI agents: sanctions and AML screening of payees, payment pages and requests.
Answers built from our own checks of this server.