Voris

ai.voris.mcpPublished by mcp.voris.aiv0.0.2Updated Oct 25, 2026

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

VerifiedSTDIODesktop onlyWeb Search & Scraping Data & Analytics

Server details

Identifier: ai.voris.mcp/server
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to mcp.voris.ai. It runs from a package rather than a hosted endpoint, so there is no endpoint to match against that domain.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/ai.voris.mcp%2Fserver.svg)](https://sourceweft.com/mcp/ai.voris.mcp%2Fserver?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Voris is a local stdio proxy that connects an MCP client to Voris's hosted privacy-native web analytics server for querying metrics and citations.

What you can do: Query web analytics metrics and citations for a site through the hosted Voris MCP server, with tools defined server-side rather than in the local package. Scaffold tracking setup for a site. Forward MCP requests from a local client such as Claude Desktop, an editor agent or a CLI to the hosted endpoint over Streamable HTTP. Scope each connection to a single site through the API key.
When to use it: Use it when you want an AI assistant to read Voris web analytics data or help set up tracking for one site, and you already have a Voris account and connection key.
Requirements: A local runtime able to launch the voris-mcp command as a subprocess, a Voris account, and the VORIS_API_KEY environment variable generated in the Voris dashboard under Settings > AI Connections. Network access to the hosted endpoint at mcp.voris.ai, which can be overridden with the --endpoint option. The README states this release is not published to npm, so the package must be obtained another way.

Before you install

The VORIS_API_KEY is a secret sent as a bearer token to the hosted Voris endpoint; keep it out of shared configuration. All authentication, scopes, rate limits and audit enforcement happen on the hosted server, and analytics data leaves your machine for that service. The README notes the npm package is not yet publicly distributed, so installation may not work as documented.

Installation

In SourceWeft

Open Voris in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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:

Example Claude Desktop configuration:

json

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

{  "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.

Source: README.md at commit 9432b58

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.0.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts