Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
X-Arobi-Tenant-KeyNoYour Arobi tenant key. Sent as the `X-Arobi-Tenant-Key` header when connecting to the optional managed cloud endpoint (https://aura-genesis.org/api/v1/mcp). The local stdio/Docker server runs fully offline and requires no arguments.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Arobi Immaculate MCP server. Seal authority with arobi_route_grant, evaluate actions with arobi_authorize, choose policy-justified models with arobi_classify_and_route, and verify hash-chained records with arobi_verify_chain.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
arobi_route_grantB

Seal WHO granted WHAT authority to WHICH workflow, with scope, category caps, attenuation, and expiry. Returns a locally Ed25519-signed route_grant and hash-chained ROUTE_GRANT record.

arobi_authorizeA

Decide whether an agent action is permitted against a sealed route grant, and seal a hash-chained AUTHORIZATION record. Returns GRANTED, DENIED, or ESCALATED with checks and reason code.

arobi_classify_and_routeA

Classify a prompt and choose the cheapest route capable of the work from your candidate set, reporting whether any cost above the cheapest capable route is justified by required_capabilities or an explicit quality_exception policy. Set record=false to preview without appending to the local chain.

arobi_verify_chainA

Recompute a set of sealed records locally and report whether the SHA-256 hash chain and Ed25519 signatures are intact, pinpointing the first broken record index and reason if tampered.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 4 tools

Disambiguation4/5

Each tool maps to a distinct step in the sealed-authorization lifecycle: grant creation, chain verification, action authorization, and prompt classification/routing. The only soft overlap is the word 'route' appearing in both arobi_route_grant and arobi_classify_and_route, but the descriptions clearly separate authority sealing from model/route selection.

Naming Consistency4/5

All names use a consistent arobi_ prefix and snake_case, and three of four are verb-led (verify_chain, authorize, classify_and_route). arobi_route_grant is noun-first and less parallel, but the family pattern remains readable and predictable.

Tool Count3/5

Four tools is thin for a system managing grants, authorizations, audit chains, and routing; each tool is heavyweight but there are no query/list or revocation companions. It sits at the borderline of under-scoped rather than clearly right-sized.

Completeness3/5

Creation and verification are covered (grant, authorize, verify_chain, classify_and_route), but there is no revocation or expiration-management tool, no way to list/inspect issued grants, and no key rotation or chain export. Agents can work around this only by treating the chain as append-only with no lifecycle control.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues