Vorim MCP Server

MCP server for Vorim AI — AI agent identity, permissions, and audit trails. The vorim mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 6 defined tools rather than through you.

What it actually does

Vorim AI is the identity and trust layer for autonomous AI agents. It gives each agent its own Ed25519 keypair, time-bounded scoped permissions, hash-linked audit events, and a publicly verifiable trust score — so when an agent does something, you can prove who acted, what they were allowed to do, and what happened.

• Cryptographic identity — — Ed25519 keypairs for every agent. Not a shared service account
• Fine-grained permissions — — 7 scopes with time bounds and rate limits, sub-5ms checks
• Tamper-evident audit trails — — SHA-256 hash-linked events, signed export bundles for compliance
• Public trust scoring — — anyone can verify any agent without auth (no shared secrets)
• Open protocol — — VAIP submitted to IETF, MIT-licensed, freely implementable
• Compliance-ready — — EU AI Act, US Executive Order 14110, SOC 2, GDPR

Its toolset

Everything the assistant can do here goes through one of these:

• Cursor — The Cursor tool exposed by this server
• Health — The Health tool exposed by this server
• Permissions — The Permissions tool exposed by this server
• Audit — The Audit tool exposed by this server
• Trust — The Trust tool exposed by this server
• Onboarding — The Onboarding tool exposed by this server

Configuration

You will need 2 environment variables: VORIM_API_KEY, VORIM_BASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Vorim's toolset — Cursor, Health, Permissions and 3 more — is a fair guide to whether it matches your workflow. It is maintained by kzino; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Vorim's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the vorim mcp server does with a few real requests.