An astronaut overseeing a futuristic data hub

Connect Context Cache Invalidation Detector to your AI

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Stop losing reasoning and instructions to aggressive prompt caching.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 3 capabilities

We ship only the actions that matter.

Capability set01 / 01

01-03

3 capabilities in this set.

Part of 3 available through Context Cache Invalidation Detector.

  1. 01

    Compute pillar checksums

    Generates unique SHA-256 fingerprints for the four pillars of your current context.

  2. 02

    Get continuity status

    Returns a health assessment of your session based on its current continuity score.

  3. 03

    Check context integrity

    Validates whether the current session context is still fully intact.

Real work

What teams actually run

01

Debugging Agent Drift

Identify why an agent suddenly stopped following a specific system instruction during a long conversation.

02

Validating Prompt Caching

Check if your caching strategy is accidentally stripping away the conversation summary or reasoning history.

03

Session Health Monitoring

Regularly poll the continuity status to ensure a complex task hasn't entered a Degraded state.

04

Context Integrity Audits

Use checksums to verify that the system prompt hasn't changed unexpectedly during a session.

One connector, every AI

Context Cache Invalidation Detector works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put Context Cache Invalidation Detector to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

896ms average. Fast in production.

Context Cache Invalidation Detector is checked daily against the live service.

Daily averagePeak 999ms
Oct 3Today
Fastest day
784ms
Slowest day
999ms
14-day trend
Improving-11%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 3 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Context Cache Invalidation Detector, so you can see the experience inside your AI.

It does not authenticate your account with Context Cache Invalidation Detector. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Context Cache Invalidation Detector Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_RiJdU9HeoyAsKSt0VdAENP1CWaSyOe4Igqj8jBJ7/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Context Cache Invalidation Detector capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "context-cache-invalidation-detector-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_RiJdU9HeoyAsKSt0VdAENP1CWaSyOe4Igqj8jBJ7/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Context Cache Invalidation Detector in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Context Cache Invalidation Detector owners hand off.

This MCP is built for developers and power users who rely on long-context AI agents for complex, multi-step reasoning tasks.

  • 01

    AI Engineers

    Debugging reasoning drift and instruction truncation in agentic workflows.

  • 02

    Prompt Engineers

    Verifying that system instructions remain active during aggressive prompt caching.

  • 03

    LLM Researchers

    Monitoring how session management affects the continuity of reasoning blocks.

FAQ

Questions Context Cache Invalidation Detector owners ask.

  • 01

    What are the Four Pillars of Context?

    The pillars are the System Prompt, CLAUDE_md Content, Conversation Summary, and the Last Reasoning Block.

  • 02

    How does this MCP detect context loss?

    It uses SHA-256 checksumming to create fingerprints of your context. If these fingerprints change unexpectedly, it signals that context has been lost or drifted.

  • 03

    What does a Degraded session status mean?

    A Degraded status means the continuity score has dropped, indicating that at least one context pillar has drifted or been lost.

  • 04

    Can I use this with Claude or Cursor?

    Yes, this MCP works with any MCP-compatible client, including Claude, Cursor, and Windsurf.

  • 05

    Why is prompt caching a problem?

    Aggressive prompt caching can sometimes truncate instructions or clear reasoning blocks to save space, which causes the agent to lose its place or ignore rules.

  • 06

    What is the purpose of the continuity score?

    The context_continuity_score represents the health of the session by calculating the ratio of matched checksums against the expected Four Pillars of Context.

  • 07

    How does it detect if reasoning was lost?

    It compares the hash of the lastReasoningBlock against the previously stored hash. If they do not match, it indicates the reasoning was cleared or altered.

  • 08

    Can I use this with Claude Desktop?

    Yes, this MCP server can be connected to Claude Desktop, Cursor, VS Code, Windsurf, and any other MCP-compatible client via Vinkius Edge.

Connect Context Cache Invalidation Detector to Claude, Cursor, ChatGPT & more