Skip to content
MCPSTAMP
MCP server report

CacheBoost MCP server

com.cache-boost/cacheboost

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

Measured facts

Score
39F
Sign-in
API key or other
Tools listed
Behind sign-in
Protocol version
None returned
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Unverified Nothing failed, but initialize over Streamable HTTP, tools/list returns tools, inputSchema is an object schema, readOnlyHint or destructiveHint on every tool and Human-readable title on every tool could not run in a check without credentials.
ChatGPT app directory Not ready Blocked by Sign-in method the store supports (OAuth or none), Protected resource metadata (RFC 9728) and Authorization server metadata (RFC 8414 / OIDC).
Gemini Connected Apps Not ready Blocked by Sign-in method the store supports (OAuth or none) and Authorization server metadata (RFC 8414 / OIDC).
Official MCP Registry Unverified Nothing failed, but initialize over Streamable HTTP could not run in a check without credentials.

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

Fixes

4 checks to fix

  1. Fails

    Protected resource metadata (RFC 9728)

    auth_prm

    Blocks ChatGPT.

    Measured Not found: https://api.cache-boost.com/.well-known/oauth-protected-resource/mcp -> 404; https://api.cache-boost.com/.well-known/oauth-protected-resource -> 404

    Serve RFC 9728 metadata at /.well-known/oauth-protected-resource (plus the path-suffixed form) with "resource" and "authorization_servers".

  2. Fails

    Authorization server metadata (RFC 8414 / OIDC)

    auth_as_metadata

    Blocks ChatGPT and Gemini.

    Measured Not found: https://api.cache-boost.com/.well-known/oauth-authorization-server -> 404; https://api.cache-boost.com/.well-known/openid-configuration -> 404

    Serve RFC 8414 metadata at <issuer>/.well-known/oauth-authorization-server with authorization_endpoint, token_endpoint and response_types_supported ["code"].

  3. Fails

    Sign-in method the store supports (OAuth or none)

    auth_method

    Blocks ChatGPT and Gemini.

    Measured initialize: HTTP 401 and no working OAuth discovery: the server expects a credential such as an API key or static token

    ChatGPT and Gemini cannot send a static API key or token: add MCP OAuth (protected resource metadata and authorization server metadata), or serve the tools without auth. Claude accepts a static credential in a request header only in a beta

  4. Fails

    401 carries WWW-Authenticate resource_metadata

    auth_challenge

    Measured initialize: HTTP 401 without WWW-Authenticate

    On 401, send WWW-Authenticate: Bearer resource_metadata="<protected resource metadata URL>".

3 checks passed, 20 did not run

Passed. Served over HTTPS, GET answers SSE or 405, initialize latency.

Not run. Resource metadata "resource" equals the server URL, 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. These need an OAuth sign-in flow the check could not reach.

Not run. initialize over Streamable HTTP, Supported protocol version negotiated, JSON or SSE response Content-Type, JSON-RPC error for unknown method, serverInfo name and version, Server instructions, tools capability declared, 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, Tool descriptions. The tools sit behind sign-in, and the check runs without credentials.

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 CacheBoost

Markdown

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

HTML

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

About this server

Warm CDN and reverse-proxy caches: manage sites, run warms, read cache-hit stats.
Registry name
com.cache-boost/cacheboost
Remote URL
https://api.cache-boost.com/mcp
Version
0.1.0
Website
www.cache-boost.com/support/mcp/overview
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 F servers

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