Ext Ops Panel
Open dashboard
Comparison

Wayfound vs three.ws Agent Payments

Wayfound is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). three.ws Agent Payments is an MCP server published by nirholas. 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
MarketplaceWayfoundthree.ws Agent Payments
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.5
Downloads/month (npm): 254
Downloads/week (npm): 67
Forks (GitHub): 64
Stars (GitHub): 237
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

Wayfound vs three.ws Agent Payments
FactWayfoundthree.ws Agent Payments
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub237
Forks (GitHub) (differs)No figure on GitHub64
Last releaseNot publishedNot published
Where it runs (differs)Remote server (app.wayfound.ai/sse)On your machine (@three-ws/agentcore-payments-mcp)
Transport (differs)SSEstdio
Tools it declares (differs)4Not published
Environment variables it asks for (differs)1, secrets among them: 14, secrets among them: 2
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/nirholas/three.ws
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded less than an hour ago, requires a keyno 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

Wayfound

In its own words, on Docker MCP Catalog:

Wayfound’s MCP server allows business users to govern, supervise, and improve AI Agents.

three.ws Agent Payments

In its own words, on Official MCP Registry:

Governed x402 payment sessions: pay any endpoint with budget, allowlist & per-tx caps, no key.

How to run each

Wayfound As a remote MCP server

Claude Code
claude mcp add --transport sse wayfound https://app.wayfound.ai/sse

Requires: MCP_API_KEY (secret)

three.ws Agent Payments As a local MCP server: npm package

Claude Code
claude mcp add --env "PAYMENT_SESSION_TOKEN=<YOUR_PAYMENT_SESSION_TOKEN>" --env "THREE_WS_SESSION=<YOUR_THREE_WS_SESSION>" --transport stdio agentcore-payments-mcp -- npx -y @three-ws/agentcore-payments-mcp

Requires: PAYMENT_SESSION_TOKEN (secret), THREE_WS_SESSION (secret)

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

Only Wayfound has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of three.ws Agent Payments publish no list of tools, so we do not compare tools.

Settings each asks for

Only Wayfound asks for

  • MCP_API_KEY (secret)

Only three.ws Agent Payments asks for

  • PAYMENT_SESSION_TOKEN (secret)
  • THREE_WS_BASE
  • THREE_WS_SESSION (secret)
  • THREE_WS_TIMEOUT_MS

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Wayfound · What it can do: three.ws Agent Payments · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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