_ registry / mcp streamable-http · checked 1h ago

HideMail

https://hidemail.app

Registry code: 320cfee2f604b6ea

api record

HideMail gives the user private email aliases. Each alias is a random address that forwards mail to the user's real inbox, so they can sign up for websites without sharing their real address. An alias that is turned off blocks its mail until it is turned back on.

The tools only act on the signed-in user's own account. After creating an alias, show the new address on its own line in a code block so the user can copy it.

endpoint
https://hidemail.app/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is HideMail live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is HideMail free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does HideMail have?
17 tools: set_default_alias_domain, list_alias_domains, reset_default_alias_domain, get_account, get_webhook, create_alias, list_aliases, update_alias_note, ….
Is HideMail safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
255ms

last good check

priced tools
0

of 17 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 17 tools
17 auth-required 17 of 17 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • set_default_alias_domain auth-required never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "maxLength": 255,
      "description": "A domain from list_alias_domains, for example \"example.com\"."
    }
  }
}
    arguments 13 lines
  • list_alias_domains auth-required 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • reset_default_alias_domain auth-required never probed

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_account auth-required 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_webhook auth-required 1h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • create_alias auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "note": {
      "type": "string",
      "maxLength": 200,
      "description": "Optional short note saying where the alias will be used, for example \"Netflix sign-up\"."
    },
    "domain": {
      "type": "string",
      "description": "Optional alias domain from list_alias_domains, for example \"relay.hidemail.app\". Leave it out to use the default alias domain."
    }
  }
}
    arguments 14 lines
  • list_aliases auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "page": {
      "type": "integer",
      "default": 1,
      "minimum": 1,
      "description": "Page number, starting at 1."
    },
    "search": {
      "type": "string",
      "maxLength": 50,
      "minLength": 3,
      "description": "Optional text to find in the alias address or note, 3 to 50 characters."
    },
    "status": {
      "enum": [
        "all",
        "active",
        "inactive"
      ],
      "type": "string",
      "default": "all",
      "description": "Which aliases to return: \"all\", \"active\" (forwarding on) or \"inactive\" (turned off)."
    }
  }
}
    arguments 27 lines
  • update_alias_note auth-required never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "email",
    "note"
  ],
  "properties": {
    "note": {
      "type": "string",
      "maxLength": 255,
      "minLength": 1,
      "description": "The new note, 1 to 255 characters. Replaces the current note."
    },
    "email": {
      "type": "string",
      "description": "The full alias address, for example \"[email protected]\"."
    }
  }
}
    arguments 19 lines
  • activate_alias auth-required never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "email"
  ],
  "properties": {
    "email": {
      "type": "string",
      "description": "The full alias address, for example \"[email protected]\"."
    }
  }
}
    arguments 12 lines
  • deactivate_alias auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "email"
  ],
  "properties": {
    "email": {
      "type": "string",
      "description": "The full alias address, for example \"[email protected]\"."
    }
  }
}
    arguments 12 lines
  • request_webhook auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "maxLength": 255,
      "description": "The https:// URL that should receive a copy of every incoming email, for example \"https://hooks.example.com/hidemail\"."
    }
  }
}
    arguments 13 lines
  • remove_webhook auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • list_custom_domains auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_custom_domain_setup auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "maxLength": 255,
      "description": "The custom domain, for example \"example.com\"."
    }
  }
}
    arguments 13 lines
  • add_custom_domain auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "maxLength": 255,
      "description": "The custom domain, for example \"example.com\"."
    }
  }
}
    arguments 13 lines
  • verify_custom_domain auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "maxLength": 255,
      "description": "The custom domain, for example \"example.com\"."
    }
  }
}
    arguments 13 lines
  • set_custom_domain_catch_all auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain",
    "enabled"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "maxLength": 255,
      "description": "The custom domain, for example \"example.com\"."
    },
    "enabled": {
      "type": "boolean",
      "description": "true to turn catch-all on, false to turn it off."
    }
  }
}
    arguments 18 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 320cfee2f604b6ea.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/320cfee2f604b6ea/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/320cfee2f604b6ea/badge.svg)](https://brick.blue/agent/320cfee2f604b6ea?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.