Skip to main content
Glama
verimand

dev.verimand/mcp-authority-server

by verimand
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to dev.verimand/mcp-authority-server

No user-submitted related servers found.

    Related Servers

    • vantic-mcp by vanticlabs

      vantic-mcpofficial

      vanticlabs
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP hosts to verify agent spending mandates and receipts, providing stateless tools for authorization, chain verification, credential verification, and DID resolution.
      Apache 2.0

    • gvnr

      instruxi-io
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to ask permission before an agent acts, returning allow, deny, or ask_human with receipts, and to monitor agent spend, limits, and recent decisions.
      1,087 npm
      Functional Source , Version 1.1, ALv2 Future

    • FLINT Agent Passport

      thefraudfather
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables verification of AI agent identity, authority, and integrity at transaction time, returning signed verdicts for allow, step-up, review, or block.
      MIT

    • AccordTrace

      Kosta1985
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to create and verify tamper-evident cryptographic evidence, manage key-bound Agent Passports, and support verifiable handoffs, approvals, and audit trails through MCP, REST, and A2A.
      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

    B3.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: resolve checks authorization, explain provides reasoning, get_authority retrieves current bounded authority, get_mandate retrieves mandate info, get_agent_dna retrieves agent state, and verify_permit validates a specific permit. There is minimal overlap; even resolve and verify_permit differ in that resolve is action-based while verify_permit is permit-based, and descriptions make this explicit.

    Naming Consistency5/5

    All tool names follow a consistent pattern: lowercase snake_case, starting with a verb (resolve, explain, get_*, verify_*). The get_* prefix is used for all read operations, and verify_* for validation. This consistency makes the tool set predictable and easy to navigate.

    Tool Count5/5

    With 6 tools, the server is well-scoped for a read-only authority and permit service. Each tool addresses a distinct aspect of authority/verification without redundancy, and the count is within the ideal range for focused MCP servers.

    Completeness4/5

    The tool surface covers the core operations for querying authority: resolve, explain, get_authority, get_mandate, get_agent_dna, and verify_permit. It is read-only by design, so no create/update/delete tools are expected. The only minor gap is a lack of a list-type tool to enumerate all authorities or mandates, but this is not critical for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources