Skip to content
Qovia logo

Qovia MCP server

Which MCP servers are Qovia's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-28

← Back to Qovia

Whose server it is
  • Registry nameai.qovia/qoviaverified in the MCP registry

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

When we asked itchecked 2026-10-28
  • Stateanswerschecked 2026-10-28
  • Tools4
  • Server calls itselfqovia
  • Server version0.1.0
  • Protocol version2025-06-18

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 80 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 4 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.

Measured dailydaily checks: 4, the first on 2026-10-29
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
  • Answeredmeasuring4 of the 7 daily checks it takes to print a share
  • Median first answer98 ms
  • Space in an agent's context≈ 448 tokensthe definitions of all its tools (4), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 4 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • not sure · search posts across platforms filtered by date and sentiment
  • not sure · pull product reviews with ratings and seller replies
  • not sure · collect creator profiles and rates from creator platforms

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

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 →

Tools it offers4 tools · read 2026-10-28
  • search_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…

  • get_endpoint

    Show one endpoint: what it returns, its parameters (JSON Schema), example parameters, a response example and the price. Not charged, no API key needed.

  • call_endpoint

    Run an endpoint and return its data plus billing meta (charged_usd, balance_usd). Billed only when it returns data; empty results and failures are not charged. Needs the user's API key.

  • get_account

    Check the API key: balance, plan and rate limit. Not charged; counts toward the rate limit.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "qovia": {
      "type": "http",
      "url": "https://api.qovia.ai/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http qovia https://api.qovia.ai/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://api.qovia.ai/mcp as a custom connector in the settings.

OpenAPI spec

144 paths, read 2026-10-28. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.