Skip to main content
Glama
LBZ558

prophetkey-mcp

by LBZ558
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to prophetkey-mcp

No user-submitted related servers found.

    Related Servers

    • lockbox-mcp

      Waldo777-bh
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI coding agents to securely store and retrieve encrypted API keys via MCP tools.
      12 npm
      MIT

    • keyvault

      ylz201
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to securely manage API keys and secrets via the MCP protocol, with encrypted storage at rest and a simple CLI and Python SDK.
      1
      MIT

    • agentbridge

      yeszine
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to securely access locally stored API provider credentials, track usage and costs, and manage AI API vaults through MCP tools.
      1
      MIT

    • API Locker

      apilocker
      A
      license
      Not graded
      quality
      B
      maintenance
      Encrypted credential vault with a 21-tool MCP server. Store and manage LLM API keys, service API keys, and OAuth credentials — then let your AI agent list, reveal, rotate, rename, pause, and proxy calls through them.
      MIT

    • 1Password Agent MCP

      gambadio
      A
      license
      Not graded
      quality
      B
      maintenance
      Local MCP server that lets agents save copied secrets into 1Password and use approved fields through encrypted handles without plaintext secret tool arguments or responses. Includes a local permissions dashboard and optional service-account access for unattended work. Requires the 1Password CLI and runs on your computer.
      87 npm
      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/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing keys, retrieving key details, checking proxy status, running health checks, and making proxied requests. There is no meaningful overlap that would cause an agent to select the wrong tool.

    Naming Consistency5/5

    All tools follow a consistent `prophetkey_` prefix with snake_case verb_noun names. The pattern is uniform and predictable across the entire set.

    Tool Count5/5

    Five tools is a well-scoped size for this server's purpose. Each tool covers a distinct aspect of interacting with ProphetKey and its proxy without unnecessary bloat or redundancy.

    Completeness4/5

    The set covers the core workflows: discovering keys, inspecting key details, checking health, monitoring the proxy, and making authenticated requests. Lifecycle operations like adding or deleting keys are absent, but they appear intentionally handled outside the MCP server rather than being an obvious gap.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources