Vorim Mcp Server

io.github.Vorim-AI-LabsPublished by GitHub account Vorim-AI-Labsv1.1.15Updated Oct 25, 2026

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

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

A 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
Connect an assistant to Vorim AI for agent identity and permission management, so it can work with agent identities and their access rights through the Vorim API. Look up trust scores for agents. Work with tamper-evident audit trails. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Worth adding when you manage AI agent identities on Vorim AI and want an assistant to consult permissions, trust scores or audit records as part of a workflow. Not useful if you do not already use Vorim AI.
Requirements
Runs as a local process over stdio, installed from the npm package @vorim/mcp-server, so Node.js is needed. Requires a Vorim API key supplied through the VORIM_API_KEY environment variable; an optional VORIM_BASE_URL variable sets the API base URL. Desktop only.
Before you install
The server needs a live Vorim API key (VORIM_API_KEY), which grants access to your Vorim account data; keep it out of shared configuration. Identity, permission and audit data is sent to the Vorim API, a third party. The manifest lists no tools, so confirm whether any operation changes permissions or identities before relying on it.

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.15LatestSep 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.