Back to Browse

Blackwall Mcp Remote MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

Pre-signature x402 payment verdict (GO/HOLD/STOP) for AI agents, with a verifiable signed receipt.

About

Pre-signature x402 payment verdict (GO/HOLD/STOP) for AI agents, with a verifiable signed receipt.

Remote endpoints: streamable-http: https://mcp.blackwalltier.com

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

1 tool verified · Open access · No issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "com-blackwalltier-blackwall-x402-guardrail": {
      "url": "https://mcp.blackwalltier.com"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

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
counterpartystring, requiredrecipient wallet from the 402
amountstring, requireddecimal string, e.g. "0.09"
assetstring, requirede.g. USDC
chainstring, requirede.g. base
payer / resource / agent_id / contextoptionalbinds 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.

Reviews

No reviews yet

Be the first to review this server!