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.

X402-Broker Universal MCP Gateway & Multi-Agent Swarm Router

REMOTE · X402BROKER.COM

Single-connection MCP gateway discovering and executing 490+ verified MCP & A2A tools.

Available components

84 Trust /100

Last scanned (10 hours ago)

Scores higher than 91% of remote servers

Reachable. Last reached 23 Oct 2026.

Category E-commerce

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 → Why this is hard to score →

Endpoint Security100
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
  • The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability82
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 759 tokens (~47/item across 16 items; 15 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
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 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +24
    • Authorization: unverified → pass ▲ security
    • HSTS header: fail → pass ▲ security
    • First check of Authorization: pass security
    • Tool “cancel_cart” rewrote its description, which is the text the model reads security
    • Tool “cancel_checkout” rewrote its description, which is the text the model reads security
    • Tool “complete_checkout” rewrote its description, which is the text the model reads security
    • Tool “create_cart” rewrote its description, which is the text the model reads security
    • Tool “create_checkout” rewrote its description, which is the text the model reads security
    • Tool “get_cart” rewrote its description, which is the text the model reads security
    • Tool “get_checkout” rewrote its description, which is the text the model reads security
    • Tool “get_order” rewrote its description, which is the text the model reads security
    • Tool “get_product” rewrote its description, which is the text the model reads security
    • Tool “get_product_details” rewrote its description, which is the text the model reads security
    • Tool “lookup_catalog” rewrote its description, which is the text the model reads security
    • Tool “search_catalog” rewrote its description, which is the text the model reads security
    • Tool “search_shop_policies_and_faqs” rewrote its description, which is the text the model reads security
    • Tool “update_cart” rewrote its description, which is the text the model reads security
    • Tool “update_checkout” rewrote its description, which is the text the model reads security
    • Schema quality: 29 → 47 ▼ functional
    • Tool coverage: 0% → 100% ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • Tool “cancel_cart” now declares an output schema ▲ functional
    • Tool “cancel_checkout” now declares an output schema ▲ functional
    • Tool “complete_checkout” now declares an output schema ▲ functional
    • Tool “create_cart” now declares an output schema ▲ functional
    • Tool “create_checkout” now declares an output schema ▲ functional
    • Tool “get_cart” now declares an output schema ▲ functional
    • Tool “get_checkout” now declares an output schema ▲ functional
    • Tool “get_order” now declares an output schema ▲ functional
    • Tool “get_product” now declares an output schema ▲ functional
    • Tool “get_product_details” now declares an output schema ▲ functional
    • Tool “lookup_catalog” now declares an output schema ▲ functional
    • Tool “search_catalog” now declares an output schema ▲ functional
    • Tool “search_shop_policies_and_faqs” now declares an output schema ▲ functional
    • Tool “update_cart” now declares an output schema ▲ functional
    • Tool “update_checkout” now declares an output schema ▲ functional
    • The server now declares the “prompts” capability functional
    • The server now declares the “resources” capability functional
    • First check of Capabilities: pass functional
    • First check of Schema quality: 100 functional
    • First check of Tool coverage: 100 functional
    • Schema quality: fair → good functional
    • New prompt “ucp_catalog_discovery” functional
    • New resource “ucp-checkout-widget” functional
    • Server version: 2026-08-25 → 7.0.17 functional
    • “cancel_cart” reworded the description of “cart_id” cosmetic
    • “cancel_checkout” reworded the description of “checkout_id” cosmetic
    • “complete_checkout” reworded the description of “checkout_id” cosmetic
    • “complete_checkout” reworded the description of “payment_data” cosmetic
    • “create_cart” reworded the description of “line_items” cosmetic
    • “create_checkout” reworded the description of “buyer” cosmetic
    • “create_checkout” reworded the description of “line_items” cosmetic
    • “get_cart” reworded the description of “cart_id” cosmetic
    • “get_checkout” reworded the description of “checkout_id” cosmetic
    • “get_order” reworded the description of “order_id” cosmetic
    • “get_product” reworded the description of “catalog” cosmetic
    • “get_product” reworded the description of “product_id” cosmetic
    • “get_product_details” reworded the description of “product_id” cosmetic
    • “lookup_catalog” reworded the description of “catalog” cosmetic
    • “lookup_catalog” reworded the description of “ids” cosmetic
    • “search_catalog” reworded the description of “catalog” cosmetic
    • “search_catalog” reworded the description of “query” cosmetic
    • “search_shop_policies_and_faqs” reworded the description of “query” cosmetic
    • “update_cart” reworded the description of “cart_id” cosmetic
    • “update_cart” reworded the description of “line_items” cosmetic
    • “update_checkout” reworded the description of “checkout_id” cosmetic
    • “update_checkout” reworded the description of “payment” cosmetic
  • 21 Oct 26 59

    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 23 Oct 2026 · Probed https://x402broker.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=x402broker.com CN=YE1,O=Let's Encrypt,C=US 19 Oct 2026 17 Jan 2027 ECDSA 256 ECDSA-SHA384 56cb4b4f1e5abf7eef01406e8fe5177beb6
SANs: *.x402broker.com, x402broker.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of x402broker.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
x402broker.com. present 2371 13 Verified
x402broker.com. Verified address RRset verified with the apex keys
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="x402broker.com", resource_metadata="https://x402broker.com/.well-known/oauth-protected-resource"

Bearer realm="x402broker.com", resource_metadata="https://x402broker.com/.well-known/oauth-protected-resource"
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload

Protected resource metadata

Document https://x402broker.com/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://x402broker.com
Authorisation server https://x402broker.com

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://x402broker.com/api/mcp Verified 200
http (plaintext) http://x402broker.com/api/mcp HTTPS enforced 301 https://x402broker.com/api/mcp
MCP tools · 15 exposed · ~734 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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
cancel_cart ~42

Cancel an active shopping cart session by cart_id. Example: cancel_cart(cart_id='cart_1')

NameTypeReqDescription
cart_idstring–Shopping cart identifier to cancel.
NameTypeReqDescription
storestringyesMerchant domain identifier.
ucp_versionstring–Supported UCP specification version.

No examples provided.

cancel_checkout ~44

Cancel an uncommitted checkout session by checkout_id. Example: cancel_checkout(checkout_id='chk_1')

NameTypeReqDescription
checkout_idstring–Checkout session identifier to cancel.
NameTypeReqDescription
storestringyesMerchant domain identifier.
ucp_versionstring–Supported UCP specification version.

No examples provided.

complete_checkout ~60

Finalize checkout settlement via Base USDC x402 or Stripe MPP. Example: complete_checkout(checkout_id='chk_1')

NameTypeReqDescription
checkout_idstring–Checkout session identifier.
payment_dataobject–Signed payment proof or token payload.
NameTypeReqDescription
storestringyesMerchant domain identifier.
ucp_versionstring–Supported UCP specification version.

No examples provided.

create_cart ~46

Create a new shopping cart with initial line items. Example: create_cart(line_items=['agd-pass-2000'])

NameTypeReqDescription
line_itemsarray–Line items to place in the cart.
NameTypeReqDescription
storestringyesMerchant domain identifier.
ucp_versionstring–Supported UCP specification version.

No examples provided.

create_checkout ~56

Create a UCP checkout session for API passes or credits. Example: create_checkout(line_items=['agd-pass-2000'])

NameTypeReqDescription
buyerobject–Optional buyer contact details.
line_itemsarray–Line items for checkout.
NameTypeReqDescription
storestringyesMerchant domain identifier.
ucp_versionstring–Supported UCP specification version.

No examples provided.

get_cart ~41

Retrieve current shopping cart items and totals by cart_id. Example: get_cart(cart_id='cart_1')

NameTypeReqDescription
cart_idstring–Shopping cart identifier.
NameTypeReqDescription
storestringyesMerchant domain identifier.
ucp_versionstring–Supported UCP specification version.

No examples provided.

get_checkout ~41

Retrieve checkout session status and totals by checkout_id. Example: get_checkout(checkout_id='chk_1')

NameTypeReqDescription
checkout_idstring–Checkout session identifier.
NameTypeReqDescription
storestringyesMerchant domain identifier.
ucp_versionstring–Supported UCP specification version.

No examples provided.

get_order ~42

Retrieve fulfilled order receipt and API pass key by order_id. Example: get_order(order_id='ord_1')

NameTypeReqDescription
order_idstring–Completed order identifier.
NameTypeReqDescription
storestringyesMerchant domain identifier.
ucp_versionstring–Supported UCP specification version.

No examples provided.

get_product ~53

Retrieve full product or API pass metadata by product_id. Example: get_product(product_id='agd-pass-2000')

NameTypeReqDescription
catalogobject–Optional catalog context.
product_idstring–Target product identifier.
NameTypeReqDescription
storestringyesMerchant domain identifier.
ucp_versionstring–Supported UCP specification version.

No examples provided.

get_product_details ~45

Retrieve product pricing and variant IDs by product_id. Example: get_product_details(product_id='agd-pass-2000')

NameTypeReqDescription
product_idstring–Product identifier to inspect.
NameTypeReqDescription
storestringyesMerchant domain identifier.
ucp_versionstring–Supported UCP specification version.

No examples provided.

lookup_catalog ~50

Batch lookup catalog items by product identifier list. Example: lookup_catalog(ids=['agd-pass-2000'])

NameTypeReqDescription
catalogobject–Optional catalog context.
idsarray–Product identifiers to retrieve.
NameTypeReqDescription
storestringyesMerchant domain identifier.
ucp_versionstring–Supported UCP specification version.

No examples provided.

search_catalog ~51

Search the UCP product and API credit catalog by keyword. Example: search_catalog(query='pass')

NameTypeReqDescription
catalogobject–Optional catalog scope filter.
querystring–Search keyword or capability filter.
NameTypeReqDescription
storestringyesMerchant domain identifier.
ucp_versionstring–Supported UCP specification version.

No examples provided.

search_shop_policies_and_faqs ~54

Search store privacy, refund, terms of service, and SLA policies. Example: search_shop_policies_and_faqs(query='refund')

NameTypeReqDescription
querystring–Policy topic or question keyword.
NameTypeReqDescription
storestringyesMerchant domain identifier.
ucp_versionstring–Supported UCP specification version.

No examples provided.

update_cart ~56

Update line item quantities in an active shopping cart. Example: update_cart(cart_id='cart_1', line_items=[])

NameTypeReqDescription
cart_idstring–Shopping cart identifier.
line_itemsarray–Updated cart line items.
NameTypeReqDescription
storestringyesMerchant domain identifier.
ucp_versionstring–Supported UCP specification version.

No examples provided.

update_checkout ~53

Update buyer or payment rail details on a checkout session. Example: update_checkout(checkout_id='chk_1')

NameTypeReqDescription
checkout_idstring–Checkout session identifier.
paymentobject–Selected payment method configuration.
NameTypeReqDescription
storestringyesMerchant domain identifier.
ucp_versionstring–Supported UCP specification version.

No examples provided.

Install

How do I install the X402-Broker Universal MCP Gateway & Multi-Agent Swarm Router server?

X402-Broker Universal MCP Gateway & Multi-Agent Swarm Router is a hosted endpoint at https://x402broker.com/api/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 · x402broker.com

# add to Claude Code
claude mcp add --transport http com-x402broker-mcp-gateway 'https://x402broker.com/api/mcp'
Common questions

What is the X402-Broker Universal MCP Gateway & Multi-Agent Swarm Router server?

X402-Broker Universal MCP Gateway & Multi-Agent Swarm Router is listed in the public MCP registry as com.x402broker/mcp-gateway. Single-connection MCP gateway discovering and executing 490+ verified MCP & A2A tools. This page covers its hosted endpoint (https://x402broker.com/api/mcp).

Is the X402-Broker Universal MCP Gateway & Multi-Agent Swarm Router server safe to use?

X402-Broker Universal MCP Gateway & Multi-Agent Swarm Router scores 84 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 X402-Broker Universal MCP Gateway & Multi-Agent Swarm Router server expose?

X402-Broker Universal MCP Gateway & Multi-Agent Swarm Router exposes 15 tools: search_catalog, lookup_catalog, get_product, get_product_details, search_shop_policies_and_faqs, and 10 more. Their descriptions and schemas cost roughly 734 tokens of context every time the server is loaded.

Does the X402-Broker Universal MCP Gateway & Multi-Agent Swarm Router server require authentication?

Yes. X402-Broker Universal MCP Gateway & Multi-Agent Swarm Router asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the X402-Broker Universal MCP Gateway & Multi-Agent Swarm Router server still maintained?

X402-Broker Universal MCP Gateway & Multi-Agent Swarm Router is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.