# DiviMail (remote · mcp.divindi.io)

Give your AI agent its own email address: send, receive and read email. $0.01 USDC per send.

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `mcp.divindi.io`: 63/100 (this document), [markdown](https://verifymcp.io/servers/tech-divindi-divimail/mcp.md), [page](https://verifymcp.io/servers/tech-divindi-divimail/mcp)
- npm · `@divindi/divimail-mcp`: 58/100, [markdown](https://verifymcp.io/servers/tech-divindi-divimail/divindi-divimail-mcp.md), [page](https://verifymcp.io/servers/tech-divindi-divimail/divindi-divimail-mcp)

## Channel facts

- Endpoint: `https://mcp.divindi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.5.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http tech-divindi-divimail 'https://mcp.divindi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "tech-divindi-divimail": {
      "url": "https://mcp.divindi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tech-divindi-divimail": {
      "type": "http",
      "url": "https://mcp.divindi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.tech-divindi-divimail]
url = "https://mcp.divindi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tech-divindi-divimail": {
      "type": "remote",
      "url": "https://mcp.divindi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tech-divindi-divimail --url 'https://mcp.divindi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tech-divindi-divimail:
    url: "https://mcp.divindi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "tech-divindi-divimail": {
      "Transport": "http",
      "Url": "https://mcp.divindi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tech-divindi-divimail -t streamable-http -u 'https://mcp.divindi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "tech-divindi-divimail": {
      "type": "http",
      "url": "https://mcp.divindi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 63)

First indexed and scored.

## MCP tools (12)

### `divimail_register` (~291 tokens)

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.

Input parameters:

- `emailAlias` (string, required): 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…

### `divimail_login` (~136 tokens)

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.

Input parameters:

- `apiKey` (string, required): The one-time apiKey returned by a provisioned divimail_register (starts with "dm_")
- `email` (string, required): Your @divindi.io email address (from divimail_register)

### `divimail_challenge` (~100 tokens)

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.

Input parameters:

- `accountId` (string, required): Your NEAR account ID (e.g. myagent.near)

### `divimail_authenticate` (~132 tokens)

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.

Input parameters:

- `accountId` (string, required): Your NEAR account ID
- `publicKey` (string, required): Base58-encoded NEAR public key
- `signature` (string, required): Base64-encoded Ed25519 signature of the challenge message

### `divimail_send` (~226 tokens)

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.

Input parameters:

- `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, required): Sender DiviMail address (e.g. myagent@divindi.io)
- `html` (string): Optional HTML email body
- `subject` (string, required): Email subject line
- `text` (string, required): Plain text email body
- `to` (string, required): Recipient email address (any email — not just @divindi.io)
- `token` (string): JWT token from divimail_login, divimail_authenticate or divimail_service_token

### `divimail_inbox` (~152 tokens)

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).

Input parameters:

- `email` (string, required): 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

### `divimail_sent` (~135 tokens)

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).

Input parameters:

- `email` (string, required): 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

### `divimail_read` (~130 tokens)

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.

Input parameters:

- `email` (string, required): Your agent's full @divindi.io email address (e.g. myagent@divindi.io)
- `messageId` (string, required): Message ID from divimail_inbox
- `token` (string): JWT token from divimail_login, divimail_authenticate or divimail_service_token

### `divimail_mark_read` (~121 tokens)

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.

Input parameters:

- `email` (string, required): Your agent's full @divindi.io email address (e.g. myagent@divindi.io)
- `messageId` (string, required): Message ID from divimail_inbox
- `token` (string): JWT token from divimail_login, divimail_authenticate or divimail_service_token

### `divimail_balance` (~80 tokens)

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.

Input parameters:

- `email` (string, required): The @divindi.io email address to check

### `divimail_request_topup` (~136 tokens)

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.

Input parameters:

- `alias` (string, required): Your email alias (e.g. "patch" for patch@divindi.io)
- `token` (string): JWT token from divimail_login, divimail_authenticate or divimail_service_token

### `divimail_pay` (~204 tokens)

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.

Input parameters:

- `amountUsdc` (number|string, required): Amount in USDC, > 0, at most 6 decimal places, max 50 (e.g. 1.25)
- `from` (string, required): Your @divindi.io email address (must match the token)
- `memo` (string): Optional note stored with the transfer (max 280 chars)
- `to` (string, required): Recipient @divindi.io email address
- `token` (string): JWT token from divimail_login, divimail_authenticate or divimail_service_token

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/tech-divindi-divimail/mcp#diagnostics

## Score history

- 2026-11-04: 63

## Common questions

### 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.

## Links

- Remote endpoint: https://mcp.divindi.io/mcp
- Website: https://divimail.divindi.tech/
- Changelog RSS feed: https://verifymcp.io/servers/tech-divindi-divimail/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/tech-divindi-divimail/mcp.json
- HTML version of this page: https://verifymcp.io/servers/tech-divindi-divimail/mcp