Skip to content
Qanvo logo

Qanvo MCP server

Which MCP servers are Qanvo'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-29

← Back to Qanvo

Whose server it is
  • Registry nameapp.qanvo/screenerverified in the MCP registry

The registry name sits under qanvo.app. 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-29
  • Staterequires sign-inchecked 2026-10-29

On 2026-10-29 the server answered and asked for a sign-in with a Qanvo account (OAuth). It shows its tool list only to signed-in users, so we list none here.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: Screen stocks by describing criteria in plain English; Get emailed when stocks enter or leave a screen.
  • Checked on 5 of the 7 days it takes to judge reliability.

Once connected

  • For "Screen stocks by describing criteria in plain English", the likely first call is market_query.
  • delete_alert, update_alert, create_alert change data without a sign-in: anyone with the address can call them.
  • Parameters are untyped or undescribed in 10 of 19 tools: check arguments before calling.

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: 5, the first on 2026-10-29
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
  • What an agent can do with it2 of 2 use cases
  • Answeredmeasuring5 of the 7 daily checks it takes to print a share
  • Median first answer164 ms
  • Space in an agent's context≈ 2,451 tokensthe definitions of all its tools (19), which an agent carries on every turn
  • Tool definitionsA · 91 of 100
  • Typed results0 of 19 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 10 of 19

What an agent can do with it

  • can do · Screen stocks by describing criteria in plain English
  • not sure · Build dashboards that refresh daily with new data
  • can do · Get emailed when stocks enter or leave a screen

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

  • Tools that change data, on a server that answers without a sign-in: delete_alert, update_alert, create_alert

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 →

How to connect

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

{
  "mcpServers": {
    "screener": {
      "type": "http",
      "url": "https://qanvo.app/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http qanvo https://qanvo.app/mcp

Add to CursorAdd to VS Code

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

The first time it connects, the client opens a Qanvo sign-in.

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.