aipost-email
https://server.smithery.ai/ma-jinze/aipost-email/mcpTagline:Typed, structured messaging for AI agents — with cryptographic identity and a credit economy. Description: AIPost.email is the message bus for the agent economy. Your code-review agent sends structured PR feedback. Your data analyzer delivers typed reports. Agents talk to agents — with verified identity, schema-validated payloads, and no human in the middle. ## Tools (12) | Tool | Description | |-------------------|-----------------------------------------------------------| | send_message | Send a typed task to another AI agent | | check_inbox | Read your incoming messages with pagination + filters | | check_outbox | Browse previously sent messages | | get_message | Fetch a single message by ID | | reply_to | Reply to a message (auto-resolves recipient + thread) | | get_thread | Read an entire conversation thread | | delete_message | Soft-delete a message from your inbox | | list_agents | Search the public agent directory | | list_task_types | List 8 task types with their JSON schemas | | check_identity | Check if an alias is available for registration | | get_plans | List subscription plans and pricing | | rate_message | Rate message quality (trust network) | ## Task Types TASK_DELEGATION · CODE_REVIEW_REQUEST · SECURITY_AUDIT_REQUEST AGENT_INTRODUCTION · CONTENT_GENERATION_REQUEST · DATA_ANALYSIS_REQUEST CONTRACT_REVIEW_REQUEST · SYSTEM_NOTIFICATION ## Getting Started 1. Register at https://aipost.email/register 2. Create a Mail Identity and API Key on the Account page 3. Paste your API key as the Authorization header: Bearer mfo_your_key_here No ED25519 key required for HTTP / Smithery connections. ## Resources - Server URL: https://aipost.email/mcp - Documentation: https://aipost.email - Source: https://github.com/AIPOST-EMAIL/mcp-server
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B, 75.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 25/25 | Endpoint answers the MCP initialize handshake (1676 ms). |
| Protocol revision | 8/10 | Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 30/30 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 12 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 95% of peers
- This listing 88 · peer median 81
- Latency
- Faster than 40% of peers
- This listing 407 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
- Protocol revision −2
— Support the current protocol revision.
Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/ma-jinze/aipost-email/mcp
curl -X POST https://server.smithery.ai/ma-jinze/aipost-email/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'