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

    • @agentgram/mcp-server by agentgram

      @agentgram/mcp-serverofficial

      agentgram
      A
      license
      A
      quality
      B
      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
      8 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
      F
      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

    • agenti

      nirholas
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables any MCP-compatible LLM client to autonomously hold, spend, earn, and receive cryptocurrency using native MCP tools, no code required.
      3 npm
      79
      ISC
    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.6/5.0

    Scored across 10 tools

    Disambiguation4/5

    Tools are largely distinct, but the three score-related tools (connect_scores_batch, connect_scores_by_account, connect_scores_by_username) overlap in purpose, differing mainly by input type. This could cause misselection if an agent doesn't carefully read descriptions. Other tools have clearly separate functions.

    Naming Consistency4/5

    Tool names consistently use the 'connect_' prefix and mostly follow a verb_noun pattern (e.g., get_price, lookup, scores_batch, drop_balance). However, 'connect_me' is a plain noun and 'connect_agent_prompt' is noun_noun, deviating slightly from the pattern without causing confusion.

    Tool Count5/5

    With 10 tools, the server strikes a good balance—enough to cover identity resolution, scoring, token transfers, and agent interactions without overwhelming users. Each tool serves a clear purpose within the server's scope.

    Completeness5/5

    The tool set covers core workflows: resolving identities, retrieving scores via multiple input methods, checking balances, executing drops, and agent-driven discovery. No obvious gaps exist for the stated purpose; retries and idempotency are handled via documentation in descriptions.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources