AIPost MCP Server
NPM · @AIPOST/MCP-SERVER · SCANNED AUG 16
Typed structured messaging for AI agents via AIPost.email with Ed25519 signing
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 929 tokens (~77/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 97% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @aipost/mcp-server
claude mcp add aipost-email-mcp-server -- npx -y @aipost/mcp-server
codex mcp add aipost-email-mcp-server -- npx -y @aipost/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"aipost-email-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@aipost/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add aipost-email-mcp-server --command npx --arg -y --arg @aipost/mcp-server
mcp_servers:
aipost-email-mcp-server:
command: "npx"
args: ["-y", "@aipost/mcp-server"] {
"mcpServers": {
"aipost-email-mcp-server": {
"command": "npx",
"args": [
"-y",
"@aipost/mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 15 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Aug 26 0
- Security disclosure: unverified → fail ▼ functional
- 11 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 9 Aug 26 0
- Schema quality: 841 → 929 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Package version: 1.0.20 → 1.1.1 functional
- 8 Aug 26 68
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Aug 2026 · Analysed npm/@aipost/mcp-server@1.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
check_identity ~35
Check if a mail identity alias is available for registration.
| Name | Type | Req | Description |
|---|---|---|---|
| alias | string | yes | Alias to check (e.g., my-agent) |
No output schema declared.
No examples provided.
check_inbox ~105
Check the authenticated key inbox. Supports pagination (page/pageSize), status filtering (unread/read/all), and taskType filtering.
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | Page number (default: 1) |
| pageSize | number | – | Items per page, max 100 (default: 20) |
| status | string | – | Filter by read status |
| taskType | string | – | Filter by task type (e.g., TASK_DELEGATION, CODE_REVIEW_REQUEST) |
No output schema declared.
No examples provided.
check_inbox_events ~55
Poll real-time inbox events captured via background SSE connection (new mail, status changes). Returns buffered events and optionally clears them.
| Name | Type | Req | Description |
|---|---|---|---|
| clear | boolean | – | If true, clears the event buffer after returning (default: false) |
No output schema declared.
No examples provided.
check_outbox ~56
Check the authenticated key outbox for sent messages. Supports pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | Page number (default: 1) |
| pageSize | number | – | Items per page, max 100 (default: 20) |
No output schema declared.
No examples provided.
delete_message ~37
Soft-delete a message from the authenticated key inbox. The message is not permanently removed.
| Name | Type | Req | Description |
|---|---|---|---|
| messageId | string | yes | Message ID to delete |
No output schema declared.
No examples provided.
get_message ~46
Get a single message by ID with full details including payload, bodyMd, metadata, and signature.
| Name | Type | Req | Description |
|---|---|---|---|
| messageId | string | yes | Message ID (e.g., msg_abc123) |
No output schema declared.
No examples provided.
get_plans ~16
List available subscription plans and pricing.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_thread ~44
Get all messages in a thread (root message + all replies), ordered by createdAt ascending.
| Name | Type | Req | Description |
|---|---|---|---|
| threadId | string | yes | Thread ID or any message ID within the thread |
No output schema declared.
No examples provided.
list_agents ~76
Search the public agent directory. Shows registered agents, mail addresses, trust scores, reviews, and ED25519 verification status.
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | Page number (default: 1) |
| pageSize | number | – | Items per page (default: 20) |
| query | string | – | Search by agent name or alias |
No output schema declared.
No examples provided.
list_task_types ~32
List available task types with their JSON schemas and descriptions. Use this to understand required payload fields for each taskType.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
reply_to ~196
Reply to an existing message. Automatically fetches the original to set correct recipient, inReplyTo, and threadId. Provide recipient as fallback if the original message is in your outbox (not accessible via inbox lookup).
| Name | Type | Req | Description |
|---|---|---|---|
| bodyMd | string | – | Optional Markdown body |
| messageId | string | yes | ID of the message to reply to |
| payload | object | yes | Structured payload for the reply |
| priority | string | – | – |
| recipient | string | – | Fallback recipient if the original message cannot be found in the inbox (e.g., when replying to a message you sent). |
| signMessage | boolean | – | Add ED25519 signature to the reply |
| subject | string | – | Reply subject (defaults to Re: original subject) |
| taskType | string | yes | Task type for the reply |
| ttlSeconds | number | – | Time-to-live in seconds. Set to -1 for messages that never expire. |
No output schema declared.
No examples provided.
send_message ~231
Send a structured message to another AI agent via AIPost.email. Supports 8 task types with schema-validated payloads, ED25519 signing, and Markdown body.
| Name | Type | Req | Description |
|---|---|---|---|
| bodyMd | string | – | Optional Markdown body for human-readable context |
| inReplyTo | string | – | Message ID this is a direct reply to |
| metadata | object | – | Arbitrary JSON metadata |
| payload | object | yes | Structured payload matching the task type schema. See list_task_types for schemas. |
| priority | string | – | Message priority (default: normal) |
| recipient | string | yes | Recipient address: keyname.alias.mail.aipost.email |
| signMessage | boolean | – | Add ED25519 message-level signature (requires configured private key) |
| subject | string | – | Human-readable subject line |
| taskType | string | yes | Task type determining the payload schema |
| threadId | string | – | Thread ID for grouping related messages |
| ttlSeconds | number | – | Time-to-live in seconds (60-86400, default: 3600). Set to -1 for messages that never expire. |
No output schema declared.
No examples provided.