HideMail
app.hidemail/hidemailVersion 1.1.1Private email aliases that forward to your inbox: create, find, edit and turn aliases off or on.
Status
Responds289 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 13:36 UTC
- Latency
- 289 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- 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://hidemail.app/mcpResponds289 msNo sign-in
Claude Code
claude mcp add --transport http hidemail https://hidemail.app/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: hidemail
Remote MCP server URL: https://hidemail.app/mcpCursor
{
"mcpServers": {
"hidemail": {
"url": "https://hidemail.app/mcp"
}
}
}VS Code
code --add-mcp '{"name":"hidemail","type":"http","url":"https://hidemail.app/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
17 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
activate_aliasTurns one of the signed-in user's aliases back on, so mail sent to it is forwarded to their inbox again. | No | No | Yes | No |
add_custom_domainAdds one of the user's own domains to HideMail and starts setting it up. The ownership TXT record from get_custom_domain_setup must be published first. Setup takes a few seconds; then publish the MX record and call verify_custom_domain. The free plan allows 1 custom domain, the paid plan 5. | No | No | No | Yes |
create_aliasCreates a new random email alias for the signed-in user that forwards to their inbox. Use when the user needs a private address for a website or service. The optional note describes where the alias is used. The optional domain must be one of the domains from list_alias_domains; without it the default alias domain is used. May return a plan-limit or rate-limit message instead of an alias. | No | No | No | No |
deactivate_aliasTurns one of the signed-in user's aliases off. Mail sent to it is blocked until it is turned back on with activate_alias. Nothing is deleted. | Yes | No | Yes | No |
get_accountShows the signed-in user's HideMail plan ("free" or "paid") and how many aliases they have out of the plan's limit. Use before creating several aliases to check there is room. Never returns the user's real email address. | No | Yes | Yes | No |
get_custom_domain_setupShows the DNS records a custom domain needs (an ownership TXT record and an MX record), whether each one is published yet, the MX hosts the domain uses now, and the setup status. Call it before add_custom_domain and again after changing DNS. If replaces_other_mail_provider is true, the domain already receives mail elsewhere: ask the user before changing its MX record, because all of that mail will go to HideMail instead. | No | Yes | Yes | Yes |
get_webhookShows the webhook URL that receives a copy of every email arriving on the signed-in user's aliases, or that none is set. | No | Yes | Yes | No |
list_alias_domainsLists the domains new aliases can be created on: the built-in HideMail domain and the user's custom domains that can receive mail. The one with is_default true is used for new aliases. | No | Yes | Yes | No |
list_aliasesLists the signed-in user's aliases, newest first, with their note, on/off status and how many emails each one forwarded or blocked. Use to find an alias by address or note, or to filter by status. Results are paginated, 50 per page. | No | Yes | Yes | No |
list_custom_domainsLists the user's own domains added to HideMail with their setup status (provisioning, provisioning_failed, needs_mx, ready) and whether catch-all is on. | No | Yes | Yes | No |
remove_webhookStops sending copies of incoming email to the signed-in user's webhook. Mail still reaches their inbox. Takes effect immediately; setting a webhook again needs email confirmation. | Yes | No | Yes | No |
request_webhookAsks to send a copy of every email arriving on the signed-in user's aliases to an https:// webhook URL. Nothing changes yet: the user gets a confirmation email and the webhook is set only after they confirm it there. Tell the user to check their inbox. | No | No | No | No |
reset_default_alias_domainSwitches new aliases back to the built-in HideMail domain. Existing aliases keep their address. | No | No | Yes | No |
set_custom_domain_catch_allTurns catch-all on or off for a verified custom domain. With catch-all on, mail to any address on the domain that has no alias yet creates that alias (paid plan only). With it off, such mail is dropped; existing aliases keep working either way. | Yes | No | Yes | No |
set_default_alias_domainChooses the domain new aliases are created on. Use a domain from list_alias_domains. Existing aliases keep their address. | No | No | Yes | No |
update_alias_noteReplaces the note of one of the signed-in user's aliases. The previous note is overwritten and cannot be recovered. | Yes | No | Yes | No |
verify_custom_domainChecks that the custom domain's MX record points at HideMail and, if so, starts receiving its mail. Once verified, the domain can be made the default with set_default_alias_domain. | No | No | Yes | Yes |
Details
- Registry status
- Active
- Published
- Oct 16, 2026
- Updated
- Oct 16, 2026
- Repository
- Not given
- Categories (suggested)
- CommunicationSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared