Kaal Agent Safety (x402 paid MCP)
RemoteAbout Kaal Agent Safety (x402 paid MCP)
Kaal Agent Safety is a paid MCP server for URL payment-safety checks and provider recommendations. Its tools return signed receipts and use per-call USDC payments on Base through x402.
Key features
- 01Deterministic URL phishing and payment-safety checks
- 02Flags URL, host and security-configuration risks
- 03Ranked provider and cost-directory recommendations
- 04Signed receipts with free verification endpoint
Use cases
- 01Check a URL before an agent interacts with it
- 02Compare providers by category and cost
MCP support
Exposes `safety_check` and `recommend` as tools over streamable HTTP. Tool calls require x402 payment in USDC on Base; discovery and tool listing are free.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://places-wayne-experiment-facial.trycloudflare.com/mcpclaude mcp add --transport http immoney1-kaal-agent-safety https://places-wayne-experiment-facial.trycloudflare.com/mcp{"mcpServers":{"immoney1-kaal-agent-safety":{"type":"http","url":"https://places-wayne-experiment-facial.trycloudflare.com/mcp"}}}Open in Cursor{"servers":{"immoney1-kaal-agent-safety":{"type":"http","url":"https://places-wayne-experiment-facial.trycloudflare.com/mcp"}}}Open in VS Code{"mcpServers":{"immoney1-kaal-agent-safety":{"type":"http","url":"https://places-wayne-experiment-facial.trycloudflare.com/mcp"}}}{"mcpServers":{"immoney1-kaal-agent-safety":{"serverUrl":"https://places-wayne-experiment-facial.trycloudflare.com/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
Details
From the project READMEkaal-agent-safety — x402 paid MCP server
Two paid MCP tools plus three free HTTP endpoints. Buyers pay USDC on Base
(per-call, x402 exact scheme, EIP-3009 transferWithAuthorization) — no API
keys, no subscriptions. Free initialize + tools/list; payment only on
tools/call (HTTP 402 with payment requirements).
Endpoints
| Endpoint | Method | Price | Notes |
|---|---|---|---|
/v1/safety/check?target=<url> | GET | $0.002 | deterministic payment-safety / phishing scan + signed receipt |
/v1/recommend?category=<cat> | GET | $0.005 | ranked provider / cost-directory lookup |
/mcp | POST (MCP) | see below | streamable-http MCP transport |
/.well-known/mcp.json | GET | free | MCP discovery manifest |
/.well-known/x402 | GET | free | x402 payment manifest (payTo, facilitator, prices) |
/v1/verify?receipt=<id> | GET | free | replayable receipt verification |
/health | GET | free | liveness |
MCP tools
safety_check(target)— $0.002 per call: flagscredentials_in_url,no_hsts,ip_literal, lookalike hosts, missing/.well-known/x402manifest; returnsAVOID / CAUTION / CAUTION_NONE_DETECTED+ signed receipt.recommend(category)— $0.005 per call: ranked whitespace/cost directory across search, onchain-data, agent-safety, paid-discovery, tx-execution.
Connect
claude mcp add --transport http kaal-agent-safety https://<host>/mcp
# or any MCP client pointed at the streamable-http URL in server.json
Free: initialize, notifications/initialized, tools/list.
Paid: tools/call requires X-PAYMENT header (base64 exact-scheme payload);
server settles through an x402 facilitator and returns X-Payment-Response
with the on-chain transaction.
Run
npm ci
RECEIPT_SECRET=<32-byte-hex> \
NETWORK=base FACILITATOR_URL=http://127.0.0.1:8142 \
PORT=8140 node server.js
RECEIPT_SECRET (or WALLET_FILE=<path-to-wallet-json>) signs receipts.
NETWORK is base (mainnet) or base-sepolia. Settlement is non-custodial:
funds go straight to the configured payTo wallet on every settlement.
Verified
- Local E2E: unpaid 402 → EIP-3009 signed payment → verify → settle → on-chain receipt status 1.
- Public E2E over a tunnel: paid
GET /v1/safety/checksettled with tx0xd7bd01780b75d106fb3e286b6a3c55a78a6a486ee2cf439f4d2b3d8b5b1c28d7(Base mainnet, block 53162843, gas 83208). - Revenue ledger + treasury sweep + systemd auto-restart are part of the production deployment.
License
MIT
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.