Skip to main content
Glama

Related Servers

Alternatives to tremelay-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to invoke upstream APIs without ever holding reusable credentials, using short-lived scoped capabilities and server-side secret injection. Also provides execution controls and x402 facilitator routing for secure agent actions.
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to securely manage local credentials, obtain short-lived tokens for authenticated API access, and audit every use by purpose.
      9
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Capability-token gate for AI agents. Mint time-boxed, scope-limited grants that authorize specific tool calls.
      3,242 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to make authenticated API calls and run commands with secrets injected, while keeping credentials completely hidden from the model, with policy enforcement, grants, and audit logging.
      6
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to look up stored logins by URL, name, or alias and use them without seeing the secrets, injecting authentication into HTTP requests, running commands with credentials in the environment and scrubbed output, and fetching 2FA codes, subject to per-credential policies and user approval.
      23
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to access registered resources based on a fixed subject identity, enforcing default-deny policies and auditing for controlled context sharing.
      Apache 2.0

    TDQS

    B3.4/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools split cleanly along list/describe/invoke lines, and each targets a distinct operation on a capability handle. describe_capability and list_capabilities are adjacent in purpose but their singular-vs-collection scope keeps them separable.

    Naming Consistency4/5

    All three follow a consistent verb_noun snake_case pattern (list_capabilities, describe_capability, invoke_capability). The only blemish is the singular/plural mismatch between 'capability' and 'capabilities', a minor cosmetic deviation.

    Tool Count4/5

    Three tools is a lean but coherent minimal triad for a credential-use broker: enumerate, inspect, execute. Nothing feels redundant, though the surface is on the thin side given invoke_capability absorbs several distinct invocation modes (http_request, http_broker, attestation, SSH).

    Completeness3/5

    Discovery and invocation are covered, but the domain implies lifecycle operations that are absent. The warning about 'ambiguous or cancelled invocation' suggests cancellation/status exists conceptually yet no tool exposes it, leaving a notable gap.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive