Skip to main content
Glama
trustos-trustfolio

Trust OS MCP Server

Official
by trustos-trustfolio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Trust OS MCP Server

No user-submitted related servers found.

    Related Servers

    • oprow-continuum

      sanyamChaudhary27
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that acts as a temporal verification firewall, checking structured assumptions or diffs against immutable version receipts to return allow/block/abstain with cited evidence.
      MIT

    • titmas-agent-action-gate

      joy7758
      A
      license
      B
      quality
      B
      maintenance
      An MCP server that enforces deterministic authorization boundaries for AgentTeams workflows by verifying evidence and policy, returning ALLOW, BLOCK, or REQUIRE_APPROVAL decisions before actions are executed.
      6
      Apache 2.0

    • agent-guardrail

      rudimentall1
      A
      license
      A
      quality
      A
      maintenance
      MCP server for AI agent guardrails — validates and signs agent decisions (OAA tokens) so third parties can verify them without server access
      3
      1
      MIT

    • WhitePact

      Guruprasath-Annadurai
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that exposes governance, trust-scoring, compliance, guardrail, cost, drift, and supply-chain scanning tools and resources to any MCP client over stdio, Streamable HTTP, or legacy HTTP+SSE. It lets agents route every tool call through a deterministic five-way decision (allow, redact, require approval, deny, or quarantine) with hash-chained evidence, human approval workflows, and in-agent trust gates for LangChain, LangGraph, and Google ADK.
      30
      44 PyPI
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    Resources