DiviMail
NPM · @DIVINDI/DIVIMAIL-MCP · 2 COMPONENTS
Give your AI agent its own email address: send, receive and read email. $0.01 USDC per send.
Available components
Last scanned (16 hours ago)
Scores higher than 30% of npm servers
Category Communication
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- 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 0 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1974 tokens (~151/item across 13 items; 13 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 Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "divimail_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 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +15
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Schema quality: 116 → 151 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.03 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 1.5.0 → 1.5.1 functional
- 3 Nov 26 43
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 Nov 2026 · Analysed npm/@divindi/divimail-mcp@1.5.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
divimail_authenticate ~132
Finish signing in with your own key or NEAR wallet and get the token used for sending, inbox, top-up and pay. Step 2 of 2: call after divimail_challenge with your Ed25519 signature (base64) and public key (base58). For provision:true accounts, use divimail_login instead. Returns a JWT.
| Name | Type | Req | Description |
|---|---|---|---|
| accountId | string | yes | Your NEAR account ID |
| publicKey | string | yes | Base58-encoded NEAR public key |
| signature | string | yes | Base64-encoded Ed25519 signature of the challenge message |
No output schema declared.
No examples provided.
divimail_balance ~80
Check how much USDC a DiviMail address has for sending email or paying. Call before divimail_send or divimail_pay if unsure; if low, use divimail_request_topup. No token needed, just the @divindi.io address.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The @divindi.io email address to check |
No output schema declared.
No examples provided.
divimail_challenge ~100
Start signing in with your own key or NEAR wallet: returns a challenge message to sign. Step 1 of 2. Sign it, then call divimail_authenticate. For accounts created with provision:true, use divimail_login instead (simpler). Automated agents with a service secret can use divimail_service_token.
| Name | Type | Req | Description |
|---|---|---|---|
| accountId | string | yes | Your NEAR account ID (e.g. myagent.near) |
No output schema declared.
No examples provided.
divimail_inbox ~152
Check your agent's inbox: lists received emails for its @divindi.io address. Call this first to see what arrived, then use divimail_read with a messageId for the full content, and divimail_mark_read when done. For mail the agent sent, use divimail_sent. Needs a token. Optional limit (default 20).
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Your agent's full @divindi.io email address (e.g. myagent@divindi.io) | |
| limit | number | – | Number of messages to return (default 20) |
| token | string | yes | JWT token from divimail_login, divimail_authenticate or divimail_service_token |
No output schema declared.
No examples provided.
divimail_login ~136
Sign the agent in to its DiviMail address and get the token needed to send, check the inbox, top up or pay. Use this after divimail_register when you have the saved apiKey (starts with "dm_"). Use divimail_challenge/divimail_authenticate for own-wallet accounts instead. No NEAR signature or service secret needed. Returns a JWT.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | yes | The one-time apiKey returned by a provisioned divimail_register (starts with "dm_") |
| string | yes | Your @divindi.io email address (from divimail_register) |
No output schema declared.
No examples provided.
divimail_mark_read ~121
Mark an email in your agent's inbox as read so it is not handled twice. Use after divimail_read (or divimail_inbox) with the same messageId. Needs a token.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Your agent's full @divindi.io email address (e.g. myagent@divindi.io) | |
| messageId | string | yes | Message ID from divimail_inbox |
| token | string | yes | JWT token from divimail_login, divimail_authenticate or divimail_service_token |
No output schema declared.
No examples provided.
divimail_pay ~204
Pay another agent (or person) that has a @divindi.io address, in USDC from your DiviMail balance. Use for agent-to-agent payments, not for funding yourself (use divimail_request_topup). Free, instant internal transfer. Max $50 per transfer, $100 per sender per rolling 24h. Non-DiviMail addresses not supported. Needs a token.
| Name | Type | Req | Description |
|---|---|---|---|
| amountUsdc | number|string | yes | Amount in USDC, > 0, at most 6 decimal places, max 50 (e.g. 1.25) |
| from | string | yes | Your @divindi.io email address (must match the token) |
| memo | string | – | Optional note stored with the transfer (max 280 chars) |
| to | string | yes | Recipient @divindi.io email address |
| token | string | yes | JWT token from divimail_login, divimail_authenticate or divimail_service_token |
No output schema declared.
No examples provided.
divimail_read ~130
Open and read one email in full (body and details) from your agent's mailbox. Call after divimail_inbox using a messageId from that list; then call divimail_mark_read if you want it marked read. Needs a token.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Your agent's full @divindi.io email address (e.g. myagent@divindi.io) | |
| messageId | string | yes | Message ID from divimail_inbox |
| token | string | yes | JWT token from divimail_login, divimail_authenticate or divimail_service_token |
No output schema declared.
No examples provided.
divimail_register ~291
Give an AI agent its own @divindi.io email address so it can send and receive email. Call this once to create the address, then call divimail_login (or divimail_challenge + divimail_authenticate) to get a token. Use exactly one of: provision:true (easiest), publicKey (your ed25519 key; only the public key is stored), or nearAccountId (own NEAR wallet, no apiKey). provision/publicKey return an apiKey shown ONCE, so save it.
| Name | Type | Req | Description |
|---|---|---|---|
| emailAlias | string | yes | Desired email alias (e.g. myagent → myagent@divindi.io) |
| nearAccountId | string | – | NEAR account ID (e.g. myagent.near) — omit to auto-provision a new NEAR account |
| provision | boolean | – | Set true to auto-provision a NEAR account if you do not have one. A provisioned registration returns a one-time apiKey — save it and use divimail_login. |
| publicKey | string | – | Your own ed25519 public key (base58, optionally "ed25519:"-prefixed; must decode to 32 bytes). Client-side keygen: DiviMail stores only this public key and holds no private key. Returns a one-time ap… |
No output schema declared.
No examples provided.
divimail_request_topup ~136
Add funds so your agent can keep sending email: returns USDC deposit instructions for its DiviMail balance. It does not move money itself. Use when divimail_balance is low. Returns a NEAR mainnet deposit address plus NEAR Intents links for Base, Ethereum, Arbitrum and Solana; credited automatically within 60 s. Needs a token.
| Name | Type | Req | Description |
|---|---|---|---|
| alias | string | yes | Your email alias (e.g. "patch" for patch@divindi.io) |
| token | string | yes | JWT token from divimail_login, divimail_authenticate or divimail_service_token |
No output schema declared.
No examples provided.
divimail_send ~226
Send an email from your agent's @divindi.io address to any email address, human or agent. Needs a token from divimail_login (or authenticate/service_token). If the balance is low, see divimail_balance and divimail_request_topup. Costs $0.01 USDC per email. Supports plain text, optional HTML, CC and BCC.
| Name | Type | Req | Description |
|---|---|---|---|
| bcc | – | – | Optional BCC recipient(s) — a single email or an array of emails |
| cc | – | – | Optional CC recipient(s) — a single email or an array of emails |
| from | string | yes | Sender DiviMail address (e.g. myagent@divindi.io) |
| html | string | – | Optional HTML email body |
| subject | string | yes | Email subject line |
| text | string | yes | Plain text email body |
| to | string | yes | Recipient email address (any email — not just @divindi.io) |
| token | string | yes | JWT token from divimail_login, divimail_authenticate or divimail_service_token |
No output schema declared.
No examples provided.
divimail_sent ~135
See what emails your agent has sent: lists sent messages for its @divindi.io address. Use this to confirm a divimail_send went out or to review history. For received mail use divimail_inbox. Needs a token. Optional limit (default 20).
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Your agent's full @divindi.io email address (e.g. myagent@divindi.io) | |
| limit | number | – | Number of messages to return (default 20) |
| token | string | yes | JWT token from divimail_login, divimail_authenticate or divimail_service_token |
No output schema declared.
No examples provided.
divimail_service_token ~131
Get a token for a scheduled or unattended agent without a live signature or apiKey. Use only when this MCP server has DIVIMAIL_SERVICE_SECRET set (operator-issued). Otherwise use divimail_login (apiKey) or divimail_challenge/divimail_authenticate. Pass serviceSecret only to override the env var. Returns a JWT.
| Name | Type | Req | Description |
|---|---|---|---|
| accountId | string | yes | The NEAR account ID of the agent (e.g. patch.divimail.near) |
| serviceSecret | string | – | Override only — omit to use the server's DIVIMAIL_SERVICE_SECRET env var |
No output schema declared.
No examples provided.
How do I install the DiviMail MCP server?
DiviMail runs locally as an npm package, launched with npx -y @divindi/divimail-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @divindi/divimail-mcp
claude mcp add tech-divindi-divimail -- npx -y @divindi/divimail-mcp
What is the DiviMail MCP server?
DiviMail is an MCP server listed in the public MCP registry as tech.divindi/divimail. Give your AI agent its own email address: send, receive and read email. $0.01 USDC per send. This page covers its npm package (@divindi/divimail-mcp).
Is the DiviMail MCP server safe to use?
DiviMail scores 58 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. 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 DiviMail MCP server expose?
DiviMail exposes 13 tools: divimail_register, divimail_login, divimail_challenge, divimail_authenticate, divimail_service_token, and 8 more. Their descriptions and schemas cost roughly 1,974 tokens of context every time the server is loaded.
Is the DiviMail MCP server still maintained?
DiviMail is still listed as active in the MCP registry. We last reached this channel on 4 November 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 DiviMail MCP server under?
DiviMail declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.