Data Collection
qovia.ai
Searches, inspects, and calls Qovia data endpoints across Chinese social and e-commerce platforms, returning unified records with billing metadata.
ENDPOINT 1
https://api.qovia.ai/mcp
MCP server metadata
- Name
- qovia
- Version
- 0.1.0
Qovia returns public web data (Douyin, Xiaohongshu, Bilibili, Tieba, Taobao, Fliggy and more) as unified JSON records. Find an endpoint with search_endpoints, read its parameters with get_endpoint, then run it with call_endpoint. Only successful, non-empty results are billed (the price is listed per endpoint); empty results and failures are not charged. Every call needs the user's Qovia API key (Authorization: Bearer sk-qovia-…) on this MCP connection.
Known tools 4
search_endpointsSearch 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, .
Inferred read-onlyget_endpointShow one endpoint: what it returns, its parameters (JSON Schema), example parameters, a response example and the price.
Inferred read-onlycall_endpointRun an endpoint and return its data (unified records) plus billing meta (charged_usd, balance_usd).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.qovia]
url = "https://api.qovia.ai/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"qovia": {
"type": "http",
"url": "https://api.qovia.ai/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: qovia
Remote MCP URL: https://api.qovia.ai/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"qovia": {
"url": "https://api.qovia.ai/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"qovia": {
"type": "http",
"url": "https://api.qovia.ai/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "qovia",
"transport": "streamable-http",
"url": "https://api.qovia.ai/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.