cp0x MCP

A read-only MCP server over cp0x public data, owned by cp0x.

Tools

Results include source attribution and a stale flag; failures can include an error field. Referral codes are returned as published, without inventing missing codes.

Freshness and retry fields for upstream data (about_cp0x always returns stale: false and omits upstream timing fields):

• stale: true when expired cached data is returned because a refresh failed or requests are paused.

• fetched_at: UTC timestamp of the oldest upstream response used, or null when none is available.

• age_s: age in seconds of the oldest response, or null when none is available.

• stale_since: UTC timestamp when the oldest response's cache TTL expired for a stale result; otherwise null.

• retry_after_s: included with upstream errors; integer seconds before retrying when a budget, backoff, or negative cache blocks the request, or null for the initial ordinary failure.

For check_interface_restrictions, country_match contains national and close_only flags, matching regional codes in regions, and status, the status of the declaration that produced the match (null when no declaration matches); country_match is null when no country is supplied. For each entry from list_restricted_interfaces, scope is national, close_only, regional, or observed, in that priority order. The declared_status field carries the originating layer's status for national, close-only, and regional matches; it is null for observed-only matches. When multiple declarations match, both status fields use the first layer in that scope priority order. The close_only_layers field lists layers that allow closing positions only; regions lists matching subdivisions such as CA-ON.

Example questions: “What referral deals are available for Extended?”, “Which races are active?”, and “What interface restrictions does the monitor report for Aave in the US?”

Related MCP server: MCP-Server-Aster-DEX

Connect

Public Streamable HTTP URL: https://mcp.cp0x.com/mcp

No authentication is required.

Claude (connectors / Desktop)

Add a remote MCP server by URL using https://mcp.cp0x.com/mcp in Claude connectors or Claude Desktop, with no authentication.

ChatGPT

Add a remote MCP server by URL using https://mcp.cp0x.com/mcp as a custom MCP connector, with no authentication.

Cursor

Add a remote MCP server by URL in mcp.json:

{
  "mcpServers": {
    "cp0x": {
      "url": "https://mcp.cp0x.com/mcp"
    }
  }
}

Perplexity

Add a remote MCP server by URL using https://mcp.cp0x.com/mcp; select authentication None.

Data sources and freshness

Monitor data is a published repository snapshot, not a live probe. Its version comes from the catalog's meta.generated field and is returned as data_version by check_interface_restrictions. Observations describe the recorded checks; missing probes do not establish availability.

Caches are local to each server instance and refresh on demand after expiry. If an upstream request fails, an existing cached response can be returned with stale set to true; without cached data, the result contains an error. Cache TTL does not guarantee that the upstream data has changed.

Rate limits

The HTTP server limits requests per caller IP to 60 requests/minute by default, configurable with --per-ip-per-minute. Requests over the limit receive HTTP 429 with a Retry-After header in seconds.

The upstream cp0x.com API also limits requests to 60 requests/minute per IP. The server's outgoing IP is shared by its upstream requests; cached reads reduce upstream traffic.

Each server instance shares a budget of 45 upstream requests per minute per host, keyed by host and port, across all tools in a rolling 60-second window. Only actual upstream calls consume budget; cache hits do not. When the budget is exhausted, expired cached data is returned with stale set to true; without cached data, results include an error and retry_after_s. An upstream HTTP 429 triggers host-wide backoff according to Retry-After (60 seconds if missing or nonnumeric), with the same stale fallback. Ordinary failures without cached data are negatively cached for 30 seconds per URL; repeats return an error and remaining retry_after_s without another upstream call. The initial ordinary failure reports retry_after_s as null.

Run locally

Install from the repository with Python 3.10 or later:

pip install -e .

Run over stdio:

cp0x-mcp --transport stdio

Run over HTTP:

cp0x-mcp --transport http --host 127.0.0.1 --port 8000 --allowed-host localhost:8000 --allowed-host 127.0.0.1:8000

The HTTP routes are /mcp and /health. Configure --allowed-host to match the client's Host header, including a port where needed. When no allowlist is supplied, localhost and 127.0.0.1 are allowed with or without ports.

Deploy behind a reverse proxy

Uvicorn reads FORWARDED_ALLOW_IPS to decide which proxies may supply forwarded client IPs. Set it to the reverse proxy's IP address so the caller rate limit uses the original client IP from X-Forwarded-For. Without a trusted proxy setting, all callers through an untrusted proxy share one rate-limit bucket keyed by the proxy IP.

The Docker image sets FORWARDED_ALLOW_IPS="*". With this setting, port 8000 must be reachable only by the reverse proxy. Otherwise, replace * with the proxy IP using an environment override. For a proxy on the Docker host, bind the published port to loopback:

Build and run the Docker image:

docker build -t cp0x-mcp .
docker run -p 127.0.0.1:8000:8000 cp0x-mcp

Forward /mcp and /health to port 8000 and preserve the public Host header. The image binds to all interfaces and permits Host headers mcp.cp0x.com and mcp.cp0x.com:*. Local requests to the container must send an allowed Host header. Its health-check requests /health on loopback with Host: mcp.cp0x.com; this route also enforces the host allowlist and caller rate limit.

Publish

Keep server.json in the repository root. It declares com.cp0x/public-data, version 0.1.0, and the public Streamable HTTP endpoint; publishing this remote server does not require a package.

Before publishing to the MCP Registry, verify ownership of cp0x.com using a DNS TXT record at the domain apex or an HTTP proof at https://cp0x.com/.well-known/mcp-registry-auth. Authenticate with mcp-publisher using the corresponding domain verification method, then run from the repository root:

mcp-publisher validate
mcp-publisher publish

Glama reads the root glama.json for maintainer metadata when indexing the GitHub repository.

Disclosure

Deal links contain a cp0x referral code. The server only reads public data; it does not place trades or execute paid x402 requests. MIT license, see LICENSE.