@vorionsys/mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VORION_API_KEY | No | API key for the Cognigate Runtime. Required when VORION_API_URL is set. | |
| VORION_API_URL | No | URL of the Cognigate Runtime deployment for remote tools. If not set, remote tools return a 'not configured' error. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vorion_check_trustA | Look up an AI agent's current trust score and tier in the Vorion governance system. Returns the numeric score (0-1000), tier number (T0-T7), tier name, and observation tier. Use this to check how trusted an agent is before allowing it to perform sensitive actions. |
| vorion_record_signalA | Record a behavioral signal (positive or negative) for an AI agent. Positive signals (success, compliance pass) increase trust over time. Negative signals (failure, compliance fail) decrease trust — and higher-tier agents are penalized MORE severely per the BASIS penalty ratio P(T) = 3 + T. |
| vorion_gate_actionA | Check if an AI agent is allowed to perform a specific action based on its current trust tier. Returns whether the action is allowed, the agent's current tier, the required tier, and a reason. Use this as a pre-flight check before executing sensitive operations. |
| vorion_log_proofA | Log a governance decision to the Vorion proof chain — an immutable, hash-linked audit trail. Every ALLOW or DENY decision is recorded with the agent ID, action, and reasoning. Returns a proof hash and the current chain length for verification. |
| vorion_execute_governedA | Gate + execute + log in one atomic call. Checks if the agent has sufficient trust tier, executes the action if allowed, records the outcome as a behavioral signal, and logs a proof. Returns the full governance trail: gate decision, execution result, trust delta, and proof hash. This is the recommended way to run governed tool calls — replaces manual check-then-execute patterns. |
| vorion_tenant_whoamiA | Resolve the calling API key against the deployed Cognigate Runtime. Returns the tenant id, role, and capabilities the key is scoped to. Use this first if you need to confirm which tenant context the MCP session is running in. Requires VORION_API_URL + VORION_API_KEY env vars. |
| vorion_tenant_listA | List all tenants registered on the Cognigate Runtime. Admin-only. Returns id, name, tier, createdAt, and agent counts. Requires an admin-role API key in VORION_API_KEY. |
| vorion_tenant_audit_tailA | Tail the most recent audit events for a tenant (default: caller's own tenant). Each event carries hash-chained provenance: eventId, priorProofHash, proofHash. Use this to verify governance activity is being recorded correctly or to surface the live audit stream in a dashboard / glass window. |
| vorion_canary_submitA | Submit a canary probe result to the Cognigate Runtime. Canary probes are adversarial or behavioral test cases that measure whether an agent responded correctly. Results classified as pass / fail / ambiguous feed the tenant's behavioral baseline and can trigger AUDITED state on repeated ambiguous outcomes. Returns the stored proofHash for chain verification. |
| vorion_health_checkA | Hit the Cognigate Runtime health endpoint. Returns status, uptime, and dependency state (proof store, audit log, metrics). Use this as a pre-flight check before relying on remote governance operations, or to confirm the deployed API is reachable. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| trust-tiers | The BASIS 8-tier trust model (T0 Sandbox through T7 Autonomous). Shows score ranges, capabilities, penalty multipliers, and the penalty formula P(T) = 3 + T. |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/vorionsys/mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server