x402-atlas-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ATLAS_DATA | No | Where data files are fetched from | |
| ATLAS_SITE | No | Where site files are fetched from | |
| ATLAS_CACHE | No | Where fetched files are kept | |
| ATLAS_STORE | No | A folder of `market-<date>.json` and `whales-<date>.json`; no network is used |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| market_todayB | The x402 market on Base as of the newest published day: payments settled, USDC moved, buyer wallets, sellers paid, operators, agents at work, and the busiest sellers by real payments. |
| searchA | Find sellers that do a job. Matches names and descriptions word by word, and reads intent (e.g. 'weather', 'enrich a person', 'llm inference') into the Atlas categories. Ranked by x402 payments on the newest day, then by self-reported paid calls. Also names matching operators. |
| sellerB | One seller's card: what it sells, its price range and how that sits against rivals, self-reported paid calls, rank in the registry, the last days of its history, and what the chain says — x402 payments, USDC, payer wallets, concentration, and which other hosts share its wallet. |
| operatorA | The hosts one operator runs — the hosts the registry lists under the same wallet — with their combined x402 payments and USDC on the newest day. Give any host in the group or the group's name. |
| agents_at_workB | Buyer wallets whose x402-settled payments reached three or more sellers on the newest day: the honest signal of an agent at work. Payments, USDC, categories bought, and the sellers paid. |
| compareA | Two to five seller hosts side by side: what each sells, its price range, x402 payments and USDC on the newest chain day, payer wallets, concentration, self-reported 30-day paid calls, and its operator group. Every row names the dates its figures come from. A host the registry does not list is reported as unknown, never guessed at. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct entity or view: operator (wallet-group aggregate), market_today (whole-market snapshot), search (discovery), seller (single entity), agents_at_work (buyer wallets), and compare (multi-entity diff). Minor overlap exists between seller and compare, and between operator and market_today, but descriptions make the boundaries clear enough.
All names are lowercase snake_case and readable, but conventions are mixed: some are bare nouns (operator, seller), some are noun phrases (market_today, agents_at_work), and two are verbs (search, compare). No predictable verb_noun pattern, though nothing is truly confusing.
Six tools are well-scoped for a read-only market/registry browser covering market, search, entity, operator, agent, and comparison views. Each tool earns its place with no redundancy.
The surface covers the main lifecycle for browsing x402 market data: market snapshot, search, single seller, operator grouping, buyers, and side-by-side comparison. Minor gaps like time-series history or category listing exist but agents can work around them.