mcpbeat Sign in

XGuard — Payment Decision & Discovery MCP Server

not responding

XGuard — Payment Decision & Discovery is listed as active in the registry but did not answer our last check. It exposes 10 tools. Last commit 8 Oct 2026.

Payment decisions, durable evidence, x402 resource discovery and live gateway status for AI agents.

Uptime history 61 days of history · worst day 0%
61 days agonow
0.0%
Uptime 24h
0 of 184 checks
10
Tools
read from the server
51 ms
Response time
average over 24h
0
Stars
last commit 8 Oct 2026

What changed 56

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 25 August 2026. No other catalogue keeps this.

20 Sep a tool changed version
1 Sep a tool changed version
27 Aug 10 tool descriptions were rewritten21 times that day xguard_discovery_search, xguard_facilitator, xguard_health and 7 more
27 Aug a tool changed version7 times that day
27 Aug 3 tools changed the parameters they ask for xguard_inspect, xguard_receipt, xguard_safety_test
27 Aug 3 tools appeared xguard_discovery_search, xguard_facilitator, xguard_route
25 Aug 8 tools appeared xguard_endpoint_details, xguard_health, xguard_inspect and 5 more
25 Aug 4 tool descriptions were rewritten xguard_discover, xguard_health, xguard_integration and 1 more
25 Aug 4 tools disappeared xguard_discover, xguard_endpoint_details, xguard_resource_details and 1 more
25 Aug 2 tools changed the parameters they ask for xguard_discover, xguard_status
and 19 more, back to 25 August 2026

What the code does

We read the source, 7 d ago · tools taken from the live server · rules ccca72095570

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Executes code built at runtime apps/relay/src/execution-first-test.js:143
    for (const script of document.querySelectorAll("script")) { assert.doesNotThrow(() => new Function(script.textContent)); assert.ok(script.getAttribute("nonce")); }
Long encoded blob in source apps/relay/src/rail-entry.js:10
const LOGO_PNG_BASE64 = "iVBORw0KGgoAAAANSUhEUgAAAZAAAAGQCAYAAACAvzbMAAAMe0lEQVR42u3dwU0kS7Cw0QaNhFjQPowXYwJGYAZbJCS2mIERmIAX+NAOMKvZ0IO6uyqzMiPinN2TnvT/tyorvgz6Xr2rm9u7rx0AXOjaIwBAQAAQEAAEBAABAQABAUBAABAQAAQEAAEBAAEBQEAAEBAABAQAAQEAAQFAQAAQEAAEBAABAQABAUBAABAQAAQEAAEBAAEBQEAAEBA…

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add xguard --transport http https://xguard-mainnet.maqamapp.workers.dev/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "xguard": {
      "url": "https://xguard-mainnet.maqamapp.workers.dev/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.xguard]
url = "https://xguard-mainnet.maqamapp.workers.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "xguard": {
      "url": "https://xguard-mainnet.maqamapp.workers.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "xguard": {
      "url": "https://xguard-mainnet.maqamapp.workers.dev/mcp"
    }
  }
}

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 10

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

xguard
xguard_discovery_search
Search the x402 Bazaar catalogs reachable through XGuard without knowing a provider or tool name in advance. Example: query='weather', limit=10.
xguard_facilitator
Return XGuard's machine-readable x402 facilitator identity, endpoints, live capabilities, automatic routing policy and pricing. Example: call with no arguments before configuring XGuard as an x402 facilitator.
xguard_health
Return XGuard facilitator and downstream settlement-path health. Example: call with no arguments to inspect XGuard and downstream-route health.
xguard_inspect
Classify and policy-check a transaction without forwarding it. Example: target='https://example.com/pay', method='POST'.
xguard_integration
Return integration, security controls and pricing for the XGuard in-path facilitator URL. Example: call with no arguments to retrieve integration and security-control details.
xguard_protocols
List transaction protocols and edge surfaces recognized by XGuard. Example: call with no arguments to list the transaction protocols XGuard recognizes.
xguard_receipt
Look up a durable XGuard settlement receipt. Example: supply a receipt_id beginning with 'xgr_' followed by 40 lowercase hex characters.
xguard_route
Ask XGuard which live downstream settlement path it would choose for an x402 network/scheme while keeping XGuard as the configured facilitator URL. Example: network='eip155:8453', scheme='exact'.
xguard_safety_test
Score a transaction sample without contacting its target. Example: target='https://example.com/pay', method='POST'.
xguard_supported
Return currently supported x402 payment kinds aggregated from healthy configured settlement providers. Example: call with no arguments before choosing an x402 payment kind.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

xguard_resource_details
removed 25 Aug 2026
xguard_discover
removed 25 Aug 2026
xguard_endpoint_details
removed 25 Aug 2026
xguard_status
removed 25 Aug 2026

Endpoints

URLTransportStateLatencyChecked
https://xguard-mainnet.maqamapp.workers.dev/mcp streamable-http answering 51 ms 11 min ago
https://xguardgate.com/mcp streamable-http answering 160 ms 11 min ago

Alternatives to XGuard — Payment Decision & Discovery

same job, measured the same way
x402 Pay — USDC API Payment Helper
by scriptmasterlabs

Pay for APIs with USDC. Read-only x402 payment discovery, verification, evidence, and status.

5 tools answering
Azeth Protocol
by azeth-protocol

Smart accounts, x402 payments, on-chain reputation, and service discovery for AI agents

68 installs/wk local only
Agent Pay
by joepangallo

Payment gateway for AI agents with tool discovery, provisioning, metering, and reliability tools.

49 installs/wk local only
Secant Agent Research Pack
by jnilrac

Paid MCP web research for agents: search, extraction, citations, and x402 payment discovery.

6 tools answering
VouchSpec Agent Skill Evidence
by mordiaky

Read-only discovery for exact-commit Agent Skill validation, x402 payment, and signed receipts.

answering
Machine Works Broker
by dailytekk

Free evidence capability discovery, quotes and durable unmet requests. No payment or spend.

6 tools answering
Trust
by agntor

Trust layer for AI agents: identity, guard, redact, escrow, and x402 payments.

39 installs/wk local only
X402 Data Gateway
by epistemedeus

Paid x402 and MPP tools for agent discovery, payment safety, data, and DeFi.

29 tools answering

XGuard — Payment Decision & Discovery — questions

Answers built from our own checks of this server.

What can XGuard — Payment Decision & Discovery do?
It exposes 10 tools, read directly from the server on our last check. Among them: xguard_discovery_search, xguard_facilitator, xguard_health, xguard_inspect, xguard_integration, xguard_protocols and 4 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is XGuard — Payment Decision & Discovery working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 184 checks got a reply (0.0%), average response time 51 ms. The bar chart above shows every period we have measured.
Did XGuard — Payment Decision & Discovery ever remove tools?
Yes. xguard_resource_details, xguard_discover, xguard_endpoint_details, xguard_status are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.
The registry lists XGuard — Payment Decision & Discovery as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect XGuard — Payment Decision & Discovery?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does XGuard — Payment Decision & Discovery need an API key?
No. XGuard — Payment Decision & Discovery completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 10 of them are readable on this page. This is what we observed, not what the docs claim.
Is XGuard — Payment Decision & Discovery open source?
We cannot say either way: written in JavaScript, 0 stars on GitHub and 41 open issues, but we could not determine the licence, and without one the code is not open source by default.