Skip to main content
Glama
sandbox-quantum

switch-trust-mcp

by sandbox-quantum
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to switch-trust-mcp

No user-submitted related servers found.

    Related Servers

    • Context MCP

      geq1fan
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI agents with secure, read-only file system access to analyze and understand project codebases, enabling multi-repository context aggregation and cross-project code tracing.
      36 PyPI
      5
      MIT

    • Rudow MCP Server

      prenzio
      A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to query application projects directly for logs, metrics, incidents, and semantic search through read-only tools.
      17
      MIT

    • QuestLLens

      DMDuFresne
      A
      license
      Not graded
      quality
      B
      maintenance
      Gives AI agents read-only access to any QuestDB instance, enabling schema discovery, time-series querying, and monitoring of partitions, WAL state, symbols, and ingestion health through MCP.
      Apache 2.0

    • depot-mcp

      PostHog
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only inspection of Depot CI failures, job logs, GitHub Actions jobs on Depot runners, and container builds through the Depot API, so agents can diagnose issues without installing the Depot CLI.
      76 npm
      MIT

    • devguard-mcp

      Saiydur
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to perform read-only scans of local projects, Git history, GitHub Actions workflows, machines, and GitHub accounts for supply-chain malware indicators, and to access cleanup and recovery guidance.
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 37 tools

    Disambiguation4/5

    Tools are mostly well-separated by resource and action (list vs get vs summary). The clearest overlap is get_guardrail_interaction_counts vs get_guardrail_outcomes, which the description admits share the same underlying data, and get_remediation_guidance overlaps with the remediation embedded in get_issue. These are minor and the descriptions largely disambiguate.

    Naming Consistency4/5

    Overwhelmingly consistent verb_noun pattern (list_*/get_*) with predictable suffixes like _detail, _summary, _runs, _results. A few deviations: find_issues_for_file breaks the list_ convention, and get_context/get_model are vaguer than their peers. Overall readable and consistent.

    Tool Count3/5

    37 tools is heavy, but the server spans many genuinely distinct domains (guardrails, AI-SPM issues, model/agent/tool/MCP inventory, LLM interactions, ROI, evaluations, red-team endpoints), each with roughly 3-6 tools. It is justified but sits well above the comfortable 3-15 band and risks context bloat.

    Completeness4/5

    The surface is broad and largely complete for a read/analytics security platform: list+get coverage for guardrails, issues, inventory, interactions, sessions, ROI, and evaluations, plus aggregation/summary endpoints. Gaps are minor (no per-result detail endpoint for evaluation results, acknowledged trimming) and agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources