mailreveal.
Get started
A little more clarity after “send”

Give your emails
a life after send.

Add a tiny tracker to your signature. Turn email activity into a useful nudge for you, your CRM, or your favorite agent.

Create your signature
Signature mode needs no browser extension.
Just an HTML signature and a public tracking URL.
✳+
To Jamie at Fieldwork

Shall we pick this up?

Hi Jamie,

Here’s the idea we talked about. I’d love to hear what you think.

Speak soon,

A
Alex MorganCustomer success, Acmealex@acme.example
Ready when a signal arrives.Try the demo to see what happens
Your systems, in the loop.
Keep your email client.
MGmail
OOutlook
Apple Mail
HTML signatures
Image support varies by client.

A small addition.
A more connected inbox.

You already have a way of sending email.
MailReveal fits into it.

Make it yours.

Add your name, role, and links. Copy your signature into an HTML-capable email client.

Build a signature

Catch a little activity.

When the remote image loads, it appears in your history. Proxy and automated requests get clear labels.

Explore the sample workspace

Put it to work.

Send signed events to your CRM, check the API, or let an agent help you decide what happens next.

Connect a webhook

One signature, or one email?

Choose the right kind of signal for the job.

Set it once

The everyday signature

Reuse it across messages and supported clients. See aggregate activity for the signature, without connecting your mailbox.

Signature-level activityMake mine
Make it specific

The individual email tracker

Create a unique tracker for each message. Keep recipient, subject, and history together. Prepare via the app, API, or MCP.

Message-level historyTrack an email

An image load is a signal, not proof someone read your email. A reused signature can’t identify the message or recipient.

Hey agents.
You’re invited, too.

No clicking through dashboards. Request access, get your human’s approval, and connect with a scoped key.

  • Machine-readable onboarding at /agents.md
  • A key with only the permissions you need
  • REST and MCP, ready for your workflow
Read the agent guide
Owner-controlled workspace. No access until approved.
A friendly first handshake
curl https://mailreveal.com/api/v1/agent-requests \
  -H 'Content-Type: application/json' \
  -d '{"name":"My assistant",
       "purpose":"Prepare trackers and report activity"}'
201 · Request created
{
  "status": "pending",
  "code": "7A3D9C12",
  "approval_url": "…/app?tab=agents"
}
Example response. Keep your claim token private.
Your human approves. You claim. You’re connected.

A signal that
goes somewhere.

Keep email activity close to the work it belongs to. Build with a straightforward API, connect an MCP client, or let webhooks bring events to you.

OpenAPI schemaRequests, responses, permissionsAPI keys & MCPScoped keys and client setupSigned webhooksDurable delivery, retries, event IDs
{
  "mcpServers": {
    "mailreveal": {
      "url": "https://mailreveal.com/mcp",
      "headers": {
        "Authorization": "Bearer <your-scoped-key>"
      }
    }
  }
}
Use your scoped key. Credentials stay out of email signatures.

A few good questions.

Can I use this in my email signature?

Yes. Create a reusable HTML signature in MailReveal, copy it into your client’s signature editor, and test it. The reusable version reports aggregate signature activity. Use a unique email tracker when you need history for a specific message.

Does it work from my phone?

It depends on whether your mobile client preserves remote images in signatures. Test your actual app and account. For Gmail, you can also prepare a tracked draft in MailReveal and send it from the Gmail app. A Google connection alone doesn’t add trackers to every native Gmail email.

Is an image load the same as a read?

No. Mail proxies, privacy services, security scanners, previews, and the sender can load images. MailReveal labels observable sources and never claims a confirmed read or recipient identity. Image blocking and caching can also hide activity.

Can agents sign up without my password?

Yes. An agent creates an access request via the public API. You verify its request code and approve limited permissions in your workspace. The agent claims a key once and uses it for REST or MCP. It never needs your Google password or workspace owner token.

What do I need to run this?

MailReveal currently runs as one owner-controlled workspace. For recipients to load trackers, deploy it at a public HTTPS URL. Gmail sending needs Google OAuth setup; webhooks need an operator-approved destination host. You can start with signatures without connecting Gmail.

Keep sending.
Stay a little closer.

Create your signature