DataXAPI MCP Server

by dataxapi Your server? Claim it

not responding

DataXAPI is listed as active in the registry but did not answer our last check. It exposes 5 tools.

Market data for AI agents: Douyin, Xiaohongshu, TikTok, WeChat, X and 15 more. Pay per call.

Uptime history 5 days of history · worst day 17%

5 days agonow

28.6%

Uptime 24h

26 of 91 checks

Tools

read from the server

298 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 3

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 5 November 2026. No other catalogue keeps this.

7 Nov a tool changed the parameters it asks for call

6 Nov a tool changed the parameters it asks for call

5 Nov a tool changed the parameters it asks for call

DataXAPI does not always answer

Over the last week it answered 63.9% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://api.dataxapi.com/mcp

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://api.dataxapi.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://api.dataxapi.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://api.dataxapi.com/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

account

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.

call

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 many items, the charge, the balance, and how to get the next page (`cursor`: a new charged call) or the rest of a result cut to about 20 KB (`read_more`: free). Needs an API key.

describe

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.

find

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 key. When nothing matches on a named platform it lists everything that platform has: pick from it, or tell the user it is not there. Never use another platform's capability instead.

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.

Endpoints

URL	Transport	State	Latency	Checked
https://api.dataxapi.com/mcp	streamable-http	answering	46 ms	9 min ago

Alternatives to DataXAPI

same job, measured the same way

ToolSocket

by satashili

660+ data tools for agents: TikTok, Douyin, Instagram, YouTube, X, weather, GitHub. Pay per call.

88 installs/wk answering

santyvv-data — market & on-chain data

by santyvv

Market and on-chain crypto data for AI agents. Pay per call in USDC on Base (x402).

50 installs/wk 8 tools answering

TikTok data for agents

by fetcher-tiktok

13 TikTok endpoints. Pay per call in USDC via x402.

15 tools answering

X402 Gateway

by gentechlabs

Pay-per-call x402 services for agents: risk scoring, DeFi, wallet and market data.

10 tools answering

Vextorium

by vextorium-api

200+ pay-per-call APIs for AI agents via x402: on-chain data, DeFi, markets and compliance.

4 tools answering

47620 Solana Data API

by 47620

x402 pay-per-call Solana data + crypto market + JWT/unit utils for AI agents.

79 installs/wk 52 tools answering

47620 Base + Polygon Data API

by 47620

Pay-per-call Base and Polygon onchain data over x402 for AI agents.

38 installs/wk 18 tools answering

Agent Newsstand

by agentnewsstand

Market data and web intelligence for AI agents, paid per call in USDC on Base via x402.

16 tools answering

DataXAPI — questions

Answers built from our own checks of this server.

What can DataXAPI do?

It exposes 5 tools, read directly from the server on our last check. Among them: account, call, describe, find, read_more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is DataXAPI working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 26 of 91 checks got a reply (28.6%), average response time 298 ms. The bar chart above shows every period we have measured.

The registry lists DataXAPI as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect DataXAPI?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does DataXAPI need an API key?

No. DataXAPI completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is DataXAPI?

It answers our handshake in 298 ms on average, which is faster than 46% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.