fix_stale_cache — CrawlCheck MCP Tool
fix_stale_cache
(fix stale cache) is one of 23 tools on the
CrawlCheck
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call fix_stale_cache from your client
- Claude Code CrawlCheck fix_stale_cache run in your project directory
- Claude Desktop CrawlCheck fix_stale_cache ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor CrawlCheck fix_stale_cache ~/.cursor/mcp.json
- VS Code CrawlCheck fix_stale_cache .vscode/mcp.json
- Zed CrawlCheck fix_stale_cache ~/.config/zed/settings.json
- Windsurf CrawlCheck fix_stale_cache ~/.codeium/windsurf/mcp_config.json
- Cline CrawlCheck fix_stale_cache ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI CrawlCheck fix_stale_cache ~/.gemini/settings.json
- Grok CrawlCheck fix_stale_cache .mcp.json (in your project root)
- ChatGPT CrawlCheck fix_stale_cache Settings → Connectors → Advanced → Developer mode
- Claude.ai CrawlCheck fix_stale_cache Settings → Connectors → Add custom connector
- LangChain CrawlCheck fix_stale_cache pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http crawlcheck https://crawlcheck.io/mcpOther tools on this server
- scan_domain
- verify_crawler_log
- corpus_state
- resolve_robots
- draft_llms
- fix_robots
- fix_entitymap
- video_check
- video_channel
- video_site
- registry_lookup
- crawler_path
- public_counts
- telemetry
- fix_mostly_code
- fix_machine_chain
- explain_finding
- list_verified_capabilities
- machine_record
- resolve_domain
- preflight
- mcp_servers
This list was read from the server itself, by connecting to it and calling tools/list on 10 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.