Skip to main content
Glama
Sign In
tibet-ipoll-mcp

tibet-ipoll-mcp

by Humotica
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to tibet-ipoll-mcp

No user-submitted related servers found.

    Related Servers

    • tibet-ainternet-mcp

      jaspertvdm
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for AInternet — DNS, identity and messaging for AI agents, enabling .aint domain resolution, Ed25519-based identity verification, and inter-agent messaging.
      MIT

    • aip-identity

      The-Nexus-Guard
      A
      license
      A
      quality
      D
      maintenance
      MCP server for AI agent identity — verify agents with Ed25519 signatures, check trust scores, sign and verify content, exchange encrypted messages. Built on the Agent Identity Protocol (AIP).
      8
      1
      MIT

    • backchannel

      unison-labs-ai
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for async messaging between AI coding agents, enabling cross-harness and cross-machine communication with Slack-like semantics and mail-shaped delivery.
      2
      MIT
    • hauddy

      hauddyofficial

      Hauddy
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to message each other by @nickname via an MCP server, with contacts, presence, and durable delivery across local and remote agents.
      3
      Apache 2.0

    • Dispatch

      asmiia
      A
      license
      Not graded
      quality
      B
      maintenance
      This MCP server enables AI agents and teams to coordinate through shared inboxes, threaded conversations, attachments, expiring file reservations, prompts, and live notifications, while replaying missed events after restarts.
      567 npm
      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.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing agents, pulling messages, resolving domains, sending messages, and checking system status. There is no overlap or ambiguity.

    Naming Consistency5/5

    All tools follow the pattern 'ipoll_verb' in lowercase snake_case, which is highly consistent and predictable.

    Tool Count4/5

    5 tools is reasonable for an agent messaging system, covering core operations. It could be slightly more comprehensive but is well-scoped.

    Completeness4/5

    The tool set covers essential CRUD-like operations for agent communication: listing, sending, pulling, and status checking. Missing an update/delete for messages or agent registration, but the domain is adequately served.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources