MCP server health, State of MCP census
Emailens MCP
io.github.emailens/mcp
Email compatibility analysis across 15 clients — preview, audit, fix, diff, deliverability.
Checks
The exact rows akashi check io.github.emailens/mcp prints, from the 2026-07-02 census.
| Check | Status | Detail |
|---|---|---|
| registry status | pass | active |
| server.json valid | pass | validates against its declared JSON Schema |
| repo reachable | pass | exists |
| repo freshness | warn | no push in 91d |
| package npm | pass | published (0.4.1) |
| remote reachable | pass | HTTP 200 via initialize |
| MCP conformance | pass | initialize handshake ok |
| tools/list | pass | 7 tools: preview_email, analyze_email, audit_email, fix_email, list_clients, diff_emails, check_deliverability |
| at least one live entrypoint | pass | 3 alive |
| license present | pass | MIT |
Evidence
Packages
- npm @emailens/mcp · published(0.4.1)
Remote endpoints
- https://emailens.dev/api/mcp
streamable-http · reachable· HTTP 200· initialize_ok
7 tools: preview_email, analyze_email, audit_email, fix_email, list_clients, diff_emails, check_deliverability
server.json
validagainst its declared schema
One of 14559 servers in the 2026-07-02 State of MCP census: 11582 healthy (79.6%), 2212 degraded (15.2%), 596 dead (4.1%), 169 unknown (1.2%).
Verify it yourself
This page is a static read of one dated probe. Run the same check locally, any time, with no key:
$ akashi check io.github.emailens/mcpInstall Akashi - single Go binary, zero keys, MIT licensed.
Is this your server?
Claiming a server (an auto-refreshing badge and a verified publisher profile) is coming soon. Until then, embed the verified-on-date badge yourself with akashi check io.github.emailens/mcp --badge.
Open data, CC BY 4.0. How this census works - denominator, tiers, and what each check does.