Skip to main content
Glama
Quidli

Quidli Connect MCP

Official
by Quidli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Quidli Connect MCP

No user-submitted related servers found.

    Related Servers

    • Callsign by callsign-im

      Callsignofficial

      callsign-im
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to discover each other by @handle, exchange consent-based message requests, and record auditable, tamper-evident ledger entries through MCP.
      7
      Apache 2.0
    • @agentgram/mcp-server by agentgram

      @agentgram/mcp-serverofficial

      agentgram
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to interact with AgentGram, the social network for AI agents, through native MCP tools for posting, commenting, voting, and managing identity.
      22
      11 npm
      1
      MIT

    • Lens Protocol MCP Server

      daoleno
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI tools to interact with the Lens Protocol decentralized social network ecosystem. Supports fetching profiles, posts, followers, searching content, and accessing social graph data through standardized MCP interfaces.
      4
      -

    • AGENZA MCP Server

      mbtest870-ctrl
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables verifiable AI agent identity and reputation management on ICP via MCP, allowing agents to register, create handshake proofs, and verify credentials.
      -

    • Agentry MCP Server

      cthulhutoo
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides a trust layer for AI agents with identity, reputation, payments, and discovery via 92 API endpoints as MCP tools, leveraging Nostr-native infrastructure.
      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

    B3.4/5.0

    Scored across 14 tools

    Disambiguation3/5

    Several clusters overlap: connect_scores_batch covers both linked accounts and usernames, making connect_scores_by_username and connect_scores_by_account largely redundant; connect_lookup and connect_lookup_exposed both return wallet/profile data; and connect_trust_graph and connect_trust_check both query depth-1 trust. Descriptions clarify inputs and outputs, but an agent could still misselect within these clusters.

    Naming Consistency4/5

    All tools use a consistent connect_ prefix and snake_case, with mostly predictable domain/action names such as connect_trust_create and connect_drop_balance. Minor deviations like connect_me and connect_lookup_exposed are readable but slightly less formulaic than the rest.

    Tool Count4/5

    14 tools fit the multi-feature scope of identity lookup, scores, trust, and drops without becoming overwhelming. A few score and trust query variants could be consolidated, but the count is reasonable for the surface area.

    Completeness4/5

    Core workflows are covered: lookup/profile, scores, trust graph and attestations, chain metadata, balances, and drops. Minor gaps exist around managing linked accounts or checking delayed drop status, but agents can work around them via retries and existing lookups.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources