Neural network swarm orchestration with WebAssembly acceleration and MCP integration
Nothing to run from here
Swarmail is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
99/100
trust score
381
downloads a day
local
runs on your machine
2k
downloads in 30d
What it does
Mail between coding-agent sessions, on one machine or across machines, through MCP and a CLI. Includes threaded messages, full-text search, per-repository agent rosters, advisory file reservations, and optional mail notifications.
Install and start a Swarmail server before launching the stdio relay. A remote server needs its full MCP endpoint and bearer-token file.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user swarmail-mcp '--' npx -y swarmail-mcp
# 2 — ask your agent for something these tools do
# health_check, ensure_project, register_agent and 19 more
Swarmail costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
PublisherVerified · since 2026
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Swarmail as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user swarmail-mcp '--' npx -y swarmail-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take SWARMAIL_URL (MCP endpoint of the running Swarmail server) if you want to set it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
22 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Report whether the server and its database answer, with the database path. Call it
No parameter schema on file.
Create a project without registering an agent, returning id, slug, human_key and
No parameter schema on file.
Register or update an agent identity in a project, creating the project if needed.
No parameter schema on file.
Ensure the project, register an agent, optionally reserve paths, and return {project,
No parameter schema on file.
Return one agent's profile: program, model, task description, and first and last
No parameter schema on file.
Return an array of non-retired agents in a project, most recently active first, with
No parameter schema on file.
At an agreed whole-session closeout or a whole-session completion with nothing remaining, record the closeout, release owned resources and finish required dependency notices, then retire your own registration in every project you joined.
No parameter schema on file.
Bring a retired agent back into list_agents so it can receive messages again; earlier
No parameter schema on file.
Send a Markdown message to named agents in the same project. An unregistered, retired or closed
No parameter schema on file.
Reply in a message's thread, returning the stored message with reply_to. message_id
No parameter schema on file.
Withdraw your message from recipients whose delivery has not been read, acknowledged or withdrawn. Returns message_id, revision and per-recipient withdrawn/already_withdrawn/too_late results. Omit recipients for all deliveries; an explicit subset must be nonempty and valid. Retains content and…
No parameter schema on file.
Change only your message's low/normal/high/urgent priority. Requires current expected_revision from inbox, history or sender receipt and a nonempty idempotency_key. Returns message_id, revision, importance and changed. A stale revision fails before a matching-value no-op. Edits affect metadata…
No parameter schema on file.
Return an array of your latest received message metadata, newest first; include_bodies
No parameter schema on file.
Return one newest-first page across registrations matching your host/session tag or T3 thread.
No parameter schema on file.
Mark one received message read without acknowledging it, returning message_id, read and
No parameter schema on file.
Acknowledge one received message and mark it read, returning message_id, acknowledged,
No parameter schema on file.
Return a message's persisted_at and recipients with kind, read_at, acknowledged,
No parameter schema on file.
Search subjects and bodies across a project, returning {result, next_cursor?} without
No parameter schema on file.
Return {thread_id, summary:{participants, total_messages}, messages} for you to
No parameter schema on file.
Reserve repository-relative paths or globs so other agents know what you are editing.
No parameter schema on file.
Extend your active reservations by extend_seconds past their current expiry; each call
No parameter schema on file.
Release your active reservations when you finish work so other agents can reserve
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Swarmail or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 99 / 100
Release 0.7.2 · scanned 28 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest7256c98596b4905c84813c732b81e8c37a4140bacd5496adc8846c86ef4ef3b7
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest7256c98596b4905c
Scanned2026-10-28
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.7.2. Pin a release below and the command asks for exactly that one.
0.7.2
28 Oct 2026
latestNo release note was published with this version.
0.7.1
27 Oct 2026
No release note was published with this version.
0.6.0
16 Oct 2026
No release note was published with this version.
0.5.2
10 Oct 2026
No release note was published with this version.
0.1.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Swarmail can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.