AIPost.email MCP Server
OfficialRelated Servers
Alternatives to AIPost.email MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables 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.64 npmMIT
- AlicenseAqualityCmaintenanceEnables LLM agents to send, receive, and discover contacts on the agentic message bus via native tools.5MIT
- AlicenseNot gradedqualityCmaintenanceEnables async, authenticated messaging between AI agents with explicit authorization and persistent inbox.3 npmMIT
- AlicenseNot gradedqualityAmaintenanceProvides asynchronous messaging infrastructure for AI agents, enabling them to get permanent addresses and send/receive encrypted messages via MCP tools.MIT
- AlicenseAqualityNot gradedmaintenanceEnables AI agents to interact with the XMTP decentralized messaging network. Supports sending encrypted messages, managing conversations, and streaming real-time messages to any XMTP-enabled wallet address.62 npm3-
- AlicenseAqualityCmaintenanceEnables AI tools to discover, communicate with, and orchestrate AI agents over a decentralized peer-to-peer network with end-to-end encryption.6Apache 2.0
TDQS
Scored across 12 tools
Each tool targets a distinct action or resource, with clear separation between listing, fetching, sending, replying, and event polling. The only minor ambiguity is between check_inbox and check_inbox_events, but their descriptions clarify the difference.
Tool names mostly follow a clear verb_noun pattern like send_message, get_thread, and list_agents. reply_to is a slight inconsistency since it lacks a noun object, but the overall naming style remains predictable.
Twelve tools is well-scoped for an AI messaging server, covering sending, receiving, threading, replying, agent discovery, and account-related queries without excessive redundancy. Each tool earns its place in the API surface.
The tool set covers the core messaging lifecycle: send, reply, list inbox/outbox, fetch individual messages, thread traversal, deletion, and event polling. Minor gaps exist, such as no explicit mark-as-read or permanent delete, but agents can work around these with the provided status filters and soft-delete behavior.