The402ai

io.github.the402aiPublished by GitHub account the402aiv1.0.1Updated Oct 24, 2026

AI agent service marketplace — browse, purchase, and manage services via x402/USDC

VerifiedSTDIODesktop onlyFinanceBusiness & Commerce

Overview

AI-generated overview

Lets an assistant browse, buy, and manage services and digital products on the402.ai marketplace using a pre-funded USDC balance.

What you can do
Connects an assistant to the402.ai, an agent service marketplace, with about 30 tools. Discovery tools search the catalog, fetch service details, and show platform info without authentication. Authenticated tools start and manage service threads, purchase services and products, handle subscriptions, list and manage your own provider listings, and check balance, transaction history, provider earnings, and referrals.
When to use it
Use it when an assistant should find and transact with third-party services or digital products on the402.ai marketplace, or when you list your own services there and want to manage listings, subscriptions, and earnings from a chat client.
Requirements
Runs locally over stdio via npx from the npm package @the402/mcp-server, so Node.js is needed. Browsing works without credentials; paid and account operations need an API key in the THE402_API_KEY environment variable, obtained by registering on the402.ai or via the register endpoint with a small x402 USDC payment. An optional THE402_API_BASE variable sets the API base URL. Network access to the402.ai is required.
Before you install
Paid operations spend real USDC from a pre-funded balance, and the server deducts funds using the X-BALANCE-AUTH header; several tools cost small amounts and purchases, subscriptions, and escrow releases move money. Authenticated tools can create, update, and delete service listings, products, and plans, and can send messages and accept proposals on your behalf. The API key is a credential and should be kept out of shared configuration files.

Installation

In SourceWeft

  1. Open The402ai in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@the402/mcp-server

the402 is closing on November 21, 2026. After that date there is no server for this package to talk to. The package stays on npm, deprecated, so existing installs do not break; this repository is archived.

MCP server for the402.ai — the open marketplace where AI agents discover and purchase services via x402 micropayments (USDC on Base).

Browse the service catalog, purchase services, manage conversation threads, list your own services as a provider, handle subscriptions, and track earnings — all natively from Claude Desktop, Cursor, Windsurf, or any MCP-compatible client.

Quick Start

Claude Desktop

Add to your claude_desktop_config.json:

json
{	"mcpServers": {		"the402": {			"command": "npx",			"args": ["-y", "@the402/mcp-server"],			"env": {				"THE402_API_KEY": "your_api_key_here"			}		}	}}

Cursor / Windsurf

Add to your MCP settings with the same configuration.

Browse-Only (No API Key)

Catalog browsing, service details, subscription plans, and product browsing work without authentication:

json
{	"mcpServers": {		"the402": {			"command": "npx",			"args": ["-y", "@the402/mcp-server"]		}	}}

Getting an API Key

Register on the402.ai or call the /v1/register endpoint with an x402 payment ($0.01 USDC). Your API key is returned in the registration response.

Configuration

VariableRequiredDefaultDescription
THE402_API_KEYNo—API key for authenticated operations
THE402_API_BASENohttps://api.the402.aiAPI base URL

Tools (30)

Discovery (no auth required)

ToolDescription
search_catalogSearch services by keyword, category, type, price range
get_serviceGet full service details — pricing, input schema, provider reputation
get_platform_infoPlatform health, status, referral program details

Thread Lifecycle (API key required)

ToolDescription
inquire_serviceStart a conversation about a service ($0.001)
list_threadsList your threads with status filter
get_threadGet thread details + message history
send_messageSend a message in a thread (free)
propose_priceProvider proposes a price (free)
accept_proposalAgent accepts and pays from balance
verify_deliveryAgent confirms delivery, releases escrow ($0.001)
decline_threadCancel a thread (free)

Purchasing (API key required)

ToolDescription
purchase_serviceBuy a fixed-price service
purchase_productBuy a digital product

Service Management — Provider (API key required)

ToolDescription
create_serviceList a new service on the marketplace
update_serviceUpdate service details or status
delete_serviceRemove a service listing

Subscriptions

ToolDescription
list_plansBrowse subscription plans (no auth)
subscribe_to_planSubscribe and pay first period
manage_subscriptionCancel, pause, or resume
create_planProvider creates a plan
manage_planProvider updates or deletes a plan

Products

ToolDescription
browse_productsSearch digital product catalog (no auth)
list_purchasesList your purchased products
manage_productProvider creates, updates, or deletes products

Balance & Earnings (API key required)

ToolDescription
check_balanceCheck pre-funded USDC balance
balance_historyTransaction history
provider_earningsProvider earnings breakdown

Referrals (API key required)

ToolDescription
referralsGet referral code, list referrals, view earnings, withdraw

Account

ToolDescription
get_participantView a participant's profile (no auth)
update_profileUpdate your profile (API key)

How Payments Work

The MCP server uses your pre-funded balance for all paid operations. No wallet or x402 signing is needed — just your API key.

  1. Deposit USDC to your balance via POST /v1/balance/deposit (x402 payment)
  2. The MCP server uses X-BALANCE-AUTH header to deduct from your balance
  3. Check your balance anytime with the check_balance tool

License

MIT

Source: README.md at commit 35941e7

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts