DataXAPI MCP server

• Registry namecom.dataxapi/mcpverified in the MCP registry

The registry name sits under dataxapi.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-11-03
• Tools5
• Server calls itselfdataxapi
• Server version1.0.0
• Protocol version2025-06-18

On 2026-11-03 the server answered initialize and tools/list without a sign-in. First answer in 285 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 1 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
• Answeredmeasuring1 of the 7 daily checks it takes to print a share
• Median first answer106 ms
• Space in an agent's context≈ 2,975 tokensthe definitions of all its tools (5), which an agent carries on every turn
• Tool definitionsA · 90 of 100
• Typed results0 of 5 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 3 of 5

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• find

  Find which capability returns the data you need, when its ID is not obvious from the `call` list. Say the need in plain words, English or Chinese. Returns up to 5, each with its required parameters, price and a ready-made call. Free, no…

• describe

  The whole contract of 1 to 5 capabilities: parameters, fields returned in each view, paging, price and the most one call can cost, what it cannot give, example calls. Free, no key. Use it before `call` when unsure of the parameters.

• call

  Fetch one page of data from one capability. Charged per call or per item, as `describe` says; an error costs nothing. IDs read platform.resource.action; give only the parameters that capability takes. The first line of the result says how…

• read_more

  Read the rest of a result that `call` cut to fit, or the same result in another view. Free: nothing is fetched again; results are kept 24 hours. Needs the API key that made the call.

• account

  balance: the balance, this key's budget and spending. receipt: what one call was charged, by its result ID. usage: calls and charges by day or capability. status: which capabilities are up (no key). Free.