An agent can connect on its own if it already holds X_API_KEY.Remote endpoint behind a static API key or header. The registry never sees the value; the agent fills the placeholder.
tools.descriptions, tools.description_length, tools.schemas, tools.annotations, tools.directory_hints, tools.token_cost, tools.api_dumptool list unknown (behind auth, not probed, or empty)
stabilityn/a · weight 15
n/a
stability.changes, stability.rug_pulltool list unknown
dependenciesn/a · weight 15
n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package
Tool list unknown · checked 2026-10-19 10:52 UTC
Tool changes
No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
Inspect and operate Next.js Redis caches: health, tag state, SWR simulation, safe invalidation.
Official server.json
{
"name": "com.cache-boost/cacheboost",
"title": "CacheBoost",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://api.cache-boost.com/mcp",
"type": "streamable-http",
"headers": [
{
"name": "X-API-Key",
"isSecret": true,
"isRequired": true,
"description": "CacheBoost API key (cb_live_…), created under Profile → API Keys. Scopes are enforced per tool, so a read-only key can list sites and runs but cannot warm. Clients able to send a custom Authorization header may use `Authorization: Bearer <key>` instead."
}
]
}
],
"version": "0.1.0",
"websiteUrl": "https://www.cache-boost.com/support/mcp/overview",
"description": "Warm CDN and reverse-proxy caches: manage sites, run warms, read cache-hit stats."
}