Skip to main content
Glama
TrialRun MCP

TrialRun MCP

by kostadindev

Related Servers

Alternatives to TrialRun MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables businesses to route AI assistant access to files, databases, email and other MCP tools through a policy-enforcing gateway that filters what agents may call, strips secrets and personal data from results, and blocks prompt-injection content. Risky actions such as sending mail are held for human approval on a web page, and every request, decision and redaction is written to a tamper-evident audit log with Prometheus metrics.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to reach upstream MCP tool servers through a central policy gateway that authenticates each agent, enforces least-privilege and default-deny rules, and applies response obligations such as redaction, inference stripping, PII masking, and truncation. It also records every decision in a tamper-evident, hash-chained audit log that can be verified later.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      A fail-closed MCP gateway that sits between an AI agent and any real MCP server, enforcing a human-signed Ed25519 policy with tool allowlists, field checks, rate limits, rolling-sum human approval, secret redaction and a hash-chained audit log. It lets operators safely grant agents access to files, email and business systems while denying anything the signed policy does not explicitly allow, and ships with a prompt injection benchmark.
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Acts as an MCP gateway between AI agents and upstream tool servers, evaluating YAML policies on every tool call, injecting real credentials at the last mile, scanning requests and responses for secrets, PII, and prompt injection, and recording each action in a tamper-evident audit log. Also supports HTTP forward-proxy governance with rate limiting, cost tracking, and policy replay against historical audit data.
      4
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Governed MCP gateway that lets AI agents call tools with policy enforcement, prompt-injection screening, a kill-switch, and tamper-evident signed audit logs.
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides a governance gateway for LLM and agent traffic via MCP, blocking prompt injection, redacting PII, enforcing per-tenant token budgets, and caching repeat questions semantically. Enables AI agents to route model calls through the same guardrails instead of calling providers directly.
      MIT

    TDQS

    A3.8/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool has a fairly distinct purpose: policy viewing, file listing, file reading, text scanning, moment logging, reporting, and audit. The main overlap is get_report vs get_audit_log, which both surface restricted-data information, though the descriptions differentiate user-facing scoring from raw gateway events.

    Naming Consistency5/5

    All seven tools follow a consistent snake_case verb_noun pattern (get_access_policy, list_files, read_file, check_text, record_moment, get_report, get_audit_log). No camelCase mixing or vague bare verbs.

    Tool Count5/5

    Seven tools is well within the ideal 3-15 range and each maps to a distinct step of the stewardship workflow. Nothing feels padded or missing for the stated scope.

    Completeness4/5

    The read-and-monitor surface is coherent: policy, list, read, check, record, report, audit covers the assessment lifecycle. The only gaps are the absence of any file-search/write operation, which appears intentional for a read-only assessment sandbox.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues