MCPSafe.io
RegistryThreatsMethodologyDocsPricingScanSign in
MCPSafe.io

Security checks for MCP servers — public packages and private repos, fast or deep.

Legal

Privacy PolicyCookie PolicyTerms of ServiceSecurity disclosure

Resources

State of MCP SecuritySupportSystem statusMade in Germany 🇩🇪

© 2026 MCPSafe. All rights reserved.

GDPR — Privacy Policy
← Registry
A

vercel-labs/mcp-for-next.js

vHEAD · Score 96 / 100 · github

$git clone https://github.com/mcp-for-next.js.git
Last scan: 7h agoTotal scans: 0Findings: 0
MCPSAFE · ATTESTED · MCPSAFE · ATTESTEDA2026-05-12ECEABCFE

Assessment

0Critical
0High
0Medium
0Low

No issues detected — safe to use.

Scan history · newest first

2 scans
  • Apubdeep126102c7c4c79e03a420vHEAD7h ago
  • Apubfastffa4ab6caa0bb6862245vca4a1f0cc97e7h ago

Open a report to view findings, evidence, and export PDF for security or audit review.

Severity distribution

No findings recorded.

Version history

VersionGradeScoreFindingsScanned
HEADA9607h ago
ca4a1f0cc97eA9607h ago

README badge · pinned to vHEAD

[![MCPSafe](https://api.mcpsafe.io/badge/github/vercel-labs/mcp-for-next.js.svg?version=HEAD)](https://mcpsafe.io/registry/github/vercel-labs/mcp-for-next.js)

Locks to vHEAD's grade — the badge in your README will keep showing the same result even when later versions are scanned.

Live status badge

[![MCPSafe](https://api.mcpsafe.io/badge/github/vercel-labs/mcp-for-next.js.svg)](https://mcpsafe.io/registry/github/vercel-labs/mcp-for-next.js)

Auto-updates to the latest scanned version. Use for dashboards or status pages — not for release READMEs.