Atlas / MCP servers / jazelly / Next.js Router Analyzer

Next.js Router AnalyzerCAUTION

mcp/jazelly/next-js-router-analyzer

Help LLMs to understand your Next apps better

Verdict
CAUTION
Grade
B
Trust score
85 /100
Exposed tools
4 4r · 0w · 0d
Transport
sse · stdio
License
MIT
Stars
99
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

Demo

Features

  • get-routers-info

The Router Analyzer scans your Next.js app directory structure and extracts information about all API routes, including:

  • API paths
  • HTTP methods (GET, POST, PUT, DELETE, etc.)
  • Request parameters
  • Status codes
  • Request and response schemas

Installation

npm install next-mcp-server

Or if you're using pnpm:

pnpm add next-mcp-server

Usage

Command Line

You can run the mcp server directly:

npm run build
node dist/index.js

Docker

docker build -t mcp/next -f Dockerfile .
docker run mcp/next -d

For cursor usage, define a mcp.json under ~/.cursor or [projectDir]/.cursor

{
"mcpServers": {
"next.js": {
"url": "http://localhost:4857/sse"
}
}
}

The url here could vary based on your .env settings within the project.

Output

The tool generates detailed information about each route:

[
{
"filePath": "/path/to/your/app/api/test/route.ts",
"implementationPath": "/path/to/your/app/api/test/route.ts",
"apiPath": "/api/test",
"handlers": [
{
"method": "GET",
"path": "/api/test",
"functionSignature": "export async function GET(request: Request)",
"description": "Get test data",
"parameters": [],
"statusCodes": [200]
},
{
"method": "POST",
"path": "/api/test",
"functionSignature": "export async function POST(request: Request)",
"description": "Create test data",
"parameters": [],
"requestBodySchema": "{ name: string }",
"statusCodes": [201, 400]
}
]
}
]

Development

To run tests:

npm run test

To run the mcp server locally:

npm run build
node dist/index.js 

To run it from node_modules after npm i:

node node_modules/next-mcp-server/dist/index.js
Read from source at commit 16f2b4a3fdecOBSERVED · 2026-10-07
02

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.

claude-code
claude mcp add playground -- npx -y playground
claude-desktop
{
  "mcpServers": {
    "playground": {
      "command": "npx",
      "args": [
        "-y",
        "playground"
      ]
    }
  }
}
03

Exposed tools (4)

4 read · 0 write · 0 destructive.

ToolRiskDescription
BooksreadBooks and publications
ElectronicsreadElectronic devices and accessories
LaptopreadHigh-performance laptop
get_routers_inforeadGet Pages details in the Next.js app.
04

Trust audit

CAUTIONgrade B · trust 85/100 Install with care. The audit found things worth knowing before you trust its output.

LayerWhat it checksResult
L0Provenance & inventoryFAIL
L1Static analysis of the codePASS
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
none-observed
Network
declared (3 observation(s))
Shell
none-observed
Dependencies
not all pinned
Secrets in source
found

Findings (5)

HIGHHard-coded secrets · inv.env_committed · CWE-798, CWE-321
.env
.env
Why it matters. a real .env in the package
Fix. ship .env.example with placeholders only
LOWInventory / provenance · inv.hidden_file · CWE-1104
.env
.env
Why it matters. hidden member outside the usual dotfiles
Fix. review its purpose
LOWInventory / provenance · inv.hidden_file · CWE-1104
playground/.env.local
.env.local
Why it matters. hidden member outside the usual dotfiles
Fix. review its purpose
LOWSupply chain · supply.unpinned · CWE-829, CWE-1357
package.json
express, zod, zod-to-json-schema, @jest/globals, @types/express, @types/jest, @types/node, jest
Why it matters. 11 dependency range(s) float
Fix. pin exact versions or ship a lockfile
LOWSupply chain · supply.unpinned · CWE-829, CWE-1357
playground/package.json
next, react, react-dom, @types/node, @types/react, @types/react-dom, autoprefixer, postcss
Why it matters. 9 dependency range(s) float
Fix. pin exact versions or ship a lockfile

Gates applied: no_behavioural_pass.

Audited 2026-10-07 · audit v0.4.1 · source sha 16f2b4a3fdecfull audit observations/trust-audit/mcp-server/jazelly__next-js-router-analyzer.json · Report an issue / request a re-scan
05

Audit history

Every audit this server has had. A grade with a past is a grade somebody is still checking.

DateSourceVerdictGradeScoreChange
2026-10-0716f2b4a3fdecCAUTIONB85first audit
06

Questions

What is the Next.js Router Analyzer MCP server?

Help LLMs to understand your Next apps better

What tools does Next.js Router Analyzer expose?

4 in total: 4 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.

Is Next.js Router Analyzer safe to connect to an agent?

With care. The audit graded it B (85/100) and found 5 things worth knowing before you trust this server, listed below with the exact line each was found on.

What credentials does Next.js Router Analyzer need?

No credential environment variables were found in its source, so it appears to need none.

How does Next.js Router Analyzer run?

It speaks sse and stdio, so it runs as a local process your client starts. It is published on npm as playground.

How current is this page?

The grade is for one exact copy of the source (16f2b4a3fdec), read on 2026-10-07. The repository is watched and re-audited when it changes.

Advertisement