Email Verifier
REMOTE · VERIFY.NOAHSARCH.TECH
Verify emails: syntax, MX, disposable, role, typo fix, optional SMTP probe, SPF/DMARC.
Available components
Last scanned (1 hour ago)
Scores higher than 55% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Communication
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 Security63
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 997 tokens (~142/item across 7 items; 5 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 67
First indexed and scored.
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 5 Nov 2026 · Probed https://verify.noahsarch.tech/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=noahsarch.tech | CN=WE1,O=Google Trust Services,C=US | 15 Oct 2026 | 14 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 470026e1ea46ecc0e06d5a5a9df0965 |
| SANs: noahsarch.tech, *.noahsarch.tech | ||||||
| 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 verify.noahsarch.tech. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| tech. | present | 2185 | 13 | Verified |
| noahsarch.tech. | absent | 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://verify.noahsarch.tech/mcp | Verified | 200 | |
| http (plaintext) | http://verify.noahsarch.tech/mcp | Inconclusive | 406 |
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 →
domain_check Check a domain's mail setup ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain (or an address; the domain part is used). |
Structured output declared, but exposes no named fields.
No examples provided.
extract_emails Pull email addresses out of text ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dedupe | boolean | – | – |
| text | string | yes | Any text/HTML to pull addresses from. |
Structured output declared, but exposes no named fields.
No examples provided.
suggest_fix Suggest a correction for a mistyped address ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
verify_email Verify one email address ~207
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.
| Name | Type | Req | Description |
|---|---|---|---|
| check_policy | boolean | – | Also report whether the domain publishes SPF and DMARC. |
| string | yes | The address to verify. | |
| smtp_check | boolean | – | Also probe the mailbox with an SMTP RCPT TO handshake (no message is sent). Slower (1–8 s); some servers block it. |
Structured output declared, but exposes no named fields.
No examples provided.
verify_emails Verify up to 1,000 emails in one call ~199
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.
| Name | Type | Req | Description |
|---|---|---|---|
| check_policy | boolean | – | Report SPF/DMARC presence per domain. |
| dedupe | boolean | – | Drop case-insensitive duplicates before checking (duplicates are not charged). |
| emails | array | yes | Up to 1,000 addresses. |
| smtp_check | boolean | – | SMTP RCPT TO probe per mailbox (slower; some servers block it). |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Email Verifier MCP server?
Email Verifier is a hosted endpoint at https://verify.noahsarch.tech/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 · verify.noahsarch.tech
claude mcp add --transport http tech-noahsarch-email-verifier 'https://verify.noahsarch.tech/mcp'
What is the Email Verifier MCP server?
Email Verifier is an MCP server listed in the public MCP registry as tech.noahsarch/email-verifier. Verify emails: syntax, MX, disposable, role, typo fix, optional SMTP probe, SPF/DMARC. This page covers its hosted endpoint (https://verify.noahsarch.tech/mcp).
Is the Email Verifier MCP server safe to use?
Email Verifier scores 70 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 Email Verifier MCP server expose?
Email Verifier exposes 5 tools: verify_email, verify_emails, domain_check, extract_emails, suggest_fix. Their descriptions and schemas cost roughly 773 tokens of context every time the server is loaded.
Does the Email Verifier MCP server require authentication?
No. We connected to Email Verifier without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Email Verifier MCP server still maintained?
Email Verifier is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.