Skip to content
MCPSTAMP
MCP server report

Cooper Email MCP server

com.cooperemail/cooper-email

We checked this server on 2 November 2026 with McpStamp Check engine 1.2.0. It scored 94 of 100 (grade A), higher than 70.5% of the 33,003 registry servers that responded over HTTPS that day. Ready for Claude, ChatGPT, Gemini and MCP Registry.

Measured facts

Score
94A
Sign-in
OAuth
Tools listed
100
Protocol version
2025-03-26
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Ready No blocking check failed.
ChatGPT app directory Ready No blocking check failed.
Gemini Connected Apps Ready No blocking check failed.
Official MCP Registry Ready No blocking check failed.

MCP Registry ready means a valid public remote for the registry, not that the server is listed in a store.

Fixes

3 checks to fix

  1. Fails

    GET answers SSE or 405

    get_stream

    Measured HTTP 200 application/json

    Return HTTP 405 Method Not Allowed on GET (or a text/event-stream), not a page or 404.

  2. Warning

    Supported protocol version negotiated

    protocol_version

    Measured Negotiated 2025-03-26

    Support protocol version 2025-11-25 (or 2025-06-18) and echo it back in initialize.

  3. Warning

    Tool descriptions

    tool_descriptions

    Measured 7 over 2000 chars: cooper_onboard, cooper_create_inbox, cooper_send_message, cooper_add_domain, cooper_update_inbox and 2 more

    Keep each tool description between 60 and 2000 characters: when to use it, what it returns, key limits.

23 checks passed, 1 did not run

Passed. Served over HTTPS, initialize over Streamable HTTP, JSON or SSE response Content-Type, JSON-RPC error for unknown method, initialize latency, serverInfo name and version, Server instructions, tools capability declared, Sign-in method the store supports (OAuth or none), Protected resource metadata (RFC 9728), Resource metadata "resource" equals the server URL, Authorization server metadata (RFC 8414 / OIDC), First metadata URL Gemini tries answers 200 with the required fields, issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT), PKCE S256 advertised, Client registration (DCR or Client ID Metadata Documents), refresh_token grant advertised, tools/list returns tools, inputSchema is an object schema, Tool names are valid and portable, readOnlyHint or destructiveHint on every tool, Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT), Human-readable title on every tool.

Not run. 401 carries WWW-Authenticate resource_metadata. These need an OAuth sign-in flow the check could not reach.

Run a fresh check

This page is the 2 November 2026 snapshot. If you maintain this server and have shipped fixes since then, re-check it. The live check and the badge show the current result, and the next snapshot will pick up the change.

Re-check now

Badge

README badge

The badge shows the latest score for this URL and links to this report.

McpStamp score for Cooper Email

Markdown

[![McpStamp score](https://www.mcpstamp.com/badge?url=https%3A%2F%2Fcooperemail.com%2Fmcp)](https://www.mcpstamp.com/r/com-cooperemail-cooper-email/)

HTML

<a href="https://www.mcpstamp.com/r/com-cooperemail-cooper-email/"><img src="https://www.mcpstamp.com/badge?url=https%3A%2F%2Fcooperemail.com%2Fmcp" alt="McpStamp score" height="20"></a>
Registry entry

About this server

Email inboxes for AI agents: send, receive, search, drafts with owner approval, and webhooks.
Registry name
com.cooperemail/cooper-email
Remote URL
https://cooperemail.com/mcp
Version
1.4.0
Source
github.com/cooper-email/cooper-email
Website
cooperemail.com
Checked
2 November 2026, engine 1.2.0, no credentials

The description above is the server's own text from the official MCP Registry. If a result looks wrong, run a fresh check and email support@zovo.one with the report link.

More grade A servers

All grade A servers · All server reports · State of MCP readiness, November 2026