DiviMail
REMOTE · MCP.DIVINDI.IO · 2 COMPONENTS
Give your AI agent its own email address: send, receive and read email. $0.01 USDC per send.
Available components
Last scanned (13 hours ago)
Scores higher than 44% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Communication
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1843 tokens (~153/item across 12 items; 12 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 12 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
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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 63
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 · Probed https://mcp.divindi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.divindi.io | CN=YR1,O=Let's Encrypt,C=US | 4 Nov 2026 | 2 Feb 2027 | RSA 2048 | SHA256-RSA | 6fc90b9ad43656afc7eabab1fda34f46d12 |
| SANs: mcp.divindi.io | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.divindi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| divindi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.divindi.io/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.divindi.io/mcp | HTTPS enforced | 301 | https://mcp.divindi.io/mcp |
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 | – | 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 | – | 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 | – | 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 | – | 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 | – | 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 | – | 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 | – | JWT token from divimail_login, divimail_authenticate or divimail_service_token |
No output schema declared.
No examples provided.
How do I install the DiviMail MCP server?
DiviMail is a hosted endpoint at https://mcp.divindi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.divindi.io
claude mcp add --transport http tech-divindi-divimail 'https://mcp.divindi.io/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 hosted endpoint (https://mcp.divindi.io/mcp).
Is the DiviMail MCP server safe to use?
DiviMail scores 63 out of 100 on VerifyMCP. 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 12 tools: divimail_register, divimail_login, divimail_challenge, divimail_authenticate, divimail_send, and 7 more. Their descriptions and schemas cost roughly 1,843 tokens of context every time the server is loaded.
Does the DiviMail MCP server require authentication?
No. We connected to DiviMail without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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.