Skip to main content
Glama
calebe

Bardo

by calebe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Bardo

No user-submitted related servers found.

    Related Servers

    • Soul

      choihyunsus
      A
      license
      Not graded
      quality
      C
      maintenance
      Gives AI agents persistent memory, handoffs, and shared context across sessions, enabling seamless continuity and multi-agent collaboration.
      65 npm
      68
      -

    • Wallet4Agent MCP Server

      TalaoDAO
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI agents with a DID-based identity, secure wallet, and cloud KMS-backed signing keys, enabling trusted interactions with persons, companies, and other agents via standards like OIDC4VCI, OIDC4VP, and SD-JWT.
      Apache 2.0

    • Smara MCP Server

      nnaveenraju
      A
      license
      Not graded
      quality
      C
      maintenance
      A vendor-neutral, user-sovereign memory layer for AI agents and tools, providing persistent, cross-tool memory that users fully own and control.
      4 npm
      Apache 2.0
    • AgentValet by AgentValet

      AgentValetofficial

      AgentValet
      A
      license
      A
      quality
      B
      maintenance
      Identity and credential governance for AI agents. Every agent gets its own cryptographic identity, scoped short-lived credentials per platform, human approval on sensitive actions, and an immutable audit log.
      7
      2
      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 41 tools

    Disambiguation5/5

    Each tool has a distinct, well-defined purpose. Account deletion, notes, links, sessions, policies, attestations, and cryptographic operations are clearly separated with no overlapping functionality.

    Naming Consistency4/5

    The vast majority follow the verb_noun pattern (e.g., note_add, session_revoke_current). A few exceptions like 'dashboard' and 'stepup' break the pattern but are still understandable.

    Tool Count4/5

    41 tools is high but justified by the server's broad scope (identity, notes, encryption, attestations, policy, etc.). Each tool serves a specific function, though some might be combinable.

    Completeness5/5

    The tool surface covers account lifecycle, note CRUD with versioning, linking, document attestations, encryption, signing, session management, policy control, and more. No obvious gaps for the intended functionality.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources