Skip to main content
Glama
Diegoescalonaro

local-kms-mcp-server

by Diegoescalonaro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to local-kms-mcp-server

No user-submitted related servers found.

    Related Servers

    • touchstone-mcp by Touchstone-CV

      touchstone-mcpofficial

      Touchstone-CV
      A
      license
      Not graded
      quality
      C
      maintenance
      Local MCP server that signs and records agent actions into a tamper-evident log using Ed25519 keys for frictionless integration with Touchstone.
      17 npm
      Apache 2.0

    • sigil-mcp

      cdrn
      A
      license
      Not graded
      quality
      A
      maintenance
      A local signing MCP server that lets Claude Code use private keys without ever exposing key material to the model's context window.
      31 npm
      3
      Apache 2.0

    • 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
      1
      MIT

    • aip-identity

      The-Nexus-Guard
      A
      license
      A
      quality
      D
      maintenance
      MCP server for AI agent identity — verify agents with Ed25519 signatures, check trust scores, sign and verify content, exchange encrypted messages. Built on the Agent Identity Protocol (AIP).
      8
      MIT

    • fallpharm-mcp

      sjgant80-hub
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides a sovereign, MIT-licensed MCP server for professional-service workflows, running entirely on your infrastructure with Ed25519 cryptographic signing for every action.
      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

    A3.7/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a distinct purpose: checking existence, deleting, generating, getting info, listing algorithms, listing keys, rotating, and signing. No overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case, such as generate_key, list_keys, rotate_key, etc. No deviations.

    Tool Count5/5

    8 tools is within the ideal range (3-15) for a KMS server, covering key lifecycle and signing without bloat or scarcity.

    Completeness4/5

    The tool set covers key generation, deletion, rotation, listing, info retrieval, and signing. Missing encrypt/decrypt or import/export, but core key management is well-covered for a signing-focused KMS.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources