nextjs-cache-handler-mcp
io.github.leejpsd/nextjs-cache-handler-mcp
About nextjs-cache-handler-mcp
nextjs-cache-handler-mcp is an MCP server published by the GitHub account leejpsd. Inspect and operate Next.js Redis caches: health, tag state, SWR simulation, safe invalidation.
It runs on your own machine: your AI client starts it from the npm package @leejpsd/nextjs-cache-handler-mcp at version 0.1.2.
It asks for one secret: REDIS_URL. Give it a key with the least access that still works.
Version 0.1.2 was published on 2 August 2026, and the source code is public, so you can read it before installing.
Written from the registry entry. 9 automated checks on the registry entry and the package code: 7 pass, 0 warn, 0 fail, 2 info. How we check.
What it asks for
| Variable | Required | Secret | Description |
|---|---|---|---|
REDIS_URL | Yes | Yes | Redis connection string the cache handler uses |
DEPLOYMENT_VERSION | No | No | Deploy namespace (recommended) |
HASH_TAG | No | No | Set 'true' when handlers use hashTag: true (Redis Cluster) |
Checks
| Check | Result | Detail |
|---|---|---|
| Source repository linked | Pass | https://github.com/leejpsd/nextjs-cache-handler |
| Version pinned | Pass | Every package has an explicit version |
| Secrets requested | Info | Asks for 1 secret: REDIS_URL |
| Known package registry | Pass | All packages come from npm, PyPI, OCI, NuGet or MCPB |
| Namespace ownership | Info | Name verified via GitHub account leejpsd |
| Registry text aimed at the AI | Pass | Description and settings contain no hidden characters or instructions to the AI |
| Install scripts | Pass | @leejpsd/nextjs-cache-handler-mcp@0.1.2 runs nothing at install |
| Code red flags | Pass | Read 3 files in @leejpsd/nextjs-cache-handler-mcp@0.1.2: no obfuscation, encoded execution, credential reads or data-collection endpoints found |
| Text aimed at the AI | Pass | No hidden characters or instructions to the AI in 3 files, including comments and the README |
Popularity & health: 55 / 100
Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.
2 forks, 10 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.
What people say
No Hacker News threads link to its source code.
Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.
Facts
| Registry name | io.github.leejpsd/nextjs-cache-handler-mcp |
|---|---|
| Publisher | GitHub account leejpsd |
| How the name is verified | Name verified via GitHub account leejpsd. The registry ties the name prefix to that account or domain; it does not check the code. |
| Type | Local: runs on your machine from a package |
| Packages | npm @leejpsd/nextjs-cache-handler-mcp 0.1.2 (stdio) |
| Version | 0.1.2 |
| Published | |
| Last updated | |
| Source repository | https://github.com/leejpsd/nextjs-cache-handler |
| Website | None linked |
| Category | Databases & data (assigned by keyword rule, not by hand) |
Related servers in Databases & data
- sentinal-mcp7/7Redis health, BullMQ queue monitoring, memory analysis, and slow…
- google-health-mcp7/7MCP server for the Google Health API, with a local SQLite cache and…
- withings-mcp7/7MCP server for the Withings Health API with OAuth, local SQLite…
- mcp3/4Real-time Kubernetes network traffic visibility and API analysis…
- quarry6/7Safety-railed database access: Postgres, MySQL, SQLite, Redis.…
briq3/3Give your agent its own cloud: Postgres, Redis, a sandbox or any…