CacheBoost

com.cache-boostPublished by cache-boost.comOfficial publisherv0.1.0Updated Oct 24, 2026

Warm CDN and reverse-proxy caches: manage sites, run warms, read cache-hit stats.

VerifiedStreamable HTTPWeb executableCloud & Infrastructure

Overview

AI-generated overview

CacheBoost is a remote MCP server that lets an assistant manage CDN and reverse-proxy sites, run cache warms, and read cache-hit statistics.

What you can do
Manage sites: list and inspect the CDN and reverse-proxy sites in the account, and list their warm runs with per-tool scopes enforced by the API key. Run cache warms: trigger warming of cached content for a site. Read cache-hit statistics: retrieve cache-hit metrics for the sites in the account.
When to use it
Use it when an assistant should check or act on CDN and reverse-proxy cache state for sites managed in CacheBoost, for example listing sites and runs, starting a warm after a deploy, or reviewing cache-hit statistics.
Requirements
A remote streamable HTTP endpoint at api.cache-boost.com. A CacheBoost API key (cb_live_…) sent in the X-API-Key header, created under Profile → API Keys. The key's scopes determine which tools work; a read-only key can list sites and runs but cannot warm.
Before you install
The API key is a secret sent in the X-API-Key header; keep it out of logs and shared transcripts. Scopes are enforced per tool, so grant only what is needed. Warming changes cache state on live sites, so confirm before triggering warms. Site and run data is sent to CacheBoost's remote service.

Installation

In SourceWeft

  1. Open CacheBoost in the dashboard and add it to a workspace.
  2. Connect X-API-Key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.cache-boost%2Fcacheboost/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "cacheboost": {
      "type": "http",
      "url": "https://api.cache-boost.com/mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.0LatestSep 17, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.