MCP.Market

day3 MCP server

online · 100% uptime
by Mopra·io.github.Mopra/day3·v1.0.0·1 stars

Draft email campaigns in day3 from Claude Code, Cursor or VS Code as editable composer blocks.

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

full report

Adoption
Growing

1 stars

Reviews

Write one

Nobody has reviewed day3 yet.

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

day3 tools

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

Public scan report

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

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 591ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/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 day3 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
181 ms
faster than 70% of 609 Email servers
GitHub stars
1
more than 65% of 493 Email servers

Install day3 in Claude Code, Cursor or VS Code

claude mcp add --transport http day3 https://go.day3.app/api/mcp
Add to Cursor

What the publisher says

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

Day3

Marketing and transactional email, billed by sends. $1/mo. No contact tax, no marketing suite to learn.

day3.app

Source-available, not open source. This code is published for

transparency and reference. See LICENSE for terms.

This repository is the Day3 product itself: the app at go.day3.app, the public REST API, the webhook and MCP endpoints, and the worker that sends the mail.

What it does

Day3 is a deliberately small email tool for small SaaS teams. Send product updates and changelogs to your users, and send your app's transactional email (password resets, receipts, magic links), through one verified domain, one monthly allowance, and one place to see delivery.

per-send stats

  • Campaigns with a block composer, optional AI assist, scheduling, and

categories), CSV import, and hosted signup forms

  • Audiences with segments (saved filters), topics (subscription

with per-email delivery status

  • Transactional email over POST /v1/emails, Resend-compatible in shape,

published as immutable versions, unlimited on every tier

  • Automations: onboarding and lifecycle flows drawn on a node canvas,

one-click unsubscribe, automatic bounce and complaint suppression, account auto-pause on bad reputation

  • Deliverability by default: verified sending domains, double opt-in,

log of every email you ever sent

  • Metrics for deliverability, reputation and engagement, plus a searchable

Cursor or VS Code can draft a campaign that lands in Day3 as editable blocks

  • Public API v1, signed webhooks, and an MCP server so Claude Code,

audiences and send for real in sandbox mode. Paid plans buy the allowance to reach everyone else.

  • Billed on sends, not subscribers. Free accounts set up domains, build

PRODUCT.md is the canonical description of what Day3 is, what it costs, and how every feature behaves. Read it before the code.

Tech stack

Quick Links

Built by Pradsgaard Labs. Also from the same workshop: exit1.dev, uptime monitoring.

Local development

npm install

# Env: web tier + worker (see "Required environment variables" below)
cp .env.example .env.local
cp .env.worker.example .env.worker

# Database
npm run db:migrate     # forward-only, applies un-applied journal entries
npm run db:seed        # optional sample data

npm run dev            # Next.js on http://localhost:3000
npm run worker         # BullMQ worker, in a second terminal

Shortened. The full README is on GitHub.

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

day3: common questions

Is day3 MCP server safe?
Yes, by our scan: it is graded A (97/100). Read the day3 safety report
How do I install day3?
It runs remotely at go.day3.app. 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 day3 need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is day3 maintained?
The last commit was 23 days ago (2026-10-12). The latest release is v1.0.0.
Is day3 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 day3?
Servers from other publishers that do the same job: emailmd MCP server, Inbox Zero MCP server and Fluxmail MCP server. Compare all day3 alternatives.
How does day3 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 181 ms (faster than 70% of 609 Email servers). Full comparison.

Alternatives to day3

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

All day3 alternatives →
  • emailmd
    Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
    A
  • Inbox Zero
    Search Gmail and Outlook, save drafts, manage email rules, and view email stats.
    A
  • Fluxmail
    Read, search, draft, send, and organize email through Gmail, Outlook, and IMAP/SMTP mailboxes.
    B
  • Sendraven
    Email infrastructure for AI agents: send, read replies as threads, campaigns, per-key limits.
    B
  • Agent Email
    Local email connectivity for AI agents — read, draft, send, and organize Outlook mail via MCP
    A