com.quelvio/mcp-server
REMOTE · MCP.QUELVIO.COM · SCANNED SEP 20
Your company's brain for AI agents. Cited, permission-aware knowledge across every system.
Available components
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. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 595 tokens (~198/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the com.quelvio/mcp-server server?
com.quelvio/mcp-server is a hosted endpoint at https://mcp.quelvio.com/http, 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.
remote · mcp.quelvio.com
claude mcp add --transport http com-quelvio-mcp-server 'https://mcp.quelvio.com/http'
{
"mcpServers": {
"com-quelvio-mcp-server": {
"url": "https://mcp.quelvio.com/http"
}
}
} {
"servers": {
"com-quelvio-mcp-server": {
"type": "http",
"url": "https://mcp.quelvio.com/http"
}
}
} [mcp_servers.com-quelvio-mcp-server] url = "https://mcp.quelvio.com/http"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-quelvio-mcp-server": {
"type": "remote",
"url": "https://mcp.quelvio.com/http",
"enabled": true
}
}
} openclaw mcp add com-quelvio-mcp-server --url 'https://mcp.quelvio.com/http' --transport streamable-http
mcp_servers:
com-quelvio-mcp-server:
url: "https://mcp.quelvio.com/http" {
"McpServers": {
"com-quelvio-mcp-server": {
"Transport": "http",
"Url": "https://mcp.quelvio.com/http"
}
}
} assistant mcp add com-quelvio-mcp-server -t streamable-http -u 'https://mcp.quelvio.com/http'
{
"mcpServers": {
"com-quelvio-mcp-server": {
"type": "http",
"url": "https://mcp.quelvio.com/http"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.quelvio.com/http
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=quelvio.com | CN=WE1,O=Google Trust Services,C=US | 6 Aug 2026 | 4 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 86f131826e048766130d79696d3dbd28 |
| SANs: quelvio.com, mcp.quelvio.com, *.mcp.quelvio.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.quelvio.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| quelvio.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="quelvio-mcp", error="missing_token", error_description="Authorization header required.", resource_metadata="https://mcp.quelvio.com/.well-known/oauth-protected-resource"
Bearer realm="quelvio-mcp", error="missing_token", error_description="Authorization header required.", resource_metadata="https://mcp.quelvio.com/.well-known/oauth-protected-resource"Protected resource metadata
| Document | https://mcp.quelvio.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.quelvio.com |
| Authorisation server | https://mcp.quelvio.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.quelvio.com/http | Verified | 200 | |
| http (plaintext) | http://mcp.quelvio.com/http | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_source_detail ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query_id | string | yes | UUID returned in the structured-metadata block of a prior `query_knowledge` response. Tenant-scoped — cross-tenant 404. |
No output schema declared.
No examples provided.
list_domains ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| coverage_filter | string | – | Optional comma-separated subset of expert,partial,none. Default: all three. Unknown tokens 400. |
No output schema declared.
No examples provided.
query_knowledge ~322
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Optional taxonomy domain filter (e.g. 'engineering.platform'). Use `list_domains` to discover valid values for the tenant. |
| max_sources | number | – | Number of source chunks to return (1–20, default 5). The 25K token cap may force fewer results regardless of this value. |
| mode | string | – | fast | standard | deep. Defaults to `standard`. `fast` returns chunks only (no synthesized answer); `standard` and `deep` return a synthesized answer with [n] citations + the source chunks. |
| query | string | yes | Natural-language query (1–2000 characters). Be specific — results are ranked by authority + relevance, not keyword overlap. |
No output schema declared.
No examples provided.
What is the com.quelvio/mcp-server server?
com.quelvio/mcp-server is listed in the public MCP registry as com.quelvio/mcp-server. Your company's brain for AI agents. Cited, permission-aware knowledge across every system. This page covers its hosted endpoint (https://mcp.quelvio.com/http).
Is the com.quelvio/mcp-server server safe to use?
com.quelvio/mcp-server scores 84 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 com.quelvio/mcp-server server expose?
com.quelvio/mcp-server exposes 3 tools: query_knowledge, list_domains, get_source_detail. Their descriptions and schemas cost roughly 595 tokens of context every time the server is loaded.
Does the com.quelvio/mcp-server server require authentication?
Yes. com.quelvio/mcp-server 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 com.quelvio/mcp-server server still maintained?
com.quelvio/mcp-server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.