mcp-registry/com.blackwalltier/blackwall-x402-guardrail · v0.1.0
As of 2026-10-27 05:50 UTC, the Blackwalltier Blackwall X402 Guardrail MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Keyless hosted MCP: pre-signature x402 payment verdict (GO/HOLD/STOP) with a signed receipt.
Point your MCP client at this streamable-http endpoint: https://mcp.blackwalltier.com
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
1 of 1 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.blackwalltier%2Fblackwall-x402-guardrail/fixes
{
"name": "forecast_payment",
"description": "Pre-signature x402 payment verdict: GO / HOLD / STOP for paying a counterparty, from settlement reputation, price-anomaly (quoted vs the payee's own median), and OFAC sanctions — with a third-party-verifiable Ed25519 signed receipt. Verdict only; never takes custody. Free under $10 at risk; over that, returns an x402 payment challenge.",
"inputSchema": {
"type": "object",
"required": [
"counterparty",
"amount",
"asset",
"chain"
],
"properties": {
"asset": {
"type": "string",
"description": "e.g. USDC"
},
"chain": {
"type": "string",
"description": "e.g. base"
},
"payer": {
"type": "string",
"description": "agent's EVM wallet (optional; binds settlement)"
},
"amount": {
"type": "string",
"description": "amount as a decimal string, e.g. \"0.09\""
},
"context": {
"type": "object",
"description": "{quoted_price_history, expected_recipient}"
},
"agent_id": {
"type": "string",
"description": "caller DID/identity"
},
"resource": {
"type": "string",
"description": "what's being paid for"
},
"counterparty": {
"type": "string",
"description": "recipient wallet from the 402"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.blackwalltier/blackwall-x402-guardrail"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.blackwalltier/blackwall-x402-guardrail"}) over MCP.
forecast_payment ~294 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.blackwalltier%2Fblackwall-x402-guardrail?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.blackwalltier%2Fblackwall-x402-guardrail?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.blackwalltier%2Fblackwall-x402-guardrail.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.blackwalltier%2Fblackwall-x402-guardrail.svg :target: https://glimind.com/server/mcp-registry%2Fcom.blackwalltier%2Fblackwall-x402-guardrail?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:72a97b2096f9b08f…, first seen 2026-10-17, included at leaf 10022 of 77,688. Version history · verify what your client received.
Compare: most reliable finance servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-27 05:50 UTC, the Blackwalltier Blackwall X402 Guardrail MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Blackwalltier Blackwall X402 Guardrail MCP server advertises 1 tool, including forecast_payment.
Point your MCP client at this streamable-http endpoint: https://mcp.blackwalltier.com
Glimind scanned all 1 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.