# DataXAPI (remote · api.dataxapi.com)

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

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `api.dataxapi.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-dataxapi-mcp/api.md), [page](https://verifymcp.io/servers/com-dataxapi-mcp/api)

## Channel facts

- Endpoint: `https://api.dataxapi.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 52/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1453 tokens (~290/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 93% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the DataXAPI MCP server?

DataXAPI is a hosted endpoint at https://api.dataxapi.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-dataxapi-mcp": {
      "type": "remote",
      "url": "https://api.dataxapi.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-dataxapi-mcp --url 'https://api.dataxapi.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-dataxapi-mcp:
    url: "https://api.dataxapi.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-dataxapi-mcp": {
      "Transport": "http",
      "Url": "https://api.dataxapi.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-dataxapi-mcp -t streamable-http -u 'https://api.dataxapi.com/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 71, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-03 (score 70)

First indexed and scored.

## MCP tools (5)

### `find` (~153 tokens)

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.

Input parameters:

- `category` (string)
- `platform` (string): Only this platform, by ID or name; alone, lists all it has
- `query` (string): e.g. "comments on a douyin video", "小红书笔记详情"

### `describe` (~71 tokens)

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.

Input parameters:

- `ids` (array, required): Capability IDs

### `call` (~509 tokens)

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.

Input parameters:

- `board` (string): Which board
- `brand` (string): Name of the brand asked about
- `capability` (string, required)
- `cursor` (string): Cursor returned by the previous page
- `export_id` (string): A video's encrypted ID as a search result gives it, starting with export/; it expires
- `fields` (array): Return only these fields
- `id` (string): ID of the first resource in the path
- `idempotency_key` (string): Optional: left out, the server makes a new one. To be able to repeat a call whose answer you did not get, give a new unique value (a UUID) and send the same value again: that returns the first result…
- `ids` (array): Several IDs in one request
- `include` (array): Extra parts to return alongside
- `keyword` (string): The keyword asked about
- `keywords` (array): Several terms in one request
- `lang` (string): Language code
- `limit` (integer): Items per page
- `max_price` (string): Refuse if the call could cost more US dollars than this: "0.01"
- `post_id` (string): ID of the post it belongs to
- `published_within` (string): Published within the last period
- `query` (string): Search terms
- `region` (string): Country or region code
- `since` (string): Published at or after
- `sort` (string): Sort order
- `tab` (string): Tab as shown on the platform
- `type` (string): Content format
- `until` (string): Published at or before
- `url` (string): Link to the object, instead of its ID
- `username` (string): Account handle, instead of its ID
- `view` (string): How much of each item to return; compact when left out
- `window` (string): Statistics period

### `read_more` (~118 tokens)

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.

Input parameters:

- `fields` (array): Return only these fields
- `offset` (integer): Where to go on, as printed; from the start when left out
- `result_id` (string, required): As `call` printed it
- `view` (string): How much of each item to return; compact when left out

### `account` (~139 tokens)

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.

Input parameters:

- `group_by` (string): usage: day, capability, key_id, entry, source, end_user; commas between several
- `request_id` (string): receipt: the result ID
- `since` (string): usage: from this time, ISO 8601; 30 days back when left out
- `until` (string): usage: up to this time
- `what` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-dataxapi-mcp/api#diagnostics

## Score history

- 2026-11-04: 71
- 2026-11-03: 70

## Common questions

### What is the DataXAPI MCP server?

DataXAPI is an MCP server listed in the public MCP registry as com.dataxapi/mcp. Market data for AI agents: Douyin, Xiaohongshu, TikTok, WeChat, X and 15 more. Pay per call. This page covers its hosted endpoint (https://api.dataxapi.com/mcp).

### Is the DataXAPI MCP server safe to use?

DataXAPI scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the DataXAPI MCP server expose?

DataXAPI exposes 5 tools: find, describe, call, read_more, account. Their descriptions and schemas cost roughly 990 tokens of context every time the server is loaded.

### Does the DataXAPI MCP server require authentication?

No. We connected to DataXAPI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the DataXAPI MCP server still maintained?

DataXAPI is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.dataxapi.com/mcp
- Website: https://dataxapi.com/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/com-dataxapi-mcp/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-dataxapi-mcp/api.json
- HTML version of this page: https://verifymcp.io/servers/com-dataxapi-mcp/api