Skip to main content
Glama
Cubiczan

trust-ledger-os

by Cubiczan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to trust-ledger-os

No user-submitted related servers found.

    Related Servers

    • agentforge-trust-mcp

      KOVY
      A
      license
      A
      quality
      D
      maintenance
      MCP server exposing AgentForge Trust Score audit tools. Query trust, evaluate policies, list trusted servers, recommend with filter.
      4
      11 npm
      1
      MIT

    • Ratchet

      suhui-organization
      A
      license
      Not graded
      quality
      A
      maintenance
      Read-only CLI and stdio MCP server that inventories the MCP servers an agent can reach, compiles a least-privilege policy with a reason for every allow/approve/deny verdict, and emits a delivery the recipient re-verifies in their own browser using a sha256 manifest.
      Apache 2.0

    • mcp-sentinel

      IronNathanAlvares
      A
      license
      Not graded
      quality
      B
      maintenance
      A continuous, out-of-band trust and reliability layer for the MCP ecosystem. It fingerprints MCP server tool definitions, detects and classifies drift (e.g., rug pulls) via a severity taxonomy, maintains a hash-chained evidence ledger, and gates CI with SARIF—while also acting as an MCP server itself so agents can check a server's safety before binding.
      Apache 2.0

    • dsh-audit-bundle

      dongsheng123132
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for auditing DeepSeek Harness evidence. Enables inspection and verification of content-addressed audit manifests with fail-closed validation.
      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.8/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool targets a distinct resource such as manifest, phases, routes, or packages, and get_phase is clearly the single-item counterpart to list_phases. There is only mild overlap potential in get_manifest possibly summarizing other surfaces, but descriptions keep the boundaries clear.

    Naming Consistency5/5

    All tool names follow a consistent get_/list_ + noun pattern with snake_case throughout. This makes the tool set predictable and easy to navigate.

    Tool Count5/5

    Five tools is a well-scoped size for a focused read-only informational server. Each tool covers a distinct surface without unnecessary duplication or bloat.

    Completeness4/5

    The core surfaces of the server—manifest, roadmap phases, routes, and packages—are covered with list and detail access where appropriate. Missing route- or package-level detail getters could be a minor gap, but list-level access may be sufficient for the apparent purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources