Mailing Engineer MCP Server

by mailing-engineer Your server? Claim it

answering

Mailing Engineer is answering right now. Last checked 3 min ago.

E-Commerce Email Marketing, AI Newsletter Studio, DNS Audit & AWS SES Deliverability MCP.

Uptime history 7 days of history

7 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

133 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Mailing Engineer every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp --transport http https://mailing-engineer.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://mailing-engineer.com/mcp

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://mailing-engineer.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mailing-engineer.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://mailing-engineer.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://mailing-engineer.com/mcp	streamable-http	sign-in	86 ms	3 min ago

Alternatives to Mailing Engineer

same job, measured the same way

xOmniMarket

by wjabrac

Search AI capabilities across AWS Marketplace and the Official MCP Registry.

7 tools answering

Kubernetes Manifest Audit

by unbearabledev

kube-linter audit for Kubernetes manifests — 63 checks: security, availability, RBAC, network.

answering

Solana MCP

by sylenzor

Read-only Solana MCP: rug-risk, bundle & deployer checks, live market, full audit. No keys.

66 installs/wk local only

Oldweb Diagnostics

by palthainon

Public DNS, HTTPS and deployment checks, plus offline email header and delivery-log tracing.

5 tools answering

Localstack

by giovanemartins

MCP server for LocalStack AWS services, enabling AI agents to interact with local AWS infra.

43 installs/wk local only

AWS IoT Core

by nagarjunr

MCP server for AWS IoT Core: device registry, shadows, jobs, rules, messaging.

83 installs/wk local only

CloudeIDE

by cloudeide

Deploy from your terminal, and give an AI coding agent the same abilities over MCP.

53 installs/wk local only

AWS MCP Server

by aws

A managed MCP server enabling AI agents to access AWS using docs, API calls, and SOP workflows.

local only

Mailing Engineer — questions

Answers built from our own checks of this server.

Why is there no tool list for Mailing Engineer?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Mailing Engineer working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 133 ms. The bar chart above shows every period we have measured.

How do I connect Mailing Engineer?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to Mailing Engineer?

No API key is involved. Mailing Engineer answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is Mailing Engineer?

It answers our handshake in 133 ms on average, which is faster than 86% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.