Skip to main content
Glama
stcmain

whats-allowed-mcp

by stcmain
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to whats-allowed-mcp

No user-submitted related servers found.

    Related Servers

    • Aegis

      prince-rai88
      F
      license
      A
      quality
      B
      maintenance
      A blast-radius auditor for AI agents that computes combined effective permissions across all connected MCP tools, detects dangerous capability combinations deterministically, and provides a live risk graph and one-click policy fixes.
      4
      -

    • Laguarde

      FuturPanda
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to evaluate actions against team-defined policies, record decisions, and obtain human approvals for potentially risky operations.
      113 npm
      1
      -

    • inkog

      inkog-io
      A
      license
      A
      quality
      B
      maintenance
      Security co-pilot for AI agents. Scans for vulnerabilities like prompt injection, infinite loops, and token bombing in AI Agents, audits MCP servers, verifies AGENTS.md governance, and generates EU AI Act compliance reports.
      10
      28 npm
      3
      Apache 2.0

    • agent-sudo-mcp

      Kisyntra
      A
      license
      A
      quality
      A
      maintenance
      Local zero-trust permission gateway for AI agents. Enforces policy-based tool authorization, human approvals, scoped permissions, and cryptographically verifiable audit logs.
      4
      5
      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

    A4.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool addresses a distinct aspect of permission configuration: overall summary, file sources, behavioral anomalies, and unattended execution pathways. There is no functional overlap between the four tools; their purposes are clearly separated and easy to distinguish.

    Naming Consistency5/5

    All four tool names follow the same snake_case convention and are descriptive noun phrases that clearly reflect their output (e.g., permission_sources, rule_findings). The naming is consistent across the entire set, with no mixed conventions or ambiguous verbs.

    Tool Count5/5

    With only four tools, the server is tightly focused on its purpose of analyzing permission configuration. Each tool covers a necessary dimension of the domain, and the count is well within the ideal range for a specialized MCP server.

    Completeness5/5

    The tool set provides comprehensive coverage for inspecting and understanding permission configuration: a starting summary, source file inventory, anomaly detection, and unattended execution risk. For its diagnostic scope, there are no obvious missing operations or dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources