Skip to main content
Glama
API-Disk-Integrations

agent-mandate-mcp

by API-Disk-Integrations
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to agent-mandate-mcp

No user-submitted related servers found.

    Related Servers

    • ERDL Guard by OpenOBA

      ERDL Guardofficial

      OpenOBA
      A
      license
      Not graded
      quality
      A
      maintenance
      Enforces deterministic policy decisions on AI agent tool calls, supporting allow, deny, correct, escalate, and human review actions with verifiable audit receipts.
      48 npm
      MIT
    • Vaikora Guard MCP by Data443

      Vaikora Guard MCPofficial

      Data443
      A
      license
      Not graded
      quality
      D
      maintenance
      Enforces deterministic policies on AI agent tool calls, evaluating actions against compliance modules (SOC 2, HIPAA, GDPR, etc.) and returning ALLOW, BLOCK, or CONSTRAIN decisions with an audit trail.
      MIT

    • AgentShield

      shima78
      A
      license
      Not graded
      quality
      B
      maintenance
      Enforces configurable policies on AI agent tool calls, allowing, requesting review, or denying actions before they are executed.
      MIT

    • agenticrail-mcp

      MSMD-RUA
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides tools to evaluate an AI agent's step before execution, returning signed ALLOW/DENY receipts, and to verify receipt chain integrity.
      Apache 2.0

    • shield-kya

      The-Pixel-Boys
      A
      license
      Not graded
      quality
      A
      maintenance
      A local gate that lets agents submit risky tool actions for policy evaluation and receive ALLOW, DENY, or REQUIRE_APPROVE decisions before executing irreversible side effects. It can also open human approval holds and record an activity trail without executing the side effect itself.
      1,315 npm
      1
      MIT
    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 1 tool

    Disambiguation5/5

    Only one tool exists, so there is no possibility of confusing it with another tool in the server. Its scope is explicitly verification-only, which is clearly stated.

    Naming Consistency5/5

    verify_action is a clear verb_noun name that matches the tool's single responsibility. With only one tool, there is no naming inconsistency or mixed convention.

    Tool Count4/5

    One tool is thin by typical MCP standards, but the server explicitly scopes itself to verification-only functionality, so the count is reasonable. It is slightly under a typical multi-tool surface but not inappropriate.

    Completeness4/5

    Within its declared verification-only purpose, the tool has no obvious dead ends. However, the server assumes mandate envelopes are created externally, so there are no tools for managing or inspecting mandates, which is a notable but acceptable narrowing.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources