A
license-
qualityD
maintenanceProvides cryptographic governance receipts for AI agents, enabling pre-execution evaluation and signed verdicts (EXECUTE/BLOCK/REVIEW/SHADOW) with offline-verifiable audit trails.
Last updated
MIT
blackwall-x402-guardrail
Server Details
Pre-signature x402 payment verdict (GO/HOLD/STOP) for AI agents, with a verifiable signed receipt.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- bluetieroperations-create/blackwall-mcp-remote
- GitHub Stars
- 0
- Server Listing
- Black_Wall remote MCP
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.2/5.0
Tool DescriptionsA
Average 4.2/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
Only one tool exists, so there is no possibility of ambiguity or confusion for an agent selecting among tools.
Naming Consistency5/5
A single tool presents no naming inconsistency; the name 'forecast_payment' follows a clear verb_noun pattern and is descriptive.
Tool Count4/5
With just one tool, the server is minimal but arguably appropriately scoped for a single-purpose guardrail that only provides a verdict and never takes custody.
Completeness3/5
The tool covers the core verdict and challenge functionality, but lacks auxiliary operations like status checks, history, or configuration, leaving notable gaps for a full lifecycle.
Available Tools
1 toolforecast_paymentAInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| asset | Yes | e.g. USDC | |
| chain | Yes | e.g. base | |
| payer | No | agent's EVM wallet (optional; binds settlement) | |
| amount | Yes | amount as a decimal string, e.g. "0.09" | |
| context | No | {quoted_price_history, expected_recipient} | |
| agent_id | No | caller DID/identity | |
| resource | No | what's being paid for | |
| counterparty | Yes | recipient wallet from the 402 |
Tool Definition Quality
A4.2/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that the tool is read-only (verdict only, never takes custody), provides a verifiable receipt, and has a free/challenge threshold. It does not cover auth or rate limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-structured sentence that front-loads the key output and conditions. It contains no filler, making it very concise for the information conveyed.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description explains the tool's purpose, output (verdict with receipt), and cost threshold. Given no output schema, it sufficiently covers return behavior. It does not detail the nested 'context' object, but the schema already describes it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
All 8 parameters have descriptions in the input schema (100% coverage), so the description adds little beyond the schema. It provides context on how parameters like counterparty and amount are used in the forecast but does not repeat or enhance parameter semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool provides a pre-signature payment verdict (GO/HOLD/STOP) based on reputation, price anomaly, and OFAC sanctions, and emphasizes it never takes custody. This distinguishes it from payment execution tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description specifies that the tool is free under $10 at risk and returns a challenge above that, giving a clear threshold. It implies use before payment, but lacks explicit when-not-to-use or alternatives since no siblings exist.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- AlicenseAqualityAmaintenancex402-trust gives AI agents a "check before you pay" layer for the x402 ecosystem.Last updated12126MIT
- AlicenseAqualityCmaintenanceBefore an AI agent pays an x402 endpoint, checks whether it's safe to pay: liveness, scam/anomaly scan (payTo hijack, bait-and-switch, honeypot), and on-chain receiver verification. ~70% of x402 endpoints are dead or scams.Last updated3MIT
- Alicense-qualityDmaintenanceAdversarial multi-model reasoning verification for AI agents. Claude, Grok, and DeepSeek challenge each decision — returns ALLOW or HOLD with JWKS-signed attestation. x402-gated on Base.Last updated15MIT
Try in Browser
Your Connectors
Sign in to create a connector for this server.