Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

XGuard — Payment Decision & Discovery

REMOTE · XGUARDGATE.COM · SCANNED AUG 25

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

Available components

−56 this week 18 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety

Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.

Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 4 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

How do I install the XGuard — Payment Decision & Discovery MCP server?

XGuard — Payment Decision & Discovery is a hosted endpoint at https://xguardgate.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · xguardgate.com

# add to Claude Code
claude mcp add --transport http moelayyan90-xguard 'https://xguardgate.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "moelayyan90-xguard": {
      "url": "https://xguardgate.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "moelayyan90-xguard": {
      "type": "http",
      "url": "https://xguardgate.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.moelayyan90-xguard]
url = "https://xguardgate.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "moelayyan90-xguard": {
      "type": "remote",
      "url": "https://xguardgate.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add moelayyan90-xguard --url 'https://xguardgate.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  moelayyan90-xguard:
    url: "https://xguardgate.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "moelayyan90-xguard": {
      "Transport": "http",
      "Url": "https://xguardgate.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add moelayyan90-xguard -t streamable-http -u 'https://xguardgate.com/mcp'
// mcp.json
{
  "mcpServers": {
    "moelayyan90-xguard": {
      "type": "http",
      "url": "https://xguardgate.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 23 Aug 26 −58
    • Endpoint reachability: reachable → not serving MCP security
    • Stability: 0.17 → unverified security
    • Authorization: fail → unverified security
    • HTTPS: pass → unverified security
    • HSTS header: pass → fail security
    • Transport: pass → fail security
    • Tool coverage: 100 → unverified functional
    • Capabilities: pass → unverified functional
  • 22 Aug 26 +1
    • Authorization: unverified → fail security
    • DNSSEC: unverified → fail security
    • HSTS header: unverified → pass security
    • TLS certificate: unverified → pass security
    • Transport: fail → pass security
    • Endpoint reachability: unreachable → reachable functional
    • MCP protocol: unverified → pass functional
    • Stability: unverified → 0.17 functional
    • Tool coverage: unverified → 100 functional
  • 21 Aug 26 0
    • Endpoint reachability: reachable → unreachable security
    • DNSSEC: fail → unverified security
    • Stability: 0.10 → unverified security
    • Authorization: fail → unverified security
    • TLS certificate: pass → unverified security
    • HSTS header: pass → unverified security
    • Transport: pass → fail security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 19 Aug 26 +1
    • Server version: 0.6.1 → 0.6.2 functional
    • Server version: 0.6.0 → 0.6.1 functional
  • 18 Aug 26 0
    • Stability: unverified → 0.03 functional
  • 17 Aug 26 74

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 25 Aug 2026 · Probed https://xguardgate.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=xguardgate.com CN=WE1,O=Google Trust Services,C=US 24 Aug 2026 22 Nov 2026 ECDSA 256 ECDSA-SHA256 8995c4536ea1ce201387ca6edcfed24e
SANs: xguardgate.com, changemandate.xguardgate.com, *.changemandate.xguardgate.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b
DNSSEC insecure

Validation of xguardgate.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
xguardgate.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 405
Header Value
x-content-type-options nosniff
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://xguardgate.com/mcp HTTP error 405
http (plaintext) http://xguardgate.com/mcp Inconclusive 404
MCP tools · 5 exposed · ~477 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
xguard_discover ~104

Search XGuard's x402 catalog or list recent entries. Returns matching HTTP or MCP resources. Example: query='weather API', type='http'.

NameTypeReqDescription
limitintegerMaximum results to return (1-100; default 10).
payTostringFilter by exact payment-recipient address.
querystringSearch phrase; omit to list recent resources.
typestringOptional resource kind: http or mcp.

No output schema declared.

No examples provided.

xguard_payment_decision ~227

Paid only when XGuard completes the requested ALLOW/REVIEW/BLOCK decision and durable evidence record. It never executes the underlying payment. Reusing the same requestId is idempotent and must not create a second fee.

NameTypeReqDescription
amountstringyesPositive decimal amount as a string; never send card credentials.
assetstring
currencystringyes
expectedAmountstring
expectedPayeestring
expiresAtstring
merchantOriginstring
metadataobject
networkstring
offerIdstring
payeestringyes
paymentReferencestring
providerstringyesDeclared payment provider or generic_http.
railstringyesPayment rail such as card, stripe, paypal, x402, crypto_wallet, coinbase, bank_transfer, or another safe identifier.
requestIdstringyesCaller-generated idempotency identifier for this XGuard decision request.

No output schema declared.

No examples provided.

xguard_payment_offer ~62

Free optional pre-payment offer. Use when a user or autonomous agent is about to spend money and should be given the choice to verify and document the transaction with XGuard. Calling this offer does not charge an XGuard fee and does not execute the underlying payment.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

xguard_resource_details ~53

Look up one exact XGuard catalog resource by URL or key and return matching records. Example: resource='https://api.example.com/pay'.

NameTypeReqDescription
resourcestringyesExact resource URL or XGuard resource key.

No output schema declared.

No examples provided.

xguard_status ~31

Return live XGuard mainnet gateway health and discovery statistics. Example: call with no arguments before routing traffic.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the XGuard — Payment Decision & Discovery MCP server?

XGuard — Payment Decision & Discovery is an MCP server listed in the public MCP registry as io.github.moelayyan90/xguard. Payment decisions, durable evidence, x402 resource discovery and live gateway status for AI agents. This page covers its hosted endpoint (https://xguardgate.com/mcp).

Is the XGuard — Payment Decision & Discovery MCP server safe to use?

XGuard — Payment Decision & Discovery scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the XGuard — Payment Decision & Discovery MCP server expose?

XGuard — Payment Decision & Discovery exposes 5 tools: xguard_payment_offer, xguard_payment_decision, xguard_discover, xguard_resource_details, xguard_status. Their descriptions and schemas cost roughly 477 tokens of context every time the server is loaded.

Does the XGuard — Payment Decision & Discovery MCP server require authentication?

No. We connected to XGuard — Payment Decision & Discovery without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the XGuard — Payment Decision & Discovery MCP server still maintained?

XGuard — Payment Decision & Discovery is still listed as active in the MCP registry. We last reached this channel on 25 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.