Email x402 REST usage
Find email address for a person synchronously. Provide name + company or LinkedIn URL.
0.03 USDC per call
per call
← All services
View daily earnings, market cap, volume and coverage →
Emitd MCP Server
MCP server MCPtponnam · github.com/tponnam · Comms & Messaging
Price per call
—
published unit: unknown
Calls · 30d
—
not reported by any source
Value at list price · 30d
—
calls × published price — not settled revenue
Downloads · 30d
—
no package published — not measurable
Evidence
Endpoint verified by us
checked 2026-10-25
Daily market statistics
| Day · UTC | Earned | Gross volume | Refunds | Observed transfers | Market cap | Revenue coverage |
|---|---|---|---|---|---|---|
| 2026-10-25 | — | — | — | — | — | none |
| 2026-10-24 | — | — | — | — | — | none |
| 2026-10-23 | — | — | — | — | — | none |
| 2026-10-22 | — | — | — | — | — | none |
| 2026-10-21 | — | — | — | — | — | none |
| 2026-10-20 | — | — | — | — | — | none |
| 2026-10-19 | — | — | — | — | — | none |
View daily history → · UTC days; today's figures are partial.
What the provider says
Connect AI agents to Emitd email sending, message tracking, templates, and automations.
Quoted from Official MCP Registry · source record · read 2026-10-25
Facts and where they come from
- Price
- Price not published Not found
- Unit
- Not stated by the provider
- Protocol
- MCP · transport: streamable-http Provider claim
- Auth
- api key
- Endpoint
- https://mcp.emitd.com/mcp
- Source code
- https://github.com/tponnam/emitd-mcp-server
- Source
- Official MCP Registry · Provider-published registry data
- Last checked
- Endpoint called 2026-10-25
- First seen
- 2026-10-25
Payments and earnings
Verified earnings · 30d
Unknown
Measured days
0/30
Settled payments
—
Ledger computed
never
No settled payment on record. Earnings for this service are unknown — not zero.
MCP server
- Registry name
- com.emitd/emitd
- Version
- 1.0.1
- Protocol check
- Provider claim Listed in the official MCP Registry. We have not run an MCP handshake against it yet.
Provenance
One row per statement. “Verified” means we checked it ourselves and the finding is quoted. “Provider claim” means we read it in the provider's own record. “Not found” is a statement about our search, not proof of absence.
| Statement | Status | What we found | Source | Checked |
|---|---|---|---|---|
| Docs | Provider claim |
https://github.com/tponnam/emitd-mcp-server
EvidenceRepository im Registereintrag hinterlegt; Installation und Nutzung sind dort beschrieben. |
registry.modelcontextprotocol.io | 2026-10-25 |
| Endpoint | Provider claim |
https://mcp.emitd.com/mcp
EvidenceAls Remote-Endpunkt im Registereintrag genannt. |
registry.modelcontextprotocol.io | 2026-10-25 |
| Pricing | Not found |
EvidenceDas MCP-Register nennt keinen Preis. Wir haben am 2026-10-25 im Registereintrag und, soweit vorhanden, im Repository nach einer Preisangabe gesucht und keine gefunden. Das heißt nicht, dass die Nutzung kostenlos ist. |
registry.modelcontextprotocol.io | 2026-10-25 |
| Protocol | Provider claim |
MCP (streamable-http)
EvidenceDas Register führt den Eintrag als MCP-Server, Version 1.0.1. Transport: streamable-http. |
registry.modelcontextprotocol.io | 2026-10-25 |
| Provider | Provider claim |
tponnam
EvidenceIm official MCP Registry unter dem Namen "com.emitd/emitd" veröffentlicht; der Eintrag ist die Selbstauskunft des Anbieters, nicht unsere Prüfung. |
registry.modelcontextprotocol.io | 2026-10-25 |
| Reachability | Verified |
HTTP 405 · 540 ms
EvidenceEigene Anfrage am 2026-10-25 um 18:30 UTC an https://mcp.emitd.com/mcp (GET, ohne Anmeldung, ohne Bezahlung). Antwort: HTTP 405. |
mcp.emitd.com | 2026-10-25 |
Endpoint checks
| When | URL | Answer | Latency | Payment challenge |
|---|---|---|---|---|
| 2026-10-25 | https://mcp.emitd.com/mcp | HTTP 405 | 540 ms | — |
We call the documented URL once, unauthenticated and without paying. We never retry a payment challenge and never sign in.
Similar services
All of Comms & Messaging →DYOE Contact Extraction x402 REST usage
Extract public business emails, phone numbers, and social profiles from a website. Batch-safe contact enrichment for autonomous agents. Input: website URL. Returns structured JSON.
0.01 USDC per call
per call
Email validate x402 REST usage
Validate an email address: RFC 5322 syntax, MX records, 5,361 disposable domain detection, role-based address detection (35 patterns), free provider detection, and typo suggestion for common providers (gmial.com ? gmail....
0.0324 USDC per call
per call
Person profile x402 REST usage
Profile enrichment from a name and company, an email, a phone or a profile URL. Phone lookup is off by default. include_phone=true adds the per-person add-on on the pricing page for up to one person; no phone hit is guar...
0.001 USDC per call
per call
Chosen by category and by whether we have measured them, not by who pays us. A sponsored placement in this list is labelled as such.