Skip to content
MCPSTAMP
MCP server report

aeotool MCP server

com.everlange/mcp

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, Gemini and MCP Registry. Not ready for ChatGPT.

Measured facts

Score
94A
Sign-in
OAuth
Tools listed
36
Protocol version
2025-11-25
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Ready No blocking check failed.
ChatGPT app directory Not ready Blocked by Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT).
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

    Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT)

    tool_open_world

    Blocks ChatGPT.

    Measured 22/36 tools miss an explicit hint: aeo_list_sites, aeo_audit_status, aeo_report, aeo_improvements, aeo_generate and 17 more

    Set readOnlyHint, destructiveHint and openWorldHint to explicit true/false on every tool (OpenAI app review requires all three).

  2. Warning

    initialize latency

    latency

    Measured 1750 ms

    Bring initialize under 1.5 s: avoid cold starts and upstream calls in the handshake.

  3. Warning

    refresh_token grant advertised

    auth_refresh

    Measured grant_types_supported: ["authorization_code"]

    Issue refresh tokens and list "refresh_token" in grant_types_supported so users are not logged out hourly.

23 checks passed, 1 did not run

Passed. Served over HTTPS, initialize over Streamable HTTP, Supported protocol version negotiated, JSON or SSE response Content-Type, JSON-RPC error for unknown method, GET answers SSE or 405, 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), tools/list returns tools, inputSchema is an object schema, Tool names are valid and portable, readOnlyHint or destructiveHint on every tool, Human-readable title on every tool, Tool descriptions.

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 aeotool

Markdown

[![McpStamp score](https://www.mcpstamp.com/badge?url=https%3A%2F%2Feverlange.com%2Fapi%2Fmcp)](https://www.mcpstamp.com/r/com-everlange-mcp/)

HTML

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

About this server

Everlange: audit AEO on 67 criteria across 10 answer engines, apply fixes, prove the gain.
Registry name
com.everlange/mcp
Remote URL
https://everlange.com/api/mcp
Version
1.0.0
Website
everlange.com/mcp-agences
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