io.github.rog0x/cache
NPM · @ROG0X/MCP-CACHE-TOOLS
Cache headers, CDN, LRU simulation for AI agents
Available components
Last scanned (11 hours ago)
Scores higher than 75% of npm servers
Category Cloud Infrastructure
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 228 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 751 tokens (~150/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −1
- Stability: pass → 0.93 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Analysed npm/@rog0x/mcp-cache-tools@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_browser_cache ~80
Analyze what resources a page would cache in the browser. Determines which resources are cacheable, for how long, cache type (strong/heuristic/conditional), and estimates bandwidth savings on repeat visits.
| Name | Type | Req | Description |
|---|---|---|---|
| connectionSpeed | string | – | Assumed connection speed for time savings estimate |
| resources | array | yes | Array of page resources with their response headers |
No output schema declared.
No examples provided.
analyze_cache_headers ~199
Analyze HTTP cache headers (Cache-Control, ETag, Last-Modified, Expires, Vary). Grades the caching strategy and provides actionable improvement suggestions.
| Name | Type | Req | Description |
|---|---|---|---|
| cacheControl | string | – | Cache-Control header value, e.g. 'public, max-age=3600, stale-while-revalidate=60' |
| context | string | – | Type of resource for context-aware suggestions |
| etag | string | – | ETag header value, e.g. '"abc123"' or 'W/"weak-tag"' |
| expires | string | – | Expires header value, e.g. 'Thu, 01 Dec 2025 16:00:00 GMT' |
| lastModified | string | – | Last-Modified header value, e.g. 'Wed, 21 Oct 2024 07:28:00 GMT' |
| vary | string | – | Vary header value, e.g. 'Accept-Encoding, Accept-Language' |
No output schema declared.
No examples provided.
check_cdn_headers ~96
Analyze CDN response headers to detect which CDN is serving a resource (Cloudflare, Fastly, Akamai, CloudFront, Vercel, etc.), cache status (HIT/MISS), edge server, and POP location.
| Name | Type | Req | Description |
|---|---|---|---|
| headers | object | yes | HTTP response headers as key-value pairs. Include all headers for best detection accuracy. |
| url | string | – | The URL that was requested (for context in the report) |
No output schema declared.
No examples provided.
generate_cache_key ~258
Generate deterministic cache keys from various inputs: URL + params, request body hash, or composite keys. Supports TTL, versioning, namespacing, and outputs ready-to-use Redis/Memcached commands.
| Name | Type | Req | Description |
|---|---|---|---|
| algorithm | string | – | Hash algorithm |
| body | string | – | Request body for 'body' mode |
| contentType | string | – | Content-Type for 'body' mode |
| excludeParams | array | – | Exclude these query params (url mode) |
| includeParams | array | – | Only include these query params (url mode) |
| method | string | – | HTTP method for 'url' mode |
| mode | string | yes | Key generation mode: 'url' for URL-based, 'body' for request body hash, 'composite' for multi-part |
| namespace | string | – | Key namespace/prefix |
| parts | array | – | Array of key components for 'composite' mode |
| ttl | number | – | Time-to-live in seconds |
| url | string | – | URL for 'url' mode, e.g. 'https://api.example.com/users?page=2&sort=name' |
| version | string | – | Version tag for cache busting, e.g. '2.1' |
No output schema declared.
No examples provided.
simulate_cache ~118
Simulate cache behavior for a sequence of requests. Calculates hit rate, miss rate, and eviction count for LRU, LFU, FIFO, and TTL eviction strategies. Compare strategies side-by-side.
| Name | Type | Req | Description |
|---|---|---|---|
| capacity | number | yes | Maximum number of entries the cache can hold |
| requests | array | yes | Sequence of cache requests in order |
| showTimeline | boolean | – | Include step-by-step timeline in output |
| strategies | array | – | Which eviction strategies to simulate |
| ttl | number | – | Default TTL in seconds (for TTL strategy) |
No output schema declared.
No examples provided.
How do I install the io.github.rog0x/cache MCP server?
io.github.rog0x/cache runs locally as an npm package, launched with npx -y @rog0x/mcp-cache-tools. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @rog0x/mcp-cache-tools
claude mcp add rog0x-cache -- npx -y @rog0x/mcp-cache-tools
What is the io.github.rog0x/cache MCP server?
io.github.rog0x/cache is an MCP server listed in the public MCP registry as io.github.rog0x/cache. Cache headers, CDN, LRU simulation for AI agents. This page covers its npm package (@rog0x/mcp-cache-tools).
Is the io.github.rog0x/cache MCP server safe to use?
io.github.rog0x/cache scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.rog0x/cache MCP server expose?
io.github.rog0x/cache exposes 5 tools: analyze_cache_headers, generate_cache_key, simulate_cache, check_cdn_headers, analyze_browser_cache. Their descriptions and schemas cost roughly 751 tokens of context every time the server is loaded.
Is the io.github.rog0x/cache MCP server still maintained?
io.github.rog0x/cache is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.rog0x/cache MCP server under?
io.github.rog0x/cache declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.rog0x/cache MCP server?
VerifyMCP ran 16 checks on io.github.rog0x/cache, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.