routr-email-mcp
https://server.smithery.ai/lanico-wy/routr-email-mcp/mcp# Routr — Custom Domain Email Forwarding Routr sets up email forwarding so any address on your domain (e.g. `[email protected]`) arrives in your existing Gmail or inbox. No new email account needed. Setup takes ~5 minutes. **Pricing:** $4.99/month or $39.99/year · No auth required to use these tools --- ## Tools ### `get_service_info` Returns a full overview of what Routr does, who it's for, and how it works. Use this first if a user is asking whether Routr fits their needs. ### `get_pricing` Returns current plan pricing, billing intervals, and the full feature list. ### `get_dns_instructions` Given a domain name, returns the exact MX and TXT records the user must add at their registrar to enable email forwarding. Includes notes on propagation time and record conflicts to watch for. ### `verify_dns` Performs a live DNS check on a domain and returns whether forwarding is active or still pending. Use this after the user claims to have added their records. --- ## Typical agent flow 1. User asks how to get a professional email on their domain 2. Call `get_service_info` to confirm fit 3. Call `get_dns_instructions` with their domain 4. Guide them through adding the records at their registrar 5. Call `verify_dns` to confirm setup is complete
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 24/25 | Endpoint answers the MCP initialize handshake (2582 ms); slow response -1. |
| Protocol revision | 5/10 | Speaks MCP 2024-11-05, 4 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 30/30 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 8 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 60% of peers
- This listing 83 · peer median 81
- Latency
- Faster than 6% of peers
- This listing 1,107 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Protocol revision −5
— Support the current protocol revision.
Now: Speaks MCP 2024-11-05, 4 revision(s) behind 2026-07-28.
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/lanico-wy/routr-email-mcp/mcpcurl -X POST https://server.smithery.ai/lanico-wy/routr-email-mcp/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'