# Qovia (remote · api.qovia.ai)

Public data from 20+ platforms, including Douyin, Xiaohongshu, Weibo and TikTok, as structured JSON

- Trust score: 85/100 (high trust)
- Change this week: +18
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.qovia.ai`: 85/100 (this document), [markdown](https://verifymcp.io/servers/ai-qovia-qovia/api.md), [page](https://verifymcp.io/servers/ai-qovia-qovia/api)

## Channel facts

- Endpoint: `https://api.qovia.ai/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.1.1`

## 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-05.

- **Endpoint Security**: 92/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 429 tokens (~107/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

Qovia is a hosted endpoint at https://api.qovia.ai/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 ai-qovia-qovia 'https://api.qovia.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-qovia-qovia": {
      "url": "https://api.qovia.ai/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.ai-qovia-qovia]
url = "https://api.qovia.ai/mcp"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  ai-qovia-qovia:
    url: "https://api.qovia.ai/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "ai-qovia-qovia": {
      "type": "http",
      "url": "https://api.qovia.ai/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-05 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

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

- [security] First check of Authorization: pass

### 2026-11-03 (score 83, +7)

- [security improvement] Authorization: partial → pass
- [cosmetic] Tool “call_endpoint” changed its title: Call Qovia Endpoint
- [cosmetic] Tool “get_account” changed its title: Get Qovia Account
- [cosmetic] Tool “get_endpoint” changed its title: Get Endpoint Details
- [cosmetic] Tool “search_endpoints” changed its title: Search Qovia Endpoints

### 2026-11-02 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 75, +7)

- [security improvement] Authorization: unverified → partial
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “call_endpoint” rewrote its description, which is the text the model reads
- [security] Tool “get_account” rewrote its description, which is the text the model reads
- [security] Tool “get_endpoint” rewrote its description, which is the text the model reads
- [security] Tool “search_endpoints” rewrote its description, which is the text the model reads

### 2026-10-30 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 67, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “call_endpoint” rewrote its description, which is the text the model reads

### 2026-10-26 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (4)

### `search_endpoints` (~136 tokens)

Search Qovia Endpoints

Search Qovia's data endpoints by keyword (Chinese or English) and/or platform slug (douyin, tiktok, xiaohongshu, pgy, bilibili, tieba, wechat, taobao, jd, fliggy, xingtu, huahuo, cljx, ...). Returns ids, titles, price per call and whether each endpoint is live. Free; no sign-in required.

Input parameters:

- `include_unavailable` (boolean): Also list endpoints that are not live yet
- `platform` (string): Platform slug
- `query` (string): Words in the id, path or title

### `get_endpoint` (~55 tokens)

Get Endpoint Details

Show one endpoint: what it returns, its parameters (JSON Schema), example parameters, a response example and the price. Free; no sign-in required.

Input parameters:

- `endpoint_id` (string, required): e.g. raw.douyin.video

### `call_endpoint` (~83 tokens)

Call Qovia Endpoint

Run an endpoint and return its data plus billing info (charged_usd and remaining credit). Requires a Qovia account connected to this MCP server; billed only when data is returned, so empty results and failures are free.

Input parameters:

- `endpoint_id` (string, required): e.g. raw.douyin.video
- `params` (object): The endpoint's parameters (see get_endpoint)

### `get_account` (~30 tokens)

Get Qovia Account

Show the connected Qovia account's credit, plan and rate limit. Free; counts toward the rate limit.

## Diagnostics

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

## Score history

- 2026-11-05: 85
- 2026-11-04: 84
- 2026-11-03: 83
- 2026-11-02: 76
- 2026-11-01: 75
- 2026-10-31: 75
- 2026-10-30: 68
- 2026-10-29: 67
- 2026-10-28: 67
- 2026-10-27: 66
- 2026-10-26: 66
- 2026-10-25: 65
- 2026-10-24: 65
- 2026-10-23: 64
- 2026-10-22: 64

## Common questions

### What is the Qovia MCP server?

Qovia is an MCP server listed in the public MCP registry as ai.qovia/qovia. Public data from 20+ platforms, including Douyin, Xiaohongshu, Weibo and TikTok, as structured JSON. This page covers its hosted endpoint (https://api.qovia.ai/mcp).

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

Qovia scores 85 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 Qovia MCP server expose?

Qovia exposes 4 tools: search_endpoints, get_endpoint, call_endpoint, get_account. Their descriptions and schemas cost roughly 304 tokens of context every time the server is loaded.

### Does the Qovia MCP server require authentication?

Yes. Qovia asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Qovia MCP server still maintained?

Qovia is still listed as active in the MCP registry. We last reached this channel on 5 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.qovia.ai/mcp
- Authorisation metadata: https://api.qovia.ai/.well-known/oauth-protected-resource/mcp
- Website: https://qovia.ai/docs/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/ai-qovia-qovia/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-qovia-qovia/api.json
- HTML version of this page: https://verifymcp.io/servers/ai-qovia-qovia/api