agent-mailbox — Mailbox and Wake System for AI Agent Teams
PYPI · AGENT-MAILBOX · SCANNED OCT 4
Mailbox + wake system for AI agent teams: letters always land, right agent wakes, quiet otherwise.
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 → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to polaris-smart/agent-mailbox). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1943 tokens (~138/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "mailbox_send" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the agent-mailbox — Mailbox and Wake System for AI Agent Teams MCP server?
agent-mailbox — Mailbox and Wake System for AI Agent Teams runs locally as a PyPI package, launched with uvx agent-mailbox. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · agent-mailbox
claude mcp add polaris-smart-agent-mailbox -- uvx agent-mailbox
{
"mcpServers": {
"polaris-smart-agent-mailbox": {
"command": "uvx",
"args": [
"agent-mailbox"
]
}
}
} {
"servers": {
"polaris-smart-agent-mailbox": {
"command": "uvx",
"args": [
"agent-mailbox"
]
}
}
} codex mcp add polaris-smart-agent-mailbox -- uvx agent-mailbox
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"polaris-smart-agent-mailbox": {
"type": "local",
"command": [
"uvx",
"agent-mailbox"
],
"enabled": true
}
}
} openclaw mcp add polaris-smart-agent-mailbox --command uvx --arg agent-mailbox
mcp_servers:
polaris-smart-agent-mailbox:
command: "uvx"
args: ["agent-mailbox"] {
"McpServers": {
"polaris-smart-agent-mailbox": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"agent-mailbox"
]
}
}
} assistant mcp add polaris-smart-agent-mailbox -t stdio -c uvx -a agent-mailbox
{
"mcpServers": {
"polaris-smart-agent-mailbox": {
"command": "uvx",
"args": [
"agent-mailbox"
]
}
}
} 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.
- 3 Oct 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.
- 1 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- Schema quality: 112 → 138 ▼ functional
- Stability: unverified → 0.07 ▲ functional
- Package version: 0.7.5 → 0.7.6 functional
- 29 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Sept 26 61
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 4 Oct 2026 · Analysed pypi/agent-mailbox@0.7.6
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | polaris-smart/agent-mailbox |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/polaris-smart/agent-mailbox/.github/workflows/publish.yml@refs/tags/v0.7.6 |
| Rekor log index | 3014202355 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:eeea096f7e5ad95961269487758b724f9011ebfeb665303e3a1abba5ed38137c |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
mailbox_broadcast ~76
Broadcast to every registered agent (including boss). dedupe=True (default) suppresses semantically identical re-broadcasts per recipient within the dedup window — see mailbox_send.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| dedupe | boolean | – | – |
| from_id | string | – | – |
| subject | string | yes | – |
No output schema declared.
No examples provided.
mailbox_check ~322
Fetch your pending letters and your true backlog. Call at session start. v0.7.6 (F 状态可信): by default this is a **read-only probe** — letters stay ``pending``; counting mail never consumes it (禁自动 ack). The numbers report the mailbox as it is *right now*, straight from the store: - ``unread`` — 真·待办: letters currently ``pending``. Acked letters are never counted, so a mailbox full of acked-but-unhandled mail reports ``unread: 0`` honestly (the pre-0.7.6 bug: it counted the letters the call itself had just acked). - ``total`` — all non-done letters (pending + acked): the backlog you still owe, visible even when ``unread`` is 0. - ``messages`` — the pending letters themselves (sealed bodies redacted). Pass ``mark=True`` to explicitly flip the returned letters to ``acked`` (the legacy auto-ack behavior, now opt-in); the numbers above are still computed after that pass, so they never describe consumed mail as unread. Nothing here ever sets ``done`` or moves a status backwards. Adds ``ghosts`` when any thread you hold more than 5 open (non-done) letters in — that is the acked-sinking failure mode; drain those threads before starting new work.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| mark | boolean | – | – |
No output schema declared.
No examples provided.
mailbox_confirm_external ~104
Human confirmation gate for an external-origin letter (§3.3). Flips ``origin`` external→local so the wake/webhook paths may act on it. Only an owner-kind member (``boss`` or a registered ``owner``) may confirm; the operation appends to audit.log and the letter's handled_log (greppable by name). Anything else is a structured rejection.
| Name | Type | Req | Description |
|---|---|---|---|
| actor_id | string | – | – |
| msg_id | string | yes | – |
No output schema declared.
No examples provided.
mailbox_done ~36
Mark a message as handled. Done messages can be archived.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| msg_id | string | yes | – |
No output schema declared.
No examples provided.
mailbox_list ~130
List messages in your mailbox, optionally filtered by status and/or thread. Spans inbox **and** archive: ``check()`` moves handled letters into the archive, so an inbox-only view reports zero for any agent that drains regularly (HS 09-24: five status queries all returned 0 against 877 on-disk letters). ``thread`` takes a thread_id, or any subject on the thread (legacy letters without a thread_id are matched by the subject key heuristic).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| status | – | – | – |
| thread | – | – | – |
No output schema declared.
No examples provided.
mailbox_register ~111
Register this member and claim its mailbox. Idempotent — safe to call again. ``kind`` (v0.7.5): ``owner`` (the human), ``agent`` (a local agent) or ``guest`` (an external source). Empty keeps the existing/default kind; an explicit kind is a visibility decision and is written to audit.log.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| description | string | – | – |
| kind | string | – | – |
| owner | string | – | – |
No output schema declared.
No examples provided.
mailbox_reply ~44
Reply to a message thread. Routes to the original sender automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| body | string | yes | – |
| msg_id | string | yes | – |
No output schema declared.
No examples provided.
mailbox_send ~451
Send a message to one agent, a list of agents, or "all" for broadcast. dedupe=True (default) suppresses a re-send of semantically identical mail to a recipient whose inbox still holds it non-terminal (pending / acked) within the 24h dedup window: that recipient's entry comes back as {"to", "deduped": true, "existing_id"} with zero side effects — no letter, no sent.log line, no webhook. Pass dedupe=False to exempt periodic jobs. "count" counts only letters that actually landed. v0.7.5: ``sealed=True`` marks a 密封信 — the body stays readable only through the recipient agent's own tools; every other view (owner, web, other agents) sees metadata only. ``origin="external"`` marks outside-origin mail: it lands but never triggers actions (no wake, no webhook) until an owner confirms it. ``attention`` is the 打扰三档 (decision=需你拍板 / report=报备 / archive=存档). A ``guest`` sender must present a valid ``pairing_token``. v0.7.6 (PR2): ``links`` optionally carries structured pointers ``[{"title", "uri", "kind"?, "sha256"?, "note"?}]``. Schemes file/http/https/git only — anything else (ftp://, etc.) is a structured reject before the letter lands. Read paths annotate each link with a fresh ``state`` (ok/stale/denied) + ``reason``; ``file://`` links are gated by the mail root's ``allowed_roots`` config (fail-closed).
| Name | Type | Req | Description |
|---|---|---|---|
| attention | string | – | – |
| body | string | yes | – |
| dedupe | boolean | – | – |
| from_id | string | – | – |
| links | – | – | – |
| origin | string | – | – |
| pairing_token | string | – | – |
| priority | string | – | – |
| reply_to | – | – | – |
| sealed | boolean | – | – |
| subject | string | yes | – |
| to | – | yes | – |
No output schema declared.
No examples provided.
mailbox_thread ~197
Pull one thread in time order across every agent (inbox + archive). ``thread`` may be a thread_id, any message id on the thread, or a subject on the thread. Legacy letters without an id/thread_id are included via the subject-key heuristic (Re:/Fwd: prefixes stripped), so a 12-deep "Re: Re: ..." chain resolves to one thread. Letters come back oldest first with their status, so the full cross-agent conversation is visible in one call. v0.7.5 scope: an ``agent``/``guest`` caller sees only the letters it took part in (from/to includes them) — if the thread exists but none of its letters do, that is a structured ``permission denied``, not silent emptiness. Sealed bodies are readable only by the recipient agent; everyone else gets metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| thread | string | yes | – |
No output schema declared.
No examples provided.
mailbox_wait ~57
Block until a new message arrives (long-poll, up to timeout). Returns immediately if pending messages exist. Import 'time' is at module top.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| timeout_seconds | number | – | – |
No output schema declared.
No examples provided.
mailbox_whoami ~20
List all registered agents and the mail root location.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
task_create ~68
Create a task card (starts at todo). The assignee is auto-messaged — skip with notify=False.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | string | yes | – |
| due | string | – | – |
| from_id | string | – | – |
| notify | boolean | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
task_list ~32
List task cards, optionally filtered by assignee and/or status.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | – | – | – |
| status | – | – | – |
No output schema declared.
No examples provided.
task_move ~107
Move a task along todo→doing→review→done. Skips need force=True; done is terminal. Pass assignee to reassign. The (new) assignee is auto-messaged — moving a card wakes its owner.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | – | – | – |
| force | boolean | – | – |
| from_id | string | – | – |
| note | string | – | – |
| notify | boolean | – | – |
| status | string | yes | – |
| task_id | string | yes | – |
No output schema declared.
No examples provided.
What is the agent-mailbox — Mailbox and Wake System for AI Agent Teams MCP server?
agent-mailbox — Mailbox and Wake System for AI Agent Teams is an MCP server listed in the public MCP registry as io.github.polaris-smart/agent-mailbox. Mailbox + wake system for AI agent teams: letters always land, right agent wakes, quiet otherwise. This page covers its PyPI package (agent-mailbox).
Is the agent-mailbox — Mailbox and Wake System for AI Agent Teams MCP server safe to use?
agent-mailbox — Mailbox and Wake System for AI Agent Teams scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 October 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the agent-mailbox — Mailbox and Wake System for AI Agent Teams MCP server expose?
agent-mailbox — Mailbox and Wake System for AI Agent Teams exposes 14 tools: mailbox_register, mailbox_send, mailbox_check, mailbox_reply, mailbox_list, and 9 more. Their descriptions and schemas cost roughly 1,755 tokens of context every time the server is loaded.
Is the agent-mailbox — Mailbox and Wake System for AI Agent Teams MCP server still maintained?
agent-mailbox — Mailbox and Wake System for AI Agent Teams is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the agent-mailbox — Mailbox and Wake System for AI Agent Teams MCP server under?
agent-mailbox — Mailbox and Wake System for AI Agent Teams declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.