Skip to main content
Glama

Related Servers

Alternatives to AgentDevX

  • A
    license
    Not graded
    quality
    C
    maintenance
    Self-hosted credential store and API proxy for AI agents. One Bearer token, all your services. Handles OAuth refresh, encrypted storage, audit logging, and per-agent permissioning.
    56 npm
    MIT

Related Servers

  • A
    license
    Not graded
    quality
    D
    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
  • A
    license
    Not graded
    quality
    A
    maintenance
    Provides a zero-knowledge credential vault for AI agents, allowing secure storage, retrieval, and management of secrets with cross-agent delegation and tamper-evident audit.
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    Zero-knowledge credential injection for AI agents. Your agent authenticates to websites and APIs without ever seeing a password, TOTP code, or API key.
    3 npm
    1
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    Credential isolation proxy for AI agents. Injects API keys at the network boundary so your agent never sees the raw credential. Supports domain allowlists, agent auth, policy enforcement, and audit logging.
    3
    59 npm
    14
    Apache 2.0
  • A
    license
    Not graded
    quality
    B
    maintenance
    Bounded egress gateway & secret proxy for AI agents and applications, enabling safe credential injection into upstream requests while keeping raw secrets out of LLM prompt contexts.
    15 npm
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Agent Vault is a local credential vault for AI agents. It enables agents to use secrets by name without ever seeing their values, with host allowlists, output scrubbing, and audit logging.
    4
    MIT

TDQS

C2.9/5.0

Scored across 38 tools

Disambiguation4/5

The namespace prefixes and resource-specific names make most tools easy to distinguish, and different API namespaces are separated. A couple of tools could still be confused, notably petstore-api.getInventory vs petstore-api.findPetsByStatus and webscrape.scrape vs webscrape.extractDesign.

Naming Consistency3/5

Most tools follow a namespace.verbResource camelCase pattern, but there are notable deviations such as acme-mailer.send_email, memory.stre, and echo-server.add. The overall style remains readable, but the mixing of snake_case, camelCase, and verb-only names prevents a strong consistency score.

Tool Count2/5

With 38 tools across ten unrelated API namespaces, the server is oversized and unfocused. The PetStore block alone carries 19 tools, and many of these clusters would be better split into separate purpose-specific servers.

Completeness2/5

Several included API surfaces are only partially covered: JSONPlaceholder has create/get but no update/delete, GitHub is read-only, exchange-rate only exposes latest rates, and memory has store/recall but no delete or list. These gaps make the set feel incomplete for an agent relying on those services.

Maintenance

ActivitySlowing
ResponsivenessNo issues