Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Yeevu Email Deliverability

REMOTE · MCP.YEEVU.COM

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

Available components

+4 this week 76 Trust /100

Last scanned (17 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 357 tokens (~119/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 13 Nov 26 72

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.yeevu.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=yeevu.com CN=WE1,O=Google Trust Services,C=US 13 Nov 2026 11 Feb 2027 ECDSA 256 ECDSA-SHA256 b36e4cc0fef920a4133c56900ff7c5fe
SANs: yeevu.com, mcp.yeevu.com, *.mcp.yeevu.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.yeevu.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
yeevu.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.yeevu.com/mcp Verified 200
http (plaintext) http://mcp.yeevu.com/mcp HTTPS enforced 301 https://mcp.yeevu.com/mcp
MCP tools · 3 exposed · ~289 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_email_health ~102

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.

NameTypeReqDescription
domainstringyesThe domain to check, for example acme.com. A URL or email address also works.

No output schema declared.

No examples provided.

check_email_record ~108

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?'.

NameTypeReqDescription
checkstringyesWhich check to run.
domainstringyesThe domain to check, for example acme.com. A URL or email address also works.

No output schema declared.

No examples provided.

get_full_report_link ~79

Get a link to Yeevu's free full email deliverability report for a domain, with an overall score and step-by-step fixes. Offer it after a check, or when someone wants to see everything in one place.

NameTypeReqDescription
domainstringyesThe domain to check, for example acme.com. A URL or email address also works.

No output schema declared.

No examples provided.

Install

How do I install the Yeevu Email Deliverability MCP server?

Yeevu Email Deliverability is a hosted endpoint at https://mcp.yeevu.com/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.

remote · mcp.yeevu.com

# add to Claude Code
claude mcp add --transport http com-yeevu-email-deliverability 'https://mcp.yeevu.com/mcp'
Common questions

What is the Yeevu Email Deliverability MCP server?

Yeevu Email Deliverability is an MCP server listed in the public MCP registry as com.yeevu/email-deliverability. Check any domain's email deliverability: MX, SPF, DKIM, DMARC, MTA-STS, TLS-RPT, BIMI, blacklists. This page covers its hosted endpoint (https://mcp.yeevu.com/mcp).

Is the Yeevu Email Deliverability MCP server safe to use?

Yeevu Email Deliverability scores 76 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 Yeevu Email Deliverability MCP server expose?

Yeevu Email Deliverability exposes 3 tools: check_email_health, check_email_record, get_full_report_link. Their descriptions and schemas cost roughly 289 tokens of context every time the server is loaded.

Does the Yeevu Email Deliverability MCP server require authentication?

No. We connected to Yeevu Email Deliverability without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Yeevu Email Deliverability MCP server still maintained?

Yeevu Email Deliverability is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Yeevu Email Deliverability MCP server?

VerifyMCP ran 13 checks on Yeevu Email Deliverability, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.