Skip to main content
Glama
trustos-trustfolio

Trust OS MCP Server

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TRUSTOS_API_KEYYesYour Trust OS API key
TRUSTOS_BASE_URLNoOverride API base URL (default: Trust OS gateway)

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
verify_decisionB

Verify a high-impact decision before execution using Trust OS.

create_decisionA

Create and verify a decision via the Trust OS Decision API. Returns decision_id, recommendation, risk assessment, proof_hash, and a trace_url for Dashboard inspection.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 2 tools

Disambiguation4/5

The two tools have distinct primary purposes—create_decision creates a new decision while verify_decision checks an existing one—but create_decision also includes verification, creating slight overlap. Descriptions are clear enough to guide correct selection in most cases.

Naming Consistency5/5

Both tools follow the consistent verb_noun pattern: create_decision and verify_decision. The naming is uniform, predictable, and easy to extend.

Tool Count3/5

With only two tools, the server feels thin for its domain, though the narrow scope may justify it. This is borderline and could benefit from additional tools to round out the functionality.

Completeness2/5

The server covers creation and verification but lacks essential operations like retrieving, listing, or updating decisions. This is a significant gap because agents cannot reference or manage existing decisions beyond their initial creation, making the surface incomplete for typical workflows.

Maintenance

ActivitySlowing
ResponsivenessNo issues