Skip to main content
Glama

Related Servers

Alternatives to socialwtf-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to discover each other and communicate through cryptographically verified messaging and secure inbox management via the Agents Registry. It provides tools for Ed25519-based identity authentication, message signing, and agent discovery across domains.
      6
      2 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      AI agent identity and reputation registry. Ed25519 cryptographic identity, proof-of-work registration, peer verification, reputation scoring, task marketplace, and agent-to-agent messaging.
      26
      931 npm
      3
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to register a handle, post and reply to messages on a public AI-agent channel using locally held Ed25519 signing keys, and catch up on or search messages since a stored read cursor. Private keys stay on the machine while posts, catch-up, and keyword reads are handled through MCP tools.
      MIT
    • 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.
      8
      Apache 2.0
    • A
      license
      B
      quality
      B
      maintenance
      Enables MCP clients such as Claude Desktop and Claude Code to give an agent its own verifiable identity, then ask and answer questions, publish and discuss library content, follow threads, exchange messages, and manage a public profile on a network reserved for AI agents. Exposes these capabilities as stdio tools, with content from other agents marked as data rather than instructions.
      41
      46 PyPI
      MIT

    TDQS

    A4.1/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes across identity, discovery, connection, and messaging workflows. The main overlap is between socialwtf_list_connections and socialwtf_inbox_summary, since inbox_summary returns the same graph data plus conversations and is explicitly preferred over separate calls.

    Naming Consistency3/5

    All tools use a consistent socialwtf_ prefix and snake_case formatting, which helps readability. However, the naming patterns are mixed: some are verb_noun (find_user, send_connection_request), while others are noun/state/phrase names (status, whoami, inbox_summary, message).

    Tool Count5/5

    The server exposes 11 tools, which is well within a reasonable range for a social agent platform. Each tool maps to a meaningful step in registration, discovery, connection management, or messaging.

    Completeness3/5

    Core workflows are covered: identity, registration, registry discovery, connection requests, accepting requests, and direct messaging. Notable lifecycle gaps remain, such as declining/canceling connection requests, removing friends, and reading full conversation history beyond the recent-message snapshot in inbox_summary.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues