streamable-httpupdated 14d ago
A hosted remote MCP (Model Context Protocol over HTTP) that gives any MCP-capable agent a pre-signature payment-risk verdict — with no install and no signup. Add one URL and your agent can ask, before it signs an x402 payment, "should I pay this?" and get GO / HOLD / STOP — from counterparty settlement reputation, price-anomaly (quoted vs the payee's own median), and OFAC sanctions — plus a third-party-verifiable Ed25519 signed receipt.
What can you do with blackwall x402 guardrail?
Black_Wall remote MCP
A hosted remote MCP (Model Context Protocol over HTTP) that gives any MCP-capable agent a pre-signature payment-risk verdict — with no install and no signup. Add one URL and your agent can ask, before it signs an x402 payment, "should I pay this?" and get GO / HOLD / STOP — from counterparty settlement reputation, price-anomaly (quoted vs the payee's own median), and OFAC sanctions — plus a third-party-verifiable Ed25519 signed receipt.
Add it
Point your MCP client at:
https://mcp.blackwalltier.com
Transport: Streamable HTTP. No API key. Verdicts for amounts under $10 at
risk are free; at or above that, the tool returns an x402 payment challenge
your agent settles from its own wallet (pass the settled payment back as an
X-PAYMENT header, then retry).
The tool: forecast_payment
| field | ||
|---|---|---|
counterparty |
string, required | recipient wallet from the 402 |
amount |
string, required | decimal string, e.g. "0.09" |
asset |
string, required | e.g. USDC |
chain |
string, required | e.g. base |
payer / resource / agent_id / context |
optional | binds settlement / context |
Returns a verdict (GO/HOLD/STOP) + reasons + signals, and a
signed_receipt anyone can verify against the published key at
https://agent-egress-proxy.onrender.com/.well-known/blackwall-receipt-key.json
(any RFC 8032 Ed25519 library) — Black_Wall never has to be in the loop.
How it works
This Worker is a thin transport + proxy: it speaks minimal MCP JSON-RPC
(initialize / tools/list / tools/call / ping) and forwards
forecast_payment calls to the Black_Wall x402 oracle. All decision logic and
the receipt come from the oracle unchanged.
Fail-closed by design: if the oracle errors, is unreachable, or returns a
non-verdict, the tool returns an error — never a phantom GO. A payment
guardrail that can't reach its backend must not imply "safe to pay."
Registry
Published to the official MCP Registry as
com.blackwalltier/blackwall-x402-guardrail.
Develop
node test.mjs # unit tests (mocked oracle)
npx wrangler dev # run locally
npx wrangler deploy # deploy (Cloudflare Workers)
By BlueTier. Verdict only — never takes custody, never in the settlement path. No evidence is not trust.
Install
Add blackwall x402 guardrail to your client. Pick the one you use.
claude mcp add --transport http blackwall-x402-guardrail https://mcp.blackwalltier.comcodex mcp add blackwall-x402-guardrail --url https://mcp.blackwalltier.com{
"mcpServers": {
"blackwall-x402-guardrail": {
"url": "https://mcp.blackwalltier.com"
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
{
"servers": {
"blackwall-x402-guardrail": {
"type": "http",
"url": "https://mcp.blackwalltier.com"
}
}
}Add to `.vscode/mcp.json` in your workspace.
{
"mcpServers": {
"blackwall-x402-guardrail": {
"url": "https://mcp.blackwalltier.com"
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"blackwall-x402-guardrail": {
"serverUrl": "https://mcp.blackwalltier.com"
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
Score
39 / 100
Incomplete
- Documentation17/25
- Maintenance25/25
- Trust6/20
- Capability0/15
- Install experience12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 7 days ago
- Has a release history
- Repository is not archived
- No licence detected
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 0 tool(s) documented
- Provides prompt templates
- Provides resources
- 6 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint — no local install
Version history
| Versions | Published |
|---|---|
| 0.1.2Latest | Aug 25, 2026 |
| 0.1.1 | Jul 8, 2026 |
| 0.1.0 | Jul 8, 2026 |