Ext Ops Panel
Open dashboard
Comparison

Autonomy x402 Tools vs io.github.gigsoul/x402-api

Autonomy x402 Tools is an MCP server published by Autonomy-Labs-Tech. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.gigsoul/x402-api is an MCP server published by gigsoul. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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
MarketplaceAutonomy x402 Toolsio.github.gigsoul/x402-api
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 3.0.0
Forks (GitHub): 0
Stars (GitHub): 0
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

Autonomy x402 Tools vs io.github.gigsoul/x402-api
FactAutonomy x402 Toolsio.github.gigsoul/x402-api
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (www.autonomylabsweb.tech/api/mcp)Remote server (gig-x402-api.jayson-be1.workers.dev)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/autonomy-labs-tech/taskmarket-mcpgithub.com/gigsoul/x402
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Answered with HTTP 404 (5 days ago)Responded 4 days 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

Autonomy x402 Tools

In its own words, on Official MCP Registry:

Pay-per-call agent tools over x402: site audits, llms.txt generation, wallet watch, catalog.

io.github.gigsoul/x402-api

In its own words, on Official MCP Registry:

AI API for marketing, content and outreach. 22 endpoints. Pay with USDC on Base via x402.

How to run each

Autonomy x402 Tools As a remote MCP server

Claude Code
claude mcp add --transport http autonomy-x402-tools https://www.autonomylabsweb.tech/api/mcp

io.github.gigsoul/x402-api As a remote MCP server

Claude Code
claude mcp add --transport http x402-api https://gig-x402-api.jayson-be1.workers.dev

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

Only the endpoint of io.github.gigsoul/x402-api responded at the last daily 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: Autonomy x402 Tools · What it can do: io.github.gigsoul/x402-api · 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