InboxVet
com.inboxvet/email-verificationVersion 1.0.0Verify emails (syntax, MX, SMTP mailbox, catch-all), test email DNS and check Spamhaus blocklists.
Status
Sign-in required118 msReachable. It asks for authorization, so we did not look inside.- Last checked
- Nov 14, 2026, 14:01 UTC
- Latency
- 118 ms
- Remotes responding
- 1 of 1
- Sign-in
- OAuth sign-in
- Hosting
- EU hosting detected (detected, not a legal statement)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://inboxvet.com/api/mcpSign-in required118 msOAuth sign-in
Claude Code
This server asks for sign-in. Your client opens the sign-in when it connects.
claude mcp add --transport http email-verification https://inboxvet.com/api/mcp --header 'X-API-Key: <YOUR_X_API_KEY>'Replace <YOUR_X_API_KEY> before running.
Claude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: email-verification
Remote MCP server URL: https://inboxvet.com/api/mcp
This server expects the header X-API-Key.Cursor
{
"mcpServers": {
"email-verification": {
"url": "https://inboxvet.com/api/mcp",
"headers": {
"X-API-Key": "<YOUR_X_API_KEY>"
}
}
}
}Replace <YOUR_X_API_KEY> before running.
VS Code
code --add-mcp '{"name":"email-verification","type":"http","url":"https://inboxvet.com/api/mcp","headers":{"X-API-Key":"<YOUR_X_API_KEY>"}}'Replace <YOUR_X_API_KEY> before running.
Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
Tools are visible after sign-in; we do not look inside protected servers.
Details
- Registry status
- Active
- Published
- Oct 18, 2026
- Updated
- Oct 18, 2026
- Repository
- Not given
- Categories (suggested)
- SecuritySuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared