Back to Browse

Voris MCP Server

Developer ToolsModerate6.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

Voris privacy-native web analytics for AI agents: query metrics & citations, scaffold tracking.

About

Voris privacy-native web analytics for AI agents: query metrics & citations, scaffold tracking.

Security Report

6.2
Moderate6.2Moderate Risk

A well-designed stdio-to-HTTPS proxy for the Voris MCP server with proper authentication, clean architecture, and appropriate permission scoping. The server correctly delegates all enforcement (auth, scopes, rate limits, audit) to the hosted endpoint and avoids tool logic or database access. Minor code quality observations around error handling do not materially impact security. Supply chain analysis found 2 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.

7 files analyzed · 7 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

process_spawn

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

Your Voris MCP API key. Generate one in the Voris dashboard under Settings > AI Connections.Required

Environment variable: VORIS_API_KEY

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "ai-voris-mcp-server": {
      "env": {
        "VORIS_API_KEY": "your-voris-api-key-here"
      },
      "args": [
        "-y",
        "@voris-ai/mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

@voris-ai/mcp

voris-mcp — a thin stdio ⇄ HTTPS proxy that connects a local MCP client (Claude Desktop, an editor agent, a CLI) to the hosted Voris MCP server at https://mcp.voris.ai/mcp.

It forwards JSON-RPC messages verbatim between the client's stdio channel and the hosted endpoint over Streamable HTTP. It contains no tool logic and no database access — all enforcement (authentication, scopes, rate limits, audit) lives in the hosted server. One connection is scoped to exactly one site, by your key.

Usage

Your MCP client launches voris-mcp as a subprocess and speaks MCP over its stdin/stdout. Provide your key via the environment:

VORIS_API_KEY=vor_mcp_… voris-mcp

Example Claude Desktop configuration:

{
  "mcpServers": {
    "voris": {
      "command": "voris-mcp",
      "env": { "VORIS_API_KEY": "vor_mcp_…" }
    }
  }
}

Options

  • VORIS_API_KEY (required) — your Voris MCP connection key, generated in Settings → AI Connections. It is sent as Authorization: Bearer … to the hosted endpoint. If it is unset, voris-mcp writes a message to stderr and exits with code 1.
  • --endpoint <url> — override the hosted endpoint (default https://mcp.voris.ai/mcp). Mainly for local development; also accepts --endpoint=<url>.

All diagnostics are written to stderr; stdout carries only the MCP protocol stream, so it stays clean for the client.

Status

This release does not publish voris-mcp to npm. The package is built and tarball-tested here; public npm distribution ships in the next phase (A042). Until then, generate your key and copy the hosted-connection snippet from the Voris dashboard.

Reviews

No reviews yet

Be the first to review this server!