io.github.berkayderin/nextscan

MCPcommunity
v1.0.1io.github.berkayderinUnknownUpdated 4mo agonpmGitHub

MCP server that scans Next.js projects and returns a compact summary

MCP server that scans Next.js projects and returns a compact summary. One tool call → full project overview. Without nextscan | With nextscan | Manual file-by-file exploration | Single call | Multiple tool calls to understand routes | Compact route tree with flags | Missing security issues | Hardcoded secrets + env leak detection | Unknown API coverage | Auth + validation status per endpoint |…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
4mo agoLast update
Package
Authorio.github.berkayderin
LicenseUnknown
Version1.0.1
Sourcemcp-registry
npm@berkayderin/nextscan
GitHubberkayderin/nextscan
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/25
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/10
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
—npm provenance (Sigstore)+0/5
→ Publish from GitHub Actions with the --provenance flag
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface1 tool · none privileged
Security scan✓ Cleanv1.0.1 · 20d ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

MCP server that scans Next.js projects and returns a compact summary. One tool call → full project overview. Without nextscan | With nextscan | Manual file-by-file exploration | Single call | Multiple tool calls to understand routes | Compact route tree with flags | Missing security issues | Hardcoded secrets + env leak detection | Unknown API coverage | Auth + validation status per endpoint | Schema guesswork | Prisma/Drizzle relation mapping | Parameter | Type | Required | Description | |…

Keywords
mcp