Checks if an email/domain is disposable (temp-mail). x402-metered per call.
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":"disposable-email-checker","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 |
|---|---|---|---|---|---|
| 2 h ago | mcp initialize | ok | 200 | 1048 ms | server disposable-email-checker-mcp 1.0.0 · protocol 2025-06-18 · 1 tools |
| 8 h ago | mcp initialize | ok | 200 | 492 ms | server disposable-email-checker-mcp 1.0.0 · protocol 2025-06-18 · 1 tools |
| 15 h ago | mcp initialize | ok | 200 | 720 ms | server disposable-email-checker-mcp 1.0.0 · protocol 2025-06-18 · 1 tools |
| 22 h ago | mcp initialize | ok | 200 | 649 ms | server disposable-email-checker-mcp 1.0.0 · protocol 2025-06-18 · 1 tools |
| 28 h ago | mcp initialize | ok | 200 | 615 ms | server disposable-email-checker-mcp 1.0.0 · protocol 2025-06-18 · 1 tools |
| 35 h ago | mcp initialize | ok | 200 | 700 ms | server disposable-email-checker-mcp 1.0.0 · protocol 2025-06-18 · 1 tools |
| 2 d ago | mcp initialize | ok | 200 | 675 ms | server disposable-email-checker-mcp 1.0.0 · protocol 2025-06-18 · 1 tools |
| 2 d ago | mcp initialize | ok | 200 | 714 ms | server disposable-email-checker-mcp 1.0.0 · protocol 2025-06-18 · 1 tools |
| 2 d ago | mcp initialize | ok | 200 | 973 ms | server disposable-email-checker-mcp 1.0.0 · protocol 2025-06-18 · 1 tools |
| 3 d ago | mcp initialize | ok | 200 | 460 ms | server disposable-email-checker-mcp 1.0.0 · protocol 2025-06-18 · 1 tools |
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.