Verify email addresses: syntax, MX, disposable, role, SMTP mailbox, catch-all and typo checks.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"emailverify-by-techforce-global","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Not distributed through a package registry we index.
| when | check | result | http | latency | detail |
|---|---|---|---|---|---|
| 3 h ago | mcp initialize | failed | — | — | timeout |
| 11 h ago | mcp initialize | ok | 200 | 135 ms | server emailverify 1.0.0 · protocol 2025-06-18 · 2 tools |
| 20 h ago | mcp initialize | ok | 200 | 154 ms | server emailverify 1.0.0 · protocol 2025-06-18 · 2 tools |
| 28 h ago | mcp initialize | ok | 200 | 135 ms | server emailverify 1.0.0 · protocol 2025-06-18 · 2 tools |
| 2 d ago | mcp initialize | ok | 200 | 137 ms | server emailverify 1.0.0 · protocol 2025-06-18 · 2 tools |
| 2 d ago | mcp initialize | ok | 200 | 135 ms | server emailverify 1.0.0 · protocol 2025-06-18 · 2 tools |
| 2 d ago | mcp initialize | ok | 200 | 137 ms | server emailverify 1.0.0 · protocol 2025-06-18 · 2 tools |
| 3 d ago | mcp initialize | ok | 200 | 139 ms | server emailverify 1.0.0 · protocol 2025-06-18 · 2 tools |
| 3 d ago | mcp initialize | ok | 200 | 137 ms | server emailverify 1.0.0 · protocol 2025-06-18 · 2 tools |
| 3 d ago | mcp initialize | ok | 200 | 136 ms | server emailverify 1.0.0 · protocol 2025-06-18 · 2 tools |
No hidden text found in the tool definitions.
Text a person reading a tool definition does not see and a model does. Invisible characters can be pasted in by accident; this says what is there, not why. Covers tools only, not prompts or resources.
Attributed to the source that supplied each field. Treated as claims, not facts.
No long description beyond the summary.
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.