Vorim Mcp Server

io.github.KzinoPublished by GitHub account Kzinov1.1.2Updated Oct 26, 2026

AI agent identity, permissions, trust scores, and tamper-evident audit trails via Vorim AI

VerifiedSTDIODesktop onlySecurity & MonitoringAI & ML

Overview

AI-generated overview

Local MCP server that connects an assistant to Vorim AI for agent identity, permissions, trust scores and tamper-evident audit trails.

What you can do
  • No tool list is published, so capabilities are inferred from the description.
  • Manage AI agent identities and their permissions through the Vorim AI API.
  • Look up trust scores for agents.
  • Work with tamper-evident audit trails.
  • Calls go to a Vorim API endpoint, which can be overridden with VORIM_BASE_URL.
When to use it
Worth adding when you need an assistant to work with AI agent identity, permission and trust data, or to consult tamper-evident audit records held in Vorim AI.
Requirements
Runs as a local stdio process, installed from the npm package @vorim/mcp-server (Node.js runtime). Requires a Vorim API key supplied in the VORIM_API_KEY environment variable, and network access to the Vorim API; the base URL can be set with VORIM_BASE_URL. Desktop client only.
Before you install
The server needs a live Vorim API key (VORIM_API_KEY, prefixed agid_sk_live_), which grants access to your Vorim account and should be kept out of logs and shared configs. Identity, permission and audit data are sent to the Vorim API at the configured base URL, so point VORIM_BASE_URL only at a trusted endpoint. No tool list is published, so review what it can read or change before use.

Installation

In SourceWeft

  1. Open Vorim Mcp Server in the dashboard and add it to a workspace.
  2. 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

This repository has no README.

Tools

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

Version history

1
  1. v1.1.2LatestSep 16, 2026

Score

25% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.