MCP.Market

Likelyread MCP server

online · 100% uptime
by likelyread.com·com.likelyread/likelyread·v1.0.0

Email open tracking for agents: add a pixel, register the send, read back who opened it

A97/100grade A
What users say
No reviews yet
Be the first
Safety scan
A97/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Likelyread yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Likelyread tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-10-25 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 518ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identityendpoint served from the registry-verified namespace domain8/10
Overall 97/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Likelyread compares

Against every graded Email MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
97/100
higher than 95% of 916 Email servers
Uptime
100%
of our recent checks; the typical remote Email server answers 100%
Response time
753 ms
faster than 15% of 609 Email servers

Install Likelyread in Claude Code, Cursor or VS Code

claude mcp add --transport http likelyread https://app.likelyread.com/mcp
Add to Cursor

What the publisher says

From the Likelyread repository's README, as published. We do not edit it. Read it on GitHub

likelyread

Open-source email open tracking for Gmail. It tells you when someone opens an email you sent, explains why each open counted, and gives you a small dashboard to follow your campaigns.

Two ways to use it:

  • Likelyread Cloud at app.likelyread.com: install the Chrome extension, sign in with Google, done. Free plan; Pro adds campaign analytics and full history. See docs/CLOUD.md.
  • Self-hosted: one small server (FastAPI + SQLite) behind Caddy, installed with one command. One token, every feature, nothing leaves your VPS. Instructions below.

How it works

  1. When you click Send in Gmail with tracking on, the extension appends a 1x1 invisible image (https://your-domain/p/.gif) to the email and registers the email with your server. Sending is never blocked or delayed.
  2. When the recipient's mail client loads the image, the server logs a hit.
  3. Hits are classified when you read them:
  • self: your own compose preview or your own view of the sent email (the extension tells the server, and also blocks the request in your browser);
  • prefetch: Apple Mail Privacy Protection loading images on delivery (bare Mozilla/5.0 user agent from Apple's network);
  • open: everything else.
  1. You see the result where you look:
  • in Gmail, next to the date of each tracked email you sent, when you open the conversation: one grey tick while nobody has opened it (Not opened yet, Seen by you only, Prefetch only), two red ticks once someone has (Opened ×2). Hover for when; click to open the email in the dashboard;
  • in the toolbar popup, the last 50 tracked emails with their status;
  • on the dashboard, everything (see below).

See SPEC.md for the full contract.

Setup

You need a small Linux server (Ubuntu or Debian, 512 MB of RAM is plenty) with ports 80 and 443 open.

1. Pick an address. Use a subdomain of a domain you own, for example t.yourcompany.com: add an A record pointing to the server's IP (on Cloudflare, set it to DNS only, grey cloud). No domain yet? The installer can use a free .sslip.io address to try it out. For real email use your own domain: spam filters trust it more, and it keeps working if you move servers.

2. Run one command on the server:

curl -fsSL https://raw.githubusercontent.com/Hugo-SEQUIER/likelyread/main/deploy/install.sh | sudo bash

It installs Docker if needed, asks for your address, creates a private token, gets an HTTPS certificate and starts everything in /opt/likelyread. At the end it prints your setup link:

https://t.yourcompany.com/#connect=<your token>

Treat it like a password. You can print it again any time with sudo bash /opt/likelyread/deploy/install.sh --show-link, and it is on the dashboard under Connect.

3. Connect the extension. Install the Chrome extension, open its settings, paste the setup link and click Save. Write an email in Gmail: the red eye next to Send means it is tracked, and after you send it a note at the bottom left says Tracked by Likelyread. To try it, send it to another address you can open, such as a second account or your phone: your own views never count, so an email you send yourself stays Seen by you only.

Get the extension from the Chrome Web Store. To run your own build instead: cd extension && npm install && npm run build, then in chrome://extensions turn on Developer mode, click Load unpacked and pick extension/dist.

4. Open the dashboard. Open the setup link in your browser: it signs you in.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Likelyread: common questions

Is Likelyread MCP server safe?
Yes, by our scan: it is graded A (97/100). Read the Likelyread safety report
How do I install Likelyread?
It runs remotely at app.likelyread.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Likelyread need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is Likelyread maintained?
The last commit was 11 days ago (2026-10-24). The latest release is v1.0.0.
Is Likelyread up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Likelyread?
Servers from other publishers that do the same job: Agenticmail MCP server, Imap MCP server and Openagentemail MCP server.
How does Likelyread compare with other Email MCP servers?
safety score 97/100 (higher than 95% of 916 Email servers); uptime 100% (of our recent checks; the typical remote Email server answers 100%); response time 753 ms (faster than 15% of 609 Email servers). Full comparison.

Alternatives to Likelyread

Same job from other publishers: the closest match first, then the best rated.

  • Agenticmail
    Real email and SMS for AI agents — send mail, receive verification codes, drive a real inbox.
    B
  • Imap
    IMAP/SMTP MCP server to search, read, organize, send, reply & forward email for AI assistants
    A
  • Openagentemail
    Unlimited agent mailboxes — create identities, read/wait for mail, extract OTPs, send email.
    B
  • Fluxmail
    Read, search, draft, send, and organize email through Gmail, Outlook, and IMAP/SMTP mailboxes.
    B
  • MCPEmails
    Never-stored live email: read, send and triage Gmail, Outlook / Microsoft 365, or any IMAP mailbox.
    A