Email Verifier MCP server
tech.noahsarch/email-verifiernoahsarch.techstreamable-httpv0.1.1Scanned
Verify emails: syntax, MX, disposable, role, typo fix, optional SMTP probe, SPF/DMARC.
5 tools: 4 change things and 1 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
4 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.
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 Email Verifier MCP server can do
The Email Verifier MCP server is published by noahsarch.tech, a domain the MCP Registry verified. It has 5 tools. It can create or change data (4 tools: verify_email, verify_emails, domain_check and suggest_fix), but cannot delete data. 1 tool only reads.
1 tool reads private data (extract_emails); 1 tool brings in text other people can write (extract_emails).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 13, 2026, version 0.1.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.
5 tools
Changes things 4Claude Code: ask
domain_checkDoes the domain accept mail, which MX hosts, is it a disposable or free-mail provider, does it publish SPF and DMARC (and the DMARC policy)?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.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Does the domain accept mail, which MX hosts, is it a disposable or free-mail provider, does it publish SPF and DMARC (and the DMARC policy)? Use before trusting a sender domain or when onboarding a company. Example: domain 'noahsarch.tech'. Response: result with status (deliverable | risky | undeliverable | invalid | unknown), reason, score 0–100, the checks run, plus data_confidence, estimated_items[], sources[], data_version, warnings[] and a disclaimer. No logging of addresses.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
suggest_fixFix common typos: gmial.com, hotmail.con, yaho.com, stray spaces/dots.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.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Fix common typos: gmial.com, hotmail.con, yaho.com, stray spaces/dots. Returns the suggestion (or null) and which fixes applied. Free. Example: email 'sara@gmial.con'. Response: result with status (deliverable | risky | undeliverable | invalid | unknown), reason, score 0–100, the checks run, plus data_confidence, estimated_items[], sources[], data_version, warnings[] and a disclaimer. No logging of addresses.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
verify_emailFull check of one address: RFC syntax and normalisation, domain existence and MX records (incl.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.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Full check of one address: RFC syntax and normalisation, domain existence and MX records (incl. null-MX and implicit-MX), disposable-provider list (10k+ domains), role account, free-mail provider, typo suggestion; optional SMTP RCPT probe with catch-all detection and optional SPF/DMARC. Example: email 'john.doe@gmail.com', smtp_check false. Response: result with status (deliverable | risky | undeliverable | invalid | unknown), reason, score 0–100, the checks run, plus data_confidence, estimated_items[], sources[], data_version, warnings[] and a disclaimer. No logging of addresses.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
verify_emailsSame checks as verify_email for a list, run in parallel with per-domain DNS caching; returns per-address results, a summary by status, and `clean` (the deliverable ones).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.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Same checks as verify_email for a list, run in parallel with per-domain DNS caching; returns per-address results, a summary by status, and `clean` (the deliverable ones). Charged per unique address. Example: emails ['a@x.com','b@y.org'], smtp_check false. Response: result with status (deliverable | risky | undeliverable | invalid | unknown), reason, score 0–100, the checks run, plus data_confidence, estimated_items[], sources[], data_version, warnings[] and a disclaimer. No logging of addresses.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
Only reads 1Show 1 read-only tool
extract_emailsFind every address in a block of text or HTML (deduped by default).Reads private dataReads text others writeNo findings
Why it is in this group
- The description's first verb is "find": a word for reading.
What it can reach
- private-dataThe name "extract_emails" says "email": it reads mail.
- untrusted-inputThe name "extract_emails" says "email": it reads inbound email, which other people can write.
- untrusted-inputThe description's first sentence says "find" and "html": it reads web pages, which anyone can write.
Description, as the server wrote it Find every address in a block of text or HTML (deduped by default). Free. Pair with verify_emails. Response: result with status (deliverable | risky | undeliverable | invalid | unknown), reason, score 0–100, the checks run, plus data_confidence, estimated_items[], sources[], data_version, warnings[] and a disclaimer. No logging of addresses.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: 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.
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 write1
- 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.
Looked at Nov 15, 2026, 13:23 UTC, unchanged since Oct 31, 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
- 4
- 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 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://verify.noahsarch.tech/mcp: tools/list returned 5 tools to an anonymous client, including verify_email (write), verify_emails (write), domain_check (write), suggest_fix (write)
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.
Install
Pinned to version 0.1.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http email-verifier https://verify.noahsarch.tech/mcpclaude mcp add --transport http email-verifier https://verify.noahsarch.tech/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__email-verifier__extract_emails"
],
"ask": [
"mcp__email-verifier__verify_email",
"mcp__email-verifier__verify_emails",
"mcp__email-verifier__domain_check",
"mcp__email-verifier__suggest_fix"
],
"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-verifier. Review it before you use it.
Capability tags behind 1 rule
- mcp__email-verifier__extract_emails 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/tech.noahsarch/email-verifier/verify?hash=fe9ce9d512cde3f4cf4cdb863979b82a8f2f9a32320e330fd6d8bfb6530bd71d" | jq -e '.changed == false'Pinned hash fe9ce9d512cd, from Nov 13, 2026, 21:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/tech.noahsarch/email-verifier/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/tech.noahsarch/email-verifier)Source: MCP Registry. Synced Oct 31, 2026, 23:17 UTC.
Email Verifier MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Email Verifier MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Email Verifier MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Email Verifier 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 Email Verifier MCP server have?
- 5 tools: 4 write, 1 read. verify_email, verify_emails, domain_check, suggest_fix and extract_emails.
Does the Email Verifier MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Email Verifier MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Email Verifier MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.