XGuard Universal Paid AI Agent + Secretless Gateway
XGuard operates ONE remote MCP server at https://api.xguardgate.com/mcp, on the same host as its OpenAPI, its A2A JSON-RPC endpoint and its x402 facilitator relay. It is Streamable HTTP, speaks MCP protocol version 2026-07-28, identifies itself as serverInfo {xguard-universal-paid-secretless-gateway, 5.1.0}, and answers initialize and tools/list anonymously with exactly three tools, each carrying a real JSON Schema inputSchema and MCP tool annotations (readOnlyHint / destructiveHint / idempotentHint / openWorldHint). The initialize instructions and the provider's README both say the live tools/list is deliberately small: the paid-outcome chokepoint is xguard_execute, and the older explicit tool names that llms-install.md still lists (xguard.web.fetch, xguard_secretless_egress, xguard_proofrail, ...) are "compatibility references, not the default catalog". A paid tool call returns an HTTP 200 JSON-RPC result with isError: true and the x402 PaymentRequired challenge in both structuredContent and content[0].text; a funded x402 MCP client retries the identical arguments with params._meta["x402/payment"] and receives settlement in result._meta["x402/payment-response"]. Authorship is not in question: the tool names, the serverInfo name, the canonical-identity block in every response header set (x-xguard-canonical-mcp) and the MCP Registry entry io.github.moelayyan90/xguard-control-plane all name this provider.
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Endpoint
Hosted endpoint · transport streamable-http
Connect
This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):
For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:
If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:
Tools
xguard_discover— Inspect executable outcomes, prices and examples. Free; no setup.xguard_execute— Extract multi-page evidence, compare structured product offers, or merge feeds. intent:'demo' is free. Paid work returns an x402 PaymentRequired tool result; a funded x402 MCP client authorizes and retries with params._meta['x402/payment'], preserving the signed quote.xguard_get_result— Recover a paid outcome using its payment identifier and original signed quote; never charges or executes again. The quote is a bearer recovery credential.
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.
Work with this as data
Every MCP server here is available over the APIs.io API and to AI agents over MCP.