Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

HideMail

REMOTE · HIDEMAIL.APP

Private email aliases that forward to your inbox: create, find, edit and turn aliases off or on.

Available components

+3 this week 82 Trust /100

Last scanned (18 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Communication

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security89
Transport & Reachability100
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1470 tokens (~86/item across 17 items; 17 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 20 Nov 26 +1
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 19 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 18 Nov 26 +1
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 17 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 16 Nov 26 +1
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 15 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 14 Nov 26 +1
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://hidemail.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=hidemail.app CN=WE1,O=Google Trust Services,C=US 26 Oct 2026 24 Jan 2027 ECDSA 256 ECDSA-SHA256 4a85fd812d418b9a1399c0aedd232e50
SANs: hidemail.app, *.hidemail.app
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of hidemail.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
hidemail.app. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="mcp", resource_metadata="https://hidemail.app/.well-known/oauth-protected-resource/mcp"

Bearer realm="mcp", resource_metadata="https://hidemail.app/.well-known/oauth-protected-resource/mcp"
Header Value
x-content-type-options nosniff
x-frame-options SAMEORIGIN

Protected resource metadata

Document https://hidemail.app/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://hidemail.app/mcp
Authorisation server https://hidemail.app

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://hidemail.app/mcp Verified 200
http (plaintext) http://hidemail.app/mcp HTTPS enforced 301 https://hidemail.app/mcp
MCP tools · 17 exposed · ~1,217 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
activate_alias ~52

Turns one of the signed-in user's aliases back on, so mail sent to it is forwarded to their inbox again.

NameTypeReqDescription
emailstringyesThe full alias address, for example "abc123@hidemail.app".

No output schema declared.

No examples provided.

add_custom_domain ~87

Adds 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.

NameTypeReqDescription
domainstringyesThe custom domain, for example "example.com".

No output schema declared.

No examples provided.

create_alias ~143

Creates 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.

NameTypeReqDescription
domainstring–Optional alias domain from list_alias_domains, for example "relay.hidemail.app". Leave it out to use the default alias domain.
notestring–Optional short note saying where the alias will be used, for example "Netflix sign-up".

No output schema declared.

No examples provided.

deactivate_alias ~59

Turns 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.

NameTypeReqDescription
emailstringyesThe full alias address, for example "abc123@hidemail.app".

No output schema declared.

No examples provided.

get_account ~55

Shows 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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_custom_domain_setup ~112

Shows 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.

NameTypeReqDescription
domainstringyesThe custom domain, for example "example.com".

No output schema declared.

No examples provided.

get_webhook ~34

Shows the webhook URL that receives a copy of every email arriving on the signed-in user's aliases, or that none is set.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_alias_domains ~47

Lists 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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_aliases ~130

Lists 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.

NameTypeReqDescription
pageinteger–Page number, starting at 1.
searchstring–Optional text to find in the alias address or note, 3 to 50 characters.
statusstring–Which aliases to return: "all", "active" (forwarding on) or "inactive" (turned off).

No output schema declared.

No examples provided.

list_custom_domains ~43

Lists the user's own domains added to HideMail with their setup status (provisioning, provisioning_failed, needs_mx, ready) and whether catch-all is on.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

remove_webhook ~40

Stops 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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

request_webhook ~94

Asks 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.

NameTypeReqDescription
urlstringyesThe https:// URL that should receive a copy of every incoming email, for example "https://hooks.example.com/hidemail".

No output schema declared.

No examples provided.

reset_default_alias_domain ~29

Switches new aliases back to the built-in HideMail domain. Existing aliases keep their address.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_custom_domain_catch_all ~100

Turns 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.

NameTypeReqDescription
domainstringyesThe custom domain, for example "example.com".
enabledbooleanyestrue to turn catch-all on, false to turn it off.

No output schema declared.

No examples provided.

set_default_alias_domain ~53

Chooses the domain new aliases are created on. Use a domain from list_alias_domains. Existing aliases keep their address.

NameTypeReqDescription
domainstringyesA domain from list_alias_domains, for example "example.com".

No output schema declared.

No examples provided.

update_alias_note ~76

Replaces the note of one of the signed-in user's aliases. The previous note is overwritten and cannot be recovered.

NameTypeReqDescription
emailstringyesThe full alias address, for example "abc123@hidemail.app".
notestringyesThe new note, 1 to 255 characters. Replaces the current note.

No output schema declared.

No examples provided.

verify_custom_domain ~63

Checks 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.

NameTypeReqDescription
domainstringyesThe custom domain, for example "example.com".

No output schema declared.

No examples provided.

Install

How do I install the HideMail MCP server?

HideMail is a hosted endpoint at https://hidemail.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · hidemail.app

# add to Claude Code
claude mcp add --transport http app-hidemail-hidemail 'https://hidemail.app/mcp'
Common questions

What is the HideMail MCP server?

HideMail is an MCP server listed in the public MCP registry as app.hidemail/hidemail. Private email aliases that forward to your inbox: create, find, edit and turn aliases off or on. This page covers its hosted endpoint (https://hidemail.app/mcp).

Is the HideMail MCP server safe to use?

HideMail scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the HideMail MCP server expose?

HideMail exposes 17 tools: create_alias, list_aliases, update_alias_note, activate_alias, deactivate_alias, and 12 more. Their descriptions and schemas cost roughly 1,217 tokens of context every time the server is loaded.

Does the HideMail MCP server require authentication?

Yes. HideMail asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the HideMail MCP server still maintained?

HideMail is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the HideMail MCP server?

VerifyMCP ran 13 checks on HideMail, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.