Skip to main content
Glama
Sign In
Nauti-Labs

clearance-mcp

by Nauti-Labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to clearance-mcp

No user-submitted related servers found.

    Related Servers

    • imprest

      Theoddalex
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that provides programmable spend limits and audit trails for AI agents to make payments from a dedicated wallet, preventing overspend and unauthorized transactions.
      8
      MIT

    • approval-gate

      yulinlina
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that provides human-in-the-loop approval for risky AI agent actions, with durable state and audit logs.
      MIT

    • agent-guardrail

      rudimentall1
      A
      license
      A
      quality
      A
      maintenance
      MCP server for AI agent guardrails — validates and signs agent decisions (OAA tokens) so third parties can verify them without server access
      3
      26 PyPI
      1
      MIT

    • agent-security-gateway

      Un1u6ky
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that provides a security gateway for AI agents, enforcing allow/confirm/deny policies on tool calls and requiring human approval for risky operations, with full audit logging.
      -
    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/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool maps to a distinct clearance lifecycle action or auxiliary operation: list, create, get, approve, deny, revoke, verify token, create key, and get usage. Approve and deny are related decisions but are clearly separated by intent and outcome. There is no meaningful overlap between tools.

    Naming Consistency4/5

    Most tools follow a consistent resource_action pattern such as clearances_list, clearances_create, keys_create, and usage_get. The only notable deviation is verify_token, which uses verb_noun ordering. The convention is still highly predictable overall.

    Tool Count5/5

    Nine tools is a well-scoped set for a clearance approval workflow API. Each tool earns its place by covering a distinct operation rather than duplicating functionality.

    Completeness4/5

    The core clearance lifecycle is well covered: create, list, get, approve, deny, revoke, and token verification. API key management is only partially covered because keys can be created but not listed or revoked, and usage is limited to a single get operation. These are minor gaps rather than blockers for the primary clearance workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources