INDIVIDUAL MCP TOOL

get_source_detail

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.

quelvio.comnone authenticationAvailability not checked

Input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent endpoint

quelvio.com

CONNECT 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.quelvio-mcp]
url = "https://mcp.quelvio.com/http"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: quelvio-mcp
Remote MCP URL: https://mcp.quelvio.com/http

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": {
    "quelvio-mcp": {
      "url": "https://mcp.quelvio.com/http"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "quelvio-mcp",
  "transport": "streamable-http",
  "url": "https://mcp.quelvio.com/http"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

query_knowledge — 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.
list_domains — 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.