x402 Tools vs io.github.halowerk/halowerk-mcp
x402 Tools is an MCP server published by foxxx009. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.halowerk/halowerk-mcp is an MCP server published by halowerk. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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
| Marketplace |  x402 Tools |  io.github.halowerk/halowerk-mcp |
|---|---|---|
| Official MCP Registry | Listed Version: 1.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.1.1 Downloads/month (npm): 241 Downloads/week (npm): 78 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
| Fact | x402 Tools | io.github.halowerk/halowerk-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (fitze-x402-seller.app.workbuddy.host/mcp) | On your machine (halowerk-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 5, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/foxxx009/x402-tools-mcp | github.com/halowerk/halowerk-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: last check 2 days ago returned HTTP 405 | no remote endpoint we check |
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 Tools
Pay-per-call research tools for AI agents, paid via x402 USDC. Remote MCP, one free tool.
io.github.halowerk/halowerk-mcp
134 paid APIs as MCP tools, billed per call in USDC on Base. No account, no login.
How to run each
x402 Tools As a remote MCP server
claude mcp add --transport http x402-tools-mcp https://fitze-x402-seller.app.workbuddy.host/mcpio.github.halowerk/halowerk-mcp As a local MCP server: npm package
claude mcp add --env "HALOWERK_PRIVATE_KEY=<YOUR_HALOWERK_PRIVATE_KEY>" --transport stdio halowerk-mcp -- npx -y halowerk-mcpRequires: HALOWERK_PRIVATE_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only x402 Tools 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
The marketplaces of x402 Tools publish no settings it asks for, so we do not compare settings.
What it can do: x402 Tools · What it can do: io.github.halowerk/halowerk-mcp · 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.