Skip to content

Divindi MCP server

Which MCP servers are Divindi's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-11-04

← Back to Divindi

Whose server it is
  • Registry nametech.divindi/divimailverified in the MCP registry

The registry name sits under divindi.tech. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-11-04
  • Stateanswerschecked 2026-11-04
  • Tools12
  • Server calls itselfdivimail
  • Server version1.5.0
  • Protocol version2025-06-18

On 2026-11-04 the server answered initialize and tools/list without a sign-in. First answer in 494 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 1 of the 7 days it takes to judge reliability.

Once connected

  • divimail_send, divimail_pay change data without a sign-in: anyone with the address can call them.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-11-04
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • Use258 npm downloads a week
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer370 ms
  • Space in an agent's context≈ 2,506 tokensthe definitions of all its tools (12), which an agent carries on every turn
  • Tool definitionsB · 83 of 100
  • Typed results0 of 12 toolsdeclared outputSchema: results come typed, read once
  • Not saying whether it only reads or can destroy: 12 of 12

Worth a look

  • Tools that change data, on a server that answers without a sign-in: divimail_send, divimail_pay

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers12 tools · read 2026-11-04
  • divimail_register

    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…

  • divimail_login

    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…

  • divimail_challenge

    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…

  • divimail_authenticate

    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…

  • divimail_send

    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…

  • divimail_inbox

    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

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

  • divimail_read

    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_mark_read

    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_balance

    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_request_topup

    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…

  • divimail_pay

    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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Add it

Claude Code, in a terminal

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

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.divindi.io/mcp as a custom connector in the settings.

Also shipped through: npm

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.