Skip to main content
Glama
ShellFrameAI

AgentSecure Community

Official

Related Servers

Alternatives to AgentSecure Community

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that lets AI agents call APIs without ever seeing the credentials, using a local encrypted vault and per-secret allowlist policies for HTTP requests and subprocess environment variables.
      1
      AGPL 3.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      A local-first MCP server that lets AI agents use gated APIs without holding keys, enforcing declarative policies, injecting secrets server-side, and auditing access without content.
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Secrets management MCP server that injects credentials into API requests for AI agents, enforcing policies and logging all activity without exposing raw keys.
      31 npm
      30
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      A local stdio MCP server that enables coding agents to discover credential handles and create scoped action requests with local approval and sanitized output.
      7
      47 npm
      15
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that lets coding agents and child processes run against format-preserving phantom tokens in process.env, while real secrets are injected only inside a local edge proxy when the outbound host matches an allowlist. It also exposes blocked exfiltration attempts for auditing.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A local-first LLM routing MCP server that keeps sensitive data on your own models, with fail-closed privacy and manager-worker delegation, exposing route and complete tools to any MCP client.
      39 PyPI
      MIT

    TDQS

    A4.5/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct action+resource: inbox counts vs. message records vs. acknowledgement are split across check_messages/list_messages/read_message, and policy inspection is split cleanly into policy.describe (HTTP/secret config), secret.status (single env), and get_policy_hint (Mesh actions). Descriptions actively cross-reference the correct sibling tool for each adjacent use case, leaving little room for misselection.

    Naming Consistency3/5

    All names share the agentsecure. namespace, but the suffix conventions are mixed: dotted resource.action forms (policy.describe, secret.status, http.request) coexist with verb_noun forms (send_message, list_messages, request_approval), and agentsecure.identity has no verb at all. Still readable, but not a predictable single pattern.

    Tool Count5/5

    13 tools is well within a comfortable range and each maps to a distinct facet of the mesh (messaging, approvals, identity, policy, secrets/HTTP, audit). No filler or redundant tools are apparent.

    Completeness4/5

    Messaging (send/list/read/reply/count), approvals (create/read), identity (lookup/register), policy inspection, secret-aware HTTP, and audit retrieval are all covered. Minor gaps remain: no way to cancel or withdraw a pending approval, no message deletion/archival, and no bulk listing of approvals, but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessWithin a week