MCP.Market

Quelvio MCP server

online · 100% uptime
by quelvio.com·com.quelvio/mcp-server·v1.1.0

Your company's brain for AI agents. Cited, permission-aware knowledge across every system.

A88/100grade A
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Quelvio yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Quelvio tools (3)

write = sends, deletes, buys or posts
  • get_source_detailFree

    Return per-chunk source provenance for a previous query — document path, lifecycle state, embedding timestamp, contributor, last-updated — useful for verifying a citation or surfacing trust signals to a downstream system. Pass a `query_id` returned by an earlier `query_knowledge` call. Returns 404 if the query_id is unknown OR belongs to a different tenant (indistinguishable to prevent info-leak). Zero Knowledge Tokens consumed.

  • list_domainsFree

    List the taxonomy domains the company has indexed — with document counts, expert counts, and coverage levels — so an agent can decide whether to query before spending a Knowledge Token. Returns one row per domain with the canonical `taxonomy_domain` slug, document/chunk counts, expert count, coverage level (expert | partial | none), the single_expert risk flag, and the top contributor by authority. Use the slug as the `domain` filter on a follow-up `query_knowledge` call. Zero Knowledge Tokens consumed.

  • query_knowledgeFree

    Search the company's connected knowledge across every source — Drive, SharePoint, Confluence, Slack, Notion — with cited synthesized answers, lifecycle awareness, and refusal-on-weak-context. Returns a written answer with [n] citations plus the ranked source chunks. Modes: `fast` (1,500 kT — retrieval-only, no synthesis), `standard` (12,500 kT — default; synthesized answer over the top retrieval set), `deep` (25,000 kT — wider retrieval + premium synthesis for complex questions). Pick the cheapest tier that answers the question. Responses are capped at 25,000 output tokens per Claude Connectors policy; if truncated, structured metadata carries `truncated: true` and `query_id` so the agent can call `get_source_detail` for full provenance.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 231ms20/20
  • Tool poisoning3 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 89 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; website matches verified namespace9/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Quelvio compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 48,255 servers
Tools
3
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
39 ms
faster than 94% of 30,031 servers

What its tools let an agent do: 3 read

Install Quelvio in Claude Code, Cursor or VS Code

claude mcp add --transport http mcp-server https://mcp.quelvio.com/http
Add to Cursor

What the publisher says

From the Quelvio repository's README, as published. We do not edit it. Read it on GitHub

@quelvio/mcp-server

Quelvio MCP server — search your company's connected knowledge from any AI tool that speaks the Model Context Protocol.

Endpoint: https://mcp.quelvio.com/http (Streamable HTTP, MCP spec 2025-03-26) Source: Quelvio/quelvio-mcp-server License: MIT

Tools

Permission model

Every MCP query is scoped to your individual employee identity, not just your tenant. The server applies the same three-layer access model the dashboard uses:

  1. Tenant isolation — Qdrant collections are per-tenant; cross-tenant content is structurally unreachable.
  2. Role-based feature access — Owner / Admin / Member determines which tools are callable.
  3. Source permission filtering — permission_emails on every chunk, resolved at ingest time from the source system's ACLs (Google Drive shares, SharePoint groups, Confluence space restrictions). MCP queries see only what your individual account would see in those source systems.

The source-permission filter is unconditional — there is no flag, env var, or dashboard toggle that disables it. The MCP server records the per-employee identity on every query so cross-employee provenance inspection via getsourcedetail is rejected with 404 (only Owner/Admin can view another member's queries).

Sign in

There is no API key to provision. The first time you use Quelvio MCP from any client, you'll be redirected to your organization's sign-in page (Clerk-hosted, the same one the dashboard uses). After signing in, your client resumes automatically. Subsequent queries reuse the OAuth token until it expires (~30 days) or you revoke it from enterprise.quelvio.com.

If your AI assistant prompts you for a "Bearer token" or "API key" header in the JSON config, you have an outdated configuration — delete the headers block and let your client manage OAuth. The migration is automatic: the next time you invoke a tool, the client opens a browser tab for sign-in.

Install

Claude Desktop (and Claude Web)

Add to ~/Library/Application Support/Claude/claudedesktopconfig.json (macOS) or %APPDATA%\Claude\claudedesktopconfig.json (Windows):

{
  "mcpServers": {
    "quelvio": {
      "url": "https://mcp.quelvio.com/http"
    }
  }
}

Restart Claude Desktop. On first use Claude opens a browser tab pointing at Clerk's hosted sign-in page; complete sign-in and Claude resumes automatically.

Cursor

Add to .cursor/mcp.json in your project root (or globally at ~/.cursor/mcp.json):

{
  "mcpServers": {
    "quelvio": {
      "url": "https://mcp.quelvio.com/http"
    }
  }
}

Cursor handles the OAuth round-trip the same way Claude does.

Claude Code

claude mcp add quelvio --transport http https://mcp.quelvio.com/http

VS Code (Copilot)

Add to .vscode/mcp.json:

{
  "servers": {
    "quelvio": {
      "type": "http",
      "url": "https://mcp.quelvio.com/http"
    }
  }
}

stdio bridge (older clients)

For MCP clients that don't speak Streamable HTTP yet, install the npm package:

npm install -g @quelvio/mcp-server

Then point your client at the binary:

{
  "mcpServers": {
    "quelvio": {
      "command": "quelvio-mcp"
    }
  }
}

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Quelvio: common questions

Is Quelvio MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the Quelvio safety report
How do I install Quelvio?
It runs remotely at mcp.quelvio.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Quelvio need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Quelvio maintained?
The last commit was 126 days ago (2026-07-01). The latest release is v1.1.0.
Is Quelvio up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Quelvio?
Servers from other publishers that do the same job: color-space MCP server, llmwiki MCP server and CPU Performance Engineering MCP server.
How does Quelvio compare with other MCP servers?
safety score 88/100 (higher than 75% of 48,255 servers); tools 3 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Quelvio

Same job from other publishers: the closest match first, then the best rated.

  • color-space
    Conversions across 221 color spaces, tested against cited sources: CSS strings, gamut, LUTs
    A
  • llmwiki
    Compile documents into a cited knowledge wiki. Retrieve evidence, query, and review via local MCP.
    A
  • CPU Performance Engineering
    A CPU performance engineering brain: a vetted reading list, benchmarks and cited source passages
    A