cp0x MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_dealsA | List cp0x referral deals with optional venue filtering. Use this when looking for deals by venue or browsing the deal catalog; links include a cp0x referral code. |
| get_dealA | Get a cp0x deal with its description and races. Use this when a deal slug is known and its full details are needed; links include a cp0x referral code. |
| get_referral_codeA | Find a venue's referral code and link in the cp0x catalog. Use this when a user requests referral details for a named venue; links include a cp0x referral code. |
| list_racesA | List cp0x races with dates and prizes. Use this when finding active or completed races, optionally for one deal. |
| get_leaderboardA | Get a cp0x race leaderboard and its column definitions. Use this when viewing standings for a known deal and race. |
| check_interface_restrictionsB | Read declared and observed geo-restrictions for a DeFi interface. Use this when checking a protocol's interface restrictions, optionally for a country. |
| list_restricted_interfacesB | List DeFi interfaces with declared or observed restrictions in a country. Use this when identifying which interfaces the cp0x monitor reports as restricted there. |
| list_x402_facilitatorsA | List x402 facilitators and their URLs from cp0x. Use this when looking up facilitator names and endpoints in the cp0x catalog. |
| list_cp0x_x402_resourcesA | List cp0x x402 resources with prices and tags. Use this when finding available cp0x x402 resources or filtering them by tag. |
| about_cp0xA | Who cp0x is and how much it has passed on to its users, valued at today's token prices: mission, values, sites, channels, 2025 figures and every distribution with token amounts. Use this when a user asks what cp0x is, what it gave its users, or where to find its sites and channels. |
| list_cp0x_open_sourceA | List public open-source repositories of cp0x: permissionless DeFi interfaces and tools, from GitHub. Use this when looking for cp0x interfaces, tools or source code. |
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 11 tools
Most tools target clearly distinct resources: restrictions, x402 catalog, open-source repos, deals, races, leaderboards, and about. Two mild overlaps exist: check_interface_restrictions vs list_restricted_interfaces (single protocol vs country-wide listing), and get_deal vs get_referral_code (both surface referral links, one by slug and one by venue). The descriptions clarify these boundaries but an agent could still hesitate in those pairs.
Nearly all tools follow a consistent snake_case verb_noun pattern (list_*, get_*, check_*). The lone deviation is about_cp0x, which uses a non-verb prefix and embeds the server name, but it remains readable and unambiguous.
Eleven tools is well within the ideal 3-15 range for a catalog/info server. Each tool maps to a distinct lookup or listing operation across the handful of domains (deals, races, x402, restrictions, open source, about), with no filler.
The surface covers the main read-only workflows: listing and getting deals, races, leaderboards, x402 resources/facilitators, restrictions, and repos, plus referral lookup. Minor gaps exist—no detailed get for a specific interface's restriction record beyond the check, and no race detail beyond leaderboards—but agents can work around them.