# HideMail (remote · hidemail.app)

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

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `hidemail.app`: 82/100 (this document), [markdown](https://verifymcp.io/servers/app-hidemail-hidemail/hidemail.md), [page](https://verifymcp.io/servers/app-hidemail-hidemail/hidemail)

## Channel facts

- Endpoint: `https://hidemail.app/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.1.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1470 tokens (~86/item across 17 items; 17 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

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

### Claude

```bash
claude mcp add --transport http app-hidemail-hidemail 'https://hidemail.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-hidemail-hidemail": {
      "url": "https://hidemail.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-hidemail-hidemail": {
      "type": "http",
      "url": "https://hidemail.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-hidemail-hidemail]
url = "https://hidemail.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-hidemail-hidemail": {
      "type": "remote",
      "url": "https://hidemail.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-hidemail-hidemail --url 'https://hidemail.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-hidemail-hidemail:
    url: "https://hidemail.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-hidemail-hidemail": {
      "Transport": "http",
      "Url": "https://hidemail.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-hidemail-hidemail -t streamable-http -u 'https://hidemail.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-hidemail-hidemail": {
      "type": "http",
      "url": "https://hidemail.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 82, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-20 (score 82, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-19 (score 81, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-18 (score 81, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-17 (score 80, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-16 (score 80, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-15 (score 79, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-14 (score 79, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

## MCP tools (17)

### `create_alias` (~143 tokens)

Create alias

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.

Input parameters:

- `domain` (string): Optional alias domain from list_alias_domains, for example "relay.hidemail.app". Leave it out to use the default alias domain.
- `note` (string): Optional short note saying where the alias will be used, for example "Netflix sign-up".

### `list_aliases` (~130 tokens)

List aliases

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.

Input parameters:

- `page` (integer): Page number, starting at 1.
- `search` (string): Optional text to find in the alias address or note, 3 to 50 characters.
- `status` (string): Which aliases to return: "all", "active" (forwarding on) or "inactive" (turned off).

### `update_alias_note` (~76 tokens)

Update alias note

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

Input parameters:

- `email` (string, required): The full alias address, for example "abc123@hidemail.app".
- `note` (string, required): The new note, 1 to 255 characters. Replaces the current note.

### `activate_alias` (~52 tokens)

Turn alias on

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

Input parameters:

- `email` (string, required): The full alias address, for example "abc123@hidemail.app".

### `deactivate_alias` (~59 tokens)

Turn alias off

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.

Input parameters:

- `email` (string, required): The full alias address, for example "abc123@hidemail.app".

### `get_account` (~55 tokens)

Show account plan

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.

### `get_webhook` (~34 tokens)

Show webhook

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

### `request_webhook` (~94 tokens)

Request webhook

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.

Input parameters:

- `url` (string, required): The https:// URL that should receive a copy of every incoming email, for example "https://hooks.example.com/hidemail".

### `remove_webhook` (~40 tokens)

Remove webhook

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.

### `list_alias_domains` (~47 tokens)

List alias domains

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.

### `set_default_alias_domain` (~53 tokens)

Set default alias domain

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

Input parameters:

- `domain` (string, required): A domain from list_alias_domains, for example "example.com".

### `reset_default_alias_domain` (~29 tokens)

Reset default alias domain

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

### `list_custom_domains` (~43 tokens)

List custom domains

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.

### `get_custom_domain_setup` (~112 tokens)

Get custom domain setup

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.

Input parameters:

- `domain` (string, required): The custom domain, for example "example.com".

### `add_custom_domain` (~87 tokens)

Add custom domain

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.

Input parameters:

- `domain` (string, required): The custom domain, for example "example.com".

### `verify_custom_domain` (~63 tokens)

Verify custom domain

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.

Input parameters:

- `domain` (string, required): The custom domain, for example "example.com".

### `set_custom_domain_catch_all` (~100 tokens)

Turn catch-all on or off

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.

Input parameters:

- `domain` (string, required): The custom domain, for example "example.com".
- `enabled` (boolean, required): true to turn catch-all on, false to turn it off.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-hidemail-hidemail/hidemail#diagnostics

## Score history

- 2026-11-21: 82
- 2026-11-20: 82
- 2026-11-19: 81
- 2026-11-18: 81
- 2026-11-17: 80
- 2026-11-16: 80
- 2026-11-15: 79
- 2026-11-14: 79
- 2026-11-13: 78
- 2026-11-12: 78
- 2026-11-11: 36
- 2026-11-10: 36
- 2026-11-09: 36
- 2026-11-08: 36
- 2026-11-07: 36
- 2026-11-06: 36
- 2026-11-05: 36
- 2026-11-04: 36
- 2026-11-03: 36
- 2026-11-02: 36
- 2026-11-01: 36
- 2026-10-31: 36
- 2026-10-30: 36
- 2026-10-29: 36
- 2026-10-28: 36
- 2026-10-27: 36
- 2026-10-26: 36
- 2026-10-25: 36
- 2026-10-24: 36
- 2026-10-23: 36

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

## Links

- Remote endpoint: https://hidemail.app/mcp
- Website: https://hidemail.app/support
- Changelog RSS feed: https://verifymcp.io/servers/app-hidemail-hidemail/hidemail.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-hidemail-hidemail/hidemail/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/app-hidemail-hidemail/hidemail.json
- HTML version of this page: https://verifymcp.io/servers/app-hidemail-hidemail/hidemail
