Skip to main content
Glama
mindos-dev

MCP Pill

by mindos-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to MCP Pill

No user-submitted related servers found.

    Related Servers

    • mcp-airlock

      Shalimov04
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables placing a governance proxy between AI agents and MCP servers to enforce policy, force dry-runs, require human confirmation for dangerous calls, and provide audit and tracing.
      47 PyPI
      25
      MIT

    • sagaz-mcp

      BabyKuramaDev
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables transparent MCP proxying with a hash-chained effect ledger, classifying agent actions by reversibility, enforcing approval gates, and dry-run previews of sessions.
      MIT

    • lazy-mcp-router

      naive000
      F
      license
      A
      quality
      D
      maintenance
      Safety-first local MCP tool gate with control plane, runtime security, and observability for managing MCP backends.
      4
      -

    • MCP Policy Gateway

      ahmed0qaid
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and MCP clients to safely access upstream MCP servers through centralized policy enforcement, including allow/deny/approval decisions, schema pinning, circuit breakers, and audit logging.
      MIT

    • wardline

      kabirnarang39
      A
      license
      Not graded
      quality
      A
      maintenance
      Control-plane proxy that sits in front of MCP servers, enforcing per-identity policy (YAML/OPA/Cedar), budget limits, and an audit trail on every call. Includes real-time anomaly detection that auto-blocks a compromised agent without a human in the loop.
      8
      Apache 2.0
    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.5/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct domain or action: health, catalog search/inspect, policy evaluation, message validation, audit tail/verify, and previews for budget/community. Even catalog.search and catalog.inspect differ clearly by breadth of results versus single-record inspection, leaving no realistic confusion between tools.

    Naming Consistency4/5

    Tool names almost uniformly follow a domain.action pattern (catalog.search, policy.evaluate, audit.verify, etc.), but gateway.health breaks the convention by using a noun instead of a verb. The pattern is still readable and predictable, with only one minor deviation.

    Tool Count5/5

    Nine tools is a well-scoped count for this governance/preflight server. Each tool covers a meaningful capability area without redundancy or bloat, and the set feels neither sparse nor overloaded.

    Completeness5/5

    The domain is pre-execution governance—health, catalog discovery, policy evaluation, message validation, audit, and previews—and the set covers all apparent phases of that process. There are no obvious dead ends or missing operations for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources