DiviMail

tech.divindi/divimaildivindi.techstreamable-httpv1.5.1Scanned 3 hours ago

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

12 tools: 3 do something that can't be undone and 9 change things.

Reads private data · 1
Reads text others write · 1
Can send data out · 2
No findings

Anlyon alternative

12 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

12 tools

Can't be undone 3Sends, pays, publishes or merges: once done, it cannot be taken back.Claude Code: ask

divimail_payPay another agent (or person) that has a @divindi.io address, in USDC from your DiviMail balance.Can send data outNo findings
Why it is in this group
- The name "divimail_pay" says "pay": a word that usually means money moves, which cannot be taken back.
- The input addresses people (input.to): what it sends cannot be taken back.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Description, as the server wrote it
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.
divimail_request_topupAdd funds so your agent can keep sending email: returns USDC deposit instructions for its DiviMail balance.No findings
Why it is in this group
- The name "divimail_request_topup" says "request": a word for a change.
- The name "divimail_request_topup" also says "topup": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it
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.
divimail_sendSend an email from your agent's @divindi.io address to any email address, human or agent.Can send data outNo findings
Why it is in this group
- The name "divimail_send" says "send": a word for sending, and what is sent cannot be taken back.
- The input addresses people (input.to): what it sends cannot be taken back.
What it can reach
- outboundThe name "divimail_send" says "send": it sends or publishes something to other people.
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Description, as the server wrote it
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.

Changes things 9Creates or changes something that can be changed back.Claude Code: ask

divimail_authenticateFinish signing in with your own key or NEAR wallet and get the token used for sending, inbox, top-up and pay.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it
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.
divimail_balanceCheck how much USDC a DiviMail address has for sending email or paying.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it
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.
divimail_challengeStart signing in with your own key or NEAR wallet: returns a challenge message to sign.No findings
Why it is in this group
- The description's first verb is "start": a word for a change.
Description, as the server wrote it
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.
divimail_inboxCheck your agent's inbox: lists received emails for its @divindi.io address.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it
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).
divimail_loginSign the agent in to its DiviMail address and get the token needed to send, check the inbox, top up or pay.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it
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.
divimail_mark_readMark an email in your agent's inbox as read so it is not handled twice.No findings
Why it is in this group
- The name "divimail_mark_read" says "mark": a word for a change.
Description, as the server wrote it
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.
divimail_readOpen and read one email in full (body and details) from your agent's mailbox.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "divimail_read" says "read": a word for reading.
- The description's first verb is "open": a word for a change.
What it can reach
- private-dataThe description's first sentence says "email": it reads mail.
- untrusted-inputThe description's first sentence says "open" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it
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.
divimail_registerGive an AI agent its own @divindi.io email address so it can send and receive email.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it
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.
divimail_sentSee what emails your agent has sent: lists sent messages for its @divindi.io address.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it
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).

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

2 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 untrusted-input tool breaks every one.

Reads private data1: Reads files, mail, messages, databases, secrets, calendars or repositories.; divimail_read
Reads text others write1: Brings in text someone else can write: web pages, inbound email, messages, issues and comments.; divimail_read
Can send data out2: Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.; divimail_pay
divimail_send

deny to break every path

{
  "permissions": {
    "deny": [
      "mcp__divimail__divimail_read"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

All changes to this server

Install

Pinned to version 1.5.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http divimail https://mcp.divindi.io/mcp

claude mcp add --transport http divimail https://mcp.divindi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json

{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__divimail__divimail_register",
      "mcp__divimail__divimail_login",
      "mcp__divimail__divimail_challenge",
      "mcp__divimail__divimail_authenticate",
      "mcp__divimail__divimail_send",
      "mcp__divimail__divimail_inbox",
      "mcp__divimail__divimail_sent",
      "mcp__divimail__divimail_read",
      "mcp__divimail__divimail_mark_read",
      "mcp__divimail__divimail_balance",
      "mcp__divimail__divimail_request_topup",
      "mcp__divimail__divimail_pay"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as divimail. Review it before you use it.

Capability tags behind 3 rules

mcp__divimail__divimail_send outbound
mcp__divimail__divimail_read private-data, untrusted-input
mcp__divimail__divimail_pay outbound

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://anlyon.dev/api/v1/servers/tech.divindi/divimail/verify?hash=3f0fdd5f203ca059019b30b0d94c0ae4b08143720386fdf24df5b6c86982976d" | jq -e '.changed == false'

Pinned hash 3f0fdd5f203c, from Nov 4, 2026, 14:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/tech.divindi/divimail/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

[![anlyon.dev](https://anlyon.dev/badge/tech.divindi/divimail.svg)](https://anlyon.dev/servers/tech.divindi/divimail)

Source: MCP Registry. Synced Nov 4, 2026, 14:18 UTC.