Skip to content

DiviMail MCP server

tech.divindi/divimaildivindi.techstreamable-httpv1.5.1Scanned

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

7 tools: 1 do something that can't be undone and 6 change things.

Tools: 0 delete, 1 irreversible, 6 write, 0 read.
  • Reads private data · 1
  • Reads text others write · 7
  • Can send data out · 1
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the DiviMail MCP server can do

The DiviMail MCP server is published by divindi.tech, a domain the MCP Registry verified. It has 7 tools. It can do things that cannot be undone, such as sending, paying or publishing (divimail_send) and create or change data (6 tools: divimail_register, divimail_inbox, divimail_sent, divimail_read and 2 more), but cannot delete data. None of its tools only reads.

1 tool reads private data (divimail_read); 7 tools bring in text other people can write (divimail_register, divimail_send, divimail_inbox and 4 more); 1 tool can send data out of your system (divimail_send). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 18, 2026, version 1.5.1.

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.

7 tools

Can't be undone 1Claude Code: ask
  • divimail_sendSend an email from your agent's @divindi.io address to any email address, human or agent.Reads text others writeCan 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

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • 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. When connected through an app sign-in, no token or address is needed. 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.

    Annotations the server declares

    • title: Send email
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Changes things 6Claude Code: ask
  • divimail_balanceCheck how much USDC a DiviMail address has for sending email or paying.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    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.

    Annotations the server declares

    • title: Check USDC balance
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • divimail_inboxCheck your agent's inbox: lists received emails for its @divindi.io address.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    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. When connected through an app sign-in, no token or address is needed. Optional limit (default 20).

    Annotations the server declares

    • title: List inbox
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • divimail_mark_readMark an email in your agent's inbox as read so it is not handled twice.Reads text others writeNo findings

    Why it is in this group

    • The name "divimail_mark_read" says "mark": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    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. When connected through an app sign-in, no token or address is needed.

    Annotations the server declares

    • title: Mark email read
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • divimail_readOpen and read one email in full (body and details) from your agent's mailbox.Reads private dataReads text others write1 finding

    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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • private-dataThe description's first sentence says "email": it reads mail.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "open" and "email": it reads inbound email, which other people can write.

    Findings

    • Warn

      The server marks "divimail_read" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "divimail_read" says "read": a word for reading.

      What this check looks for
    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. When connected through an app sign-in, no token or address is needed.

    Annotations the server declares

    • title: Read email
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • divimail_registerGive an AI agent its own @divindi.io email address so it can send and receive email.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    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 sign in: through the app's connection sign-in if you are using one, otherwise with divimail_login (or divimail_challenge + divimail_authenticate). 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.

    Annotations the server declares

    • title: Create agent email address
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • divimail_sentSee what emails your agent has sent: lists sent messages for its @divindi.io address.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    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. When connected through an app sign-in, no token or address is needed. Optional limit (default 20).

    Annotations the server declares

    • title: List sent email
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

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.

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

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write7
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__divimail__divimail_send"
    ]
  }
}

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

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 19, 2026, 17:23 UTC, unchanged since Nov 5, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
7
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.divindi.io/.well-known/oauth-protected-resource/mcp
Authorization servers
https://divindi.io
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 7 tools that change things (1 irreversible, 6 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.divindi.io/mcp: tools/list returned 7 tools to an anonymous client, including divimail_send (irreversible), divimail_register (write), divimail_inbox (write), divimail_sent (write), divimail_read (write) and 2 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "divimail_read" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "divimail_read" says "read": a word for reading.

    What this check looks for

History

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

  1. Tools5 removed, 7 changed.−5 removed~7 changedView diff
    • Removed:divimail_authenticate
    • Removed:divimail_challenge
    • Removed:divimail_login
    • Removed:divimail_pay
    • Removed:divimail_request_topup
    • Changed:divimail_balanceChanges thingsinputSchemaannotations
    • Changed:divimail_inboxChanges thingsdescriptioninputSchemaannotations
    • Changed:divimail_mark_readChanges thingsdescriptioninputSchemaannotations
    • Changed:divimail_readChanges thingsdescriptioninputSchemaannotations
    • Changed:divimail_registerChanges thingsdescriptionannotations
    • Changed:divimail_sendCan't be undonedescriptioninputSchemaannotations
    • Changed:divimail_sentChanges thingsdescriptioninputSchemaannotations

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_send",
      "mcp__divimail__divimail_inbox",
      "mcp__divimail__divimail_sent",
      "mcp__divimail__divimail_read",
      "mcp__divimail__divimail_mark_read",
      "mcp__divimail__divimail_balance"
    ],
    "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 7 rules
  • mcp__divimail__divimail_register untrusted-input
  • mcp__divimail__divimail_send untrusted-input, outbound
  • mcp__divimail__divimail_inbox untrusted-input
  • mcp__divimail__divimail_sent untrusted-input
  • mcp__divimail__divimail_read private-data, untrusted-input
  • mcp__divimail__divimail_mark_read untrusted-input
  • mcp__divimail__divimail_balance untrusted-input

Pin

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://radar.anlyon.com/api/v1/servers/tech.divindi/divimail/verify?hash=53785bec7c70bd8559ba8dbbc798da9e9240242f2b3f4dcca142a1bf5354260d" | jq -e '.changed == false'

Pinned hash 53785bec7c70, from Nov 18, 2026, 08:17 UTC.

Watch

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

https://radar.anlyon.com/servers/tech.divindi/divimail/changes.xml

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

Badge

Anlyon Radar badge for tech.divindi/divimail
[![Anlyon Radar](https://radar.anlyon.com/badge/tech.divindi/divimail.svg)](https://radar.anlyon.com/servers/tech.divindi/divimail)

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

DiviMail MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the DiviMail MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 7 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the DiviMail MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the DiviMail MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: divimail_send.

What tools does the DiviMail MCP server have?

7 tools: 1 irreversible, 6 write. divimail_send, divimail_register, divimail_inbox, divimail_sent, divimail_read, divimail_mark_read and divimail_balance.

Does the DiviMail MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the DiviMail MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): divimail_send.

Has the DiviMail MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.