io.github.leejpsd/nextjs-cache-handler-mcp
NPM · @LEEJPSD/NEXTJS-CACHE-HANDLER-MCP · SCANNED AUG 3
Inspect and operate Next.js Redis caches: health, tag state, SWR simulation, safe invalidation.
Available components
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (102 of 106), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (102 of 106), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to leejpsd/nextjs-cache-handler). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 404 tokens (~57/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage78
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 33% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @leejpsd/nextjs-cache-handler-mcp
claude mcp add leejpsd-nextjs-cache-handler-mcp -- npx -y @leejpsd/nextjs-cache-handler-mcp
codex mcp add leejpsd-nextjs-cache-handler-mcp -- npx -y @leejpsd/nextjs-cache-handler-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"leejpsd-nextjs-cache-handler-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@leejpsd/nextjs-cache-handler-mcp"
],
"enabled": true
}
}
} openclaw mcp add leejpsd-nextjs-cache-handler-mcp --command npx --arg -y --arg @leejpsd/nextjs-cache-handler-mcp
mcp_servers:
leejpsd-nextjs-cache-handler-mcp:
command: "npx"
args: ["-y", "@leejpsd/nextjs-cache-handler-mcp"] {
"mcpServers": {
"leejpsd-nextjs-cache-handler-mcp": {
"command": "npx",
"args": [
"-y",
"@leejpsd/nextjs-cache-handler-mcp"
]
}
}
} 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.
- 2 Aug 26 73
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@leejpsd/[email protected]
Provenance verified
Ecosystem: npm · Outcome: verified
Reason: verified
- Source repo:
- leejpsd/nextjs-cache-handler
- Certificate issuer:
- https://token.actions.githubusercontent.com
- Certificate SAN:
- https://github.com/leejpsd/nextjs-cache-handler/.github/workflows/release.yml@refs/heads/main
- Rekor log index:
- 2319262915
- Predicate type:
- https://slsa.dev/provenance/v1
- Subject digest:
- sha512:377bb33a4c13d127f5f383def714ed36f0b53827ead96aae66a9d719084a9bf3c3333e518819db4f6eee394c3b19f30172077315408c96cee98af81b7
- Discovery method:
- attestation_endpoint
Dependencies 102 packages
102 packages in the resolved dependency tree · 102 deprecated · 30 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
cache_health ~29
Ping Redis and summarize cache key counts per layer/kind. First tool to run when debugging cache issues.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cache_inspect ~49
Decode a cache entry: kind, timestamps, tags, TTL, sizes, compression. Values are summarized, never dumped in full.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | Full Redis key of a cache entry |
No output schema declared.
No examples provided.
cache_search ~64
Scan cache keys by glob pattern (e.g. 'next-incremental:entry:*/blog*'). Returns up to `limit` keys.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | — |
| pattern | string | yes | Redis MATCH glob, e.g. next-cache:entry:* |
No output schema declared.
No examples provided.
explain_key ~29
Parse a Redis key into layer / kind / namespace / cache key.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | — |
No output schema declared.
No examples provided.
invalidate_tag ~87
Invalidate a tag across both layers. DRY-RUN by default: shows exactly what would be written/deleted. Pass confirm=true to execute. mode 'soft' = stale-while-revalidate (revalidateTag(tag,'max') semantics); 'hard' = delete entries now.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | — | — |
| mode | string | — | — |
| tag | string | yes | — |
No output schema declared.
No examples provided.
simulate_swr ~82
Given entry timing values, classify freshness the way the handler does (fresh / stale / expired) and explain what a read would do.
| Name | Type | Req | Description |
|---|---|---|---|
| expireSec | number | yes | 0 means 'never hard-expire' |
| nowMs | number | — | — |
| revalidateSec | number | yes | — |
| timestampMs | number | yes | entry.timestamp (ms epoch) |
No output schema declared.
No examples provided.
tag_state ~64
Show invalidation state for a tag across BOTH cache layers: the ISR tag state (stale/expired timestamps) and the 'use cache' tag-expiration marker. Answers 'is this tag invalidated right now, and since when?'
| Name | Type | Req | Description |
|---|---|---|---|
| tag | string | yes | — |
No output schema declared.
No examples provided.