Ext Ops Panel
Open dashboard
Comparison

x402 Gateway — Inspect Paid API Terms vs io.github.89rat/code402

x402 Gateway — Inspect Paid API Terms is an MCP server published by scriptmasterlabs.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.89rat/code402 is an MCP server published by 89rat. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacex402 Gateway — Inspect Paid API Termsio.github.89rat/code402
Official MCP Registry Listed
Version: 1.3.0
No figure published
Not marked · First seen
Listed
Version: 1.0.1
No figure published
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

x402 Gateway — Inspect Paid API Terms vs io.github.89rat/code402
Factx402 Gateway — Inspect Paid API Termsio.github.89rat/code402
Marketplaces that list it11
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp-x402-gitlab-main.onrender.com/mcp)Remote server (rail.hcrb.in/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/89rat/m2m-exchange
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)not checked yetResponded 35 h ago

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

x402 Gateway — Inspect Paid API Terms

In its own words, on Official MCP Registry:

Discover x402 paid APIs and inspect fresh payment requirements before authorizing spend.

io.github.89rat/code402

In its own words, on Official MCP Registry:

Discover machine-payable APIs, probe x402 payment terms, and run seller operations. Non-custodial.

How to run each

x402 Gateway — Inspect Paid API Terms As a remote MCP server

Claude Code
claude mcp add --transport http x402-gateway https://mcp-x402-gitlab-main.onrender.com/mcp

io.github.89rat/code402 As a remote MCP server

Claude Code
claude mcp add --transport http code402 https://rail.hcrb.in/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only io.github.89rat/code402 has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: x402 Gateway — Inspect Paid API Terms · What it can do: io.github.89rat/code402 · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built