Skip to content

Yeevu Email Deliverability MCP server

com.yeevu/email-deliverabilityyeevu.comstreamable-httpv1.0.0Scanned

Check any domain's email deliverability: MX, SPF, DKIM, DMARC, MTA-STS, TLS-RPT, BIMI, blacklists.

3 tools: 2 change things and 1 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • 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 Yeevu Email Deliverability MCP server can do

The Yeevu Email Deliverability MCP server is published by yeevu.com, a domain the MCP Registry verified. It has 3 tools. It can create or change data (2 tools: check_email_health and check_email_record), but cannot delete data. 1 tool only reads.

1 tool reads private data (get_full_report_link); 3 tools bring in text other people can write (check_email_health, check_email_record and get_full_report_link).

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.

Last scanned Nov 13, 2026, version 1.0.0.

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.

3 tools

Changes things 2Claude Code: ask
  • check_email_healthCheck a domain's email deliverability with Yeevu: MX, SPF, DKIM, DMARC, MTA-STS, TLS-RPT, BIMI and blacklist status, with what is wrong and how to fix it.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 a domain's email deliverability with Yeevu: MX, SPF, DKIM, DMARC, MTA-STS, TLS-RPT, BIMI and blacklist status, with what is wrong and how to fix it. Use when someone asks why their emails go to spam, aren't delivered, or whether their email setup is correct.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • check_email_recordRun one Yeevu email check on a domain in full detail: mx, spf, dkim, dmarc, mta_sts, tls_rpt, bimi_record or blacklist.Reads text others write1 finding

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    • 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.

    Findings

    • Warn

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

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Run one Yeevu email check on a domain in full detail: mx, spf, dkim, dmarc, mta_sts, tls_rpt, bimi_record or blacklist. Use for questions about one record, for example 'is my SPF right?' or 'am I blacklisted?'.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
Only reads 1Show 1 read-only tool

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.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

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

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 21, 2026, 19:21 UTC, unchanged since Nov 14, 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
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

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

    Matched text

    https://mcp.yeevu.com/mcp: tools/list returned 3 tools to an anonymous client, including check_email_health (write), check_email_record (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

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

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.

    What this check looks for

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.

Install

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

claude mcp add --transport http email-deliverability https://mcp.yeevu.com/mcp
claude mcp add --transport http email-deliverability https://mcp.yeevu.com/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": [
      "mcp__email-deliverability__get_full_report_link"
    ],
    "ask": [
      "mcp__email-deliverability__check_email_health",
      "mcp__email-deliverability__check_email_record"
    ],
    "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 email-deliverability. Review it before you use it.

Capability tags behind 3 rules
  • mcp__email-deliverability__check_email_health untrusted-input
  • mcp__email-deliverability__check_email_record untrusted-input
  • mcp__email-deliverability__get_full_report_link private-data, 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/com.yeevu/email-deliverability/verify?hash=94fb318574eb5b2088e7cc15a9a9536485cd39db8ac9462f2b0333af4362e894" | jq -e '.changed == false'

Pinned hash 94fb318574eb, from Nov 13, 2026, 14:18 UTC.

Watch

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

https://radar.anlyon.com/servers/com.yeevu/email-deliverability/changes.xml

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

Badge

Anlyon Radar badge for com.yeevu/email-deliverability
[![Anlyon Radar](https://radar.anlyon.com/badge/com.yeevu/email-deliverability.svg)](https://radar.anlyon.com/servers/com.yeevu/email-deliverability)

Source: MCP Registry. Synced Nov 13, 2026, 14:17 UTC.

Yeevu Email Deliverability MCP server: questions and answers

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

Is the Yeevu Email Deliverability MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 2 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 Yeevu Email Deliverability MCP server delete data?

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

Can the Yeevu Email Deliverability MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Yeevu Email Deliverability MCP server have?

3 tools: 2 write, 1 read. check_email_health, check_email_record and get_full_report_link.

Does the Yeevu Email Deliverability MCP server need sign-in or OAuth?

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

Does the Yeevu Email Deliverability MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Yeevu Email Deliverability MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.