Skip to main content
Glama
xetenet

io.github.xetenet/xete-mcp

by xetenet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to io.github.xetenet/xete-mcp

No user-submitted related servers found.

    Related Servers

    • Shoot Email

      powersurge01
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that provides AI agents with a persistent, agent-native email mailbox for sending, receiving, and managing emails through bounded-context retrieval, idempotent operations, and explicit acknowledgement.
      MIT

    • agentbox

      sagnik11
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that gives AI agents programmable email inboxes with tools to create inboxes, send and list threaded email, and search messages.
      2 npm
      1
      MIT

    • mailmux

      Remedy92
      A
      license
      Not graded
      quality
      A
      maintenance
      A self-hosted MCP server that unifies multiple IMAP/SMTP mailboxes into one agentic inbox, enabling agents to list, search, read, and send email through MCP tools.
      MIT

    • pigeonpost

      bekirdag
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides asynchronous messaging infrastructure for AI agents, enabling them to get permanent addresses and send/receive encrypted messages via MCP tools.
      MIT
    • mailflat-mcp by MailFlat

      mailflat-mcpofficial

      MailFlat
      A
      license
      A
      quality
      A
      maintenance
      MCP server that gives an agent its own email inbox: it opens the inbox, waits for the one-time code a signup sends, and reads or sends mail. Addresses are permanent, so a test suite does not need a new one per run; only the messages expire, on a retention window you set.
      6
      12
      MIT

    • agent-comms-mcp

      redesignhealth
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for permissioned, structured agent-to-agent communications, enabling agents to coordinate and negotiate through scoped, typed messages with authentication and audit logging.
      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

    A4.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clear, non-overlapping purpose: identity retrieval, agent lookup, message sending, and inbox reading. No two tools could be confused.

    Naming Consistency5/5

    All tools follow a consistent pattern with the 'xete_' prefix and a verb_noun structure (my_identity, lookup_agent, send_message, check_inbox). No mixed conventions.

    Tool Count5/5

    Four tools precisely cover the core messaging workflow (identity, lookup, send, receive) without unnecessary additions. The scope is well-matched to the domain.

    Completeness5/5

    For a messaging server, the surface is complete: identity bootstrap, recipient verification, sending, and receiving. No critical operations are missing for the stated purpose.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources