dev.multimail/mcp-server MCP server

Checked 2026-09-07. Alive: yes. Handshake: gated.

Category: communication. API and field schema.

Facts
idmultimail-dev--mcp-server
namedev.multimail/mcp-server
registry_namedev.multimail/mcp-server
repo_urlhttps://github.com/multimail-dev/mcp-server
endpoint_urlhttps://mcp.multimail.dev/mcp
transportmixed
aliveyes
liveness_reasonnot available
check_reachableyes
check_recent_commityes
check_installableyes
handshake_statusgated
handshake_checked_at2026-09-07T18:08:32Z
handshake_protocol_versionnot available
handshake_auth_hintBearer realm="OAuth", resource_metadata="https://mcp.multimail.dev/.well-known/oauth-protected-resource", error="invalid_token", error_description="Missing or invalid access token"
handshake_auth_discoverableresource_metadata
handshake_failure_layernone
handshake_latency_ms1310
handshake_tools_statenot available
handshake_tool_countnot available
maintenance_statusslow
last_commit_at2026-06-12T01:49:10Z
categorycommunication
license_spdxMIT
How to install or connect

Connect your MCP client to https://mcp.multimail.dev/mcp.

What the checks mean

alive combines the applicable repository, package, and endpoint checks. A null result is not verifiable, not a failure. The MCP handshake is a separate structural probe and is not a security audit. Read the methodology.