# Dataxapi MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.dataxapi%2Fmcp
Registry id: `mcp-registry/com.dataxapi/mcp`
Status: live (checked 2026-11-22T17:13:25.137Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 4073
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "dataxapi-mcp-server": {
      "type": "http",
      "url": "https://api.dataxapi.com/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http dataxapi-mcp-server https://api.dataxapi.com/mcp
```

## Tools (5)

- `account`: balance: balance, key budget and spending. receipt: what one call was charged. usage: calls and charges by day or capability. status: which capabilities are up 
- `call`: One page from one capability, charged per call, per item or per minute; errors are free. Give only the parameters `describe` lists for it. The result's first li
- `describe`: The contract of 1 to 5 capabilities: each parameter with its meaning and values, fields per view, paging, price and the most a call can cost, examples. Free, no
- `find`: Find the capability for a need in plain words, English or Chinese: up to 5, each with its required parameters, price and a ready call. Free, no key. Given a pos
- `read_more`: The rest of a result `call` cut, or it in another view. Free, nothing is fetched again; kept 24 hours. Needs the key that made the call.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
