Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Midnight + Next.js MCP

NPM · MIDNIGHT-NEXTJS-MCP

Unified MCP server for Midnight blockchain development and Next.js dApps.

Available components

npm · midnight-nextjs-mcp 31
0 this week 31 Trust /100

Last scanned (1 hour ago)

Scores higher than 4% of npm servers

Category Crypto and Web3

Trust breakdown (7 categories)

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 → Why this is hard to score →

Supply Chain Security90
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.24.3, reached via next-devtools-mcp > @modelcontextprotocol/sdk. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 47 of 188 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency18
Schema Quality & AI Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Changelog

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.

  • 5 Nov 26 0
    • CVE-2026-111771 affects this package: high ▼ security
    • GHSA-f897-62hf-6gxq affects this package: high ▼ security
    • CVE-2026-109924 affects this package: high ▼ security
    • CVE-2026-111769 affects this package: high ▼ security
    • CVE-2026-109829 affects this package: high ▼ security
    • CVE-2026-84933 affects this package: high ▼ security
    • CVE-2026-25536 affects this package: high ▼ security
    • CVE-2026-111767 affects this package: high ▼ security
    • CVE-2026-11525 affects this package: high ▼ security
    • CVE-2026-1527 affects this package: high ▼ security
    • CVE-2026-13697 affects this package: high ▼ security
    • CVE-2026-18149 affects this package: high ▼ security
    • CVE-2026-109383 affects this package: high ▼ security
    • CVE-2023-54404 affects this package: high ▼ security
    • CVE-2026-9679 affects this package: high ▼ security
    • CVE-2026-14643 affects this package: high ▼ security
    • CVE-2026-16728 affects this package: high ▼ security
    • CVE-2026-9678 affects this package: high ▼ security
    • CVE-2026-1525 affects this package: high ▼ security
    • CVE-2026-84947 affects this package: high ▼ security
    • CVE-2026-84890 affects this package: high ▼ security
    • CVE-2026-15157 affects this package: high ▼ security
    • CVE-2026-104850 affects this package: high ▼ security
    • CVE-2026-6733 affects this package: high ▼ security
    • CVE-2026-22036 affects this package: high ▼ security
    • CVE-2026-16729 affects this package: high ▼ security
    • CVE-2026-111768 affects this package: high ▼ security
    • CVE-2026-85014 affects this package: high ▼ security
    • CVE-2026-1528 affects this package: high ▼ security
    • CVE-2026-12151 affects this package: high ▼ security
    • CVE-2026-2229 affects this package: high ▼ security
    • CVE-2026-85008 affects this package: high ▼ security
    • CVE-2026-18540 affects this package: high ▼ security
    • CVE-2026-87029 affects this package: high ▼ security
    • CVE-2026-109841 affects this package: high ▼ security
    • CVE-2026-1526 affects this package: high ▼ security
    • CVE-2026-87018 affects this package: high ▼ security
    • CVE-2026-0621 affects this package: high ▼ security
    • CVE-2026-19534 affects this package: high ▼ security
    • CVE-2026-109932 affects this package: high ▼ security
  • 4 Nov 26 0
    • CVE-2026-111771 affects this package: high ▼ security
    • GHSA-f897-62hf-6gxq affects this package: high ▼ security
    • CVE-2026-109924 affects this package: high ▼ security
    • CVE-2026-111769 affects this package: high ▼ security
    • CVE-2026-109829 affects this package: high ▼ security
    • CVE-2026-84933 affects this package: high ▼ security
    • CVE-2026-25536 affects this package: high ▼ security
    • CVE-2026-111767 affects this package: high ▼ security
    • CVE-2026-11525 affects this package: high ▼ security
    • CVE-2026-1527 affects this package: high ▼ security
    • CVE-2026-13697 affects this package: high ▼ security
    • CVE-2026-18149 affects this package: high ▼ security
    • CVE-2026-109383 affects this package: high ▼ security
    • CVE-2023-54404 affects this package: high ▼ security
    • CVE-2026-9679 affects this package: high ▼ security
    • CVE-2026-14643 affects this package: high ▼ security
    • CVE-2026-16728 affects this package: high ▼ security
    • CVE-2026-9678 affects this package: high ▼ security
    • CVE-2026-1525 affects this package: high ▼ security
    • CVE-2026-84947 affects this package: high ▼ security
    • CVE-2026-84890 affects this package: high ▼ security
    • CVE-2026-15157 affects this package: high ▼ security
    • CVE-2026-104850 affects this package: high ▼ security
    • CVE-2026-6733 affects this package: high ▼ security
    • CVE-2026-22036 affects this package: high ▼ security
    • CVE-2026-16729 affects this package: high ▼ security
    • CVE-2026-111768 affects this package: high ▼ security
    • CVE-2026-85014 affects this package: high ▼ security
    • CVE-2026-1528 affects this package: high ▼ security
    • CVE-2026-12151 affects this package: high ▼ security
    • CVE-2026-2229 affects this package: high ▼ security
    • CVE-2026-85008 affects this package: high ▼ security
    • CVE-2026-18540 affects this package: high ▼ security
    • CVE-2026-87029 affects this package: high ▼ security
    • CVE-2026-109841 affects this package: high ▼ security
    • CVE-2026-1526 affects this package: high ▼ security
    • CVE-2026-87018 affects this package: high ▼ security
    • CVE-2026-0621 affects this package: high ▼ security
    • CVE-2026-19534 affects this package: high ▼ security
    • CVE-2026-109932 affects this package: high ▼ security
  • 3 Nov 26 0
    • CVE-2026-111771 affects this package: high ▼ security
    • GHSA-f897-62hf-6gxq affects this package: high ▼ security
    • CVE-2026-109924 affects this package: high ▼ security
    • CVE-2026-111769 affects this package: high ▼ security
    • CVE-2026-109829 affects this package: high ▼ security
    • CVE-2026-84933 affects this package: high ▼ security
    • CVE-2026-25536 affects this package: high ▼ security
    • CVE-2026-111767 affects this package: high ▼ security
    • CVE-2026-11525 affects this package: high ▼ security
    • CVE-2026-1527 affects this package: high ▼ security
    • CVE-2026-13697 affects this package: high ▼ security
    • CVE-2026-18149 affects this package: high ▼ security
    • CVE-2026-109383 affects this package: high ▼ security
    • CVE-2023-54404 affects this package: high ▼ security
    • CVE-2026-9679 affects this package: high ▼ security
    • CVE-2026-14643 affects this package: high ▼ security
    • CVE-2026-16728 affects this package: high ▼ security
    • CVE-2026-9678 affects this package: high ▼ security
    • CVE-2026-1525 affects this package: high ▼ security
    • CVE-2026-84947 affects this package: high ▼ security
    • CVE-2026-84890 affects this package: high ▼ security
    • CVE-2026-15157 affects this package: high ▼ security
    • CVE-2026-104850 affects this package: high ▼ security
    • CVE-2026-6733 affects this package: high ▼ security
    • CVE-2026-22036 affects this package: high ▼ security
    • CVE-2026-16729 affects this package: high ▼ security
    • CVE-2026-111768 affects this package: high ▼ security
    • CVE-2026-85014 affects this package: high ▼ security
    • CVE-2026-1528 affects this package: high ▼ security
    • CVE-2026-12151 affects this package: high ▼ security
    • CVE-2026-2229 affects this package: high ▼ security
    • CVE-2026-85008 affects this package: high ▼ security
    • CVE-2026-18540 affects this package: high ▼ security
    • CVE-2026-87029 affects this package: high ▼ security
    • CVE-2026-109841 affects this package: high ▼ security
    • CVE-2026-1526 affects this package: high ▼ security
    • CVE-2026-87018 affects this package: high ▼ security
    • CVE-2026-0621 affects this package: high ▼ security
    • CVE-2026-19534 affects this package: high ▼ security
    • CVE-2026-109932 affects this package: high ▼ security
  • 2 Nov 26 0
    • CVE-2026-111771 affects this package: high ▼ security
    • GHSA-f897-62hf-6gxq affects this package: high ▼ security
    • CVE-2026-109924 affects this package: high ▼ security
    • CVE-2026-111769 affects this package: high ▼ security
    • CVE-2026-109829 affects this package: high ▼ security
    • CVE-2026-84933 affects this package: high ▼ security
    • CVE-2026-25536 affects this package: high ▼ security
    • CVE-2026-111767 affects this package: high ▼ security
    • CVE-2026-11525 affects this package: high ▼ security
    • CVE-2026-1527 affects this package: high ▼ security
    • CVE-2026-13697 affects this package: high ▼ security
    • CVE-2026-18149 affects this package: high ▼ security
    • CVE-2026-109383 affects this package: high ▼ security
    • CVE-2023-54404 affects this package: high ▼ security
    • CVE-2026-9679 affects this package: high ▼ security
    • CVE-2026-14643 affects this package: high ▼ security
    • CVE-2026-16728 affects this package: high ▼ security
    • CVE-2026-9678 affects this package: high ▼ security
    • CVE-2026-1525 affects this package: high ▼ security
    • CVE-2026-84947 affects this package: high ▼ security
    • CVE-2026-84890 affects this package: high ▼ security
    • CVE-2026-15157 affects this package: high ▼ security
    • CVE-2026-104850 affects this package: high ▼ security
    • CVE-2026-6733 affects this package: high ▼ security
    • CVE-2026-22036 affects this package: high ▼ security
    • CVE-2026-16729 affects this package: high ▼ security
    • CVE-2026-111768 affects this package: high ▼ security
    • CVE-2026-85014 affects this package: high ▼ security
    • CVE-2026-1528 affects this package: high ▼ security
    • CVE-2026-12151 affects this package: high ▼ security
    • CVE-2026-2229 affects this package: high ▼ security
    • CVE-2026-85008 affects this package: high ▼ security
    • CVE-2026-18540 affects this package: high ▼ security
    • CVE-2026-87029 affects this package: high ▼ security
    • CVE-2026-109841 affects this package: high ▼ security
    • CVE-2026-1526 affects this package: high ▼ security
    • CVE-2026-87018 affects this package: high ▼ security
    • CVE-2026-0621 affects this package: high ▼ security
    • CVE-2026-19534 affects this package: high ▼ security
    • CVE-2026-109932 affects this package: high ▼ security
  • 1 Nov 26 0

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

    • CVE-2026-111771 affects this package: high ▼ security
    • GHSA-f897-62hf-6gxq affects this package: high ▼ security
    • CVE-2026-109924 affects this package: high ▼ security
    • CVE-2026-111769 affects this package: high ▼ security
    • CVE-2026-109829 affects this package: high ▼ security
    • CVE-2026-84933 affects this package: high ▼ security
    • CVE-2026-25536 affects this package: high ▼ security
    • CVE-2026-111767 affects this package: high ▼ security
    • CVE-2026-11525 affects this package: high ▼ security
    • CVE-2026-1527 affects this package: high ▼ security
    • CVE-2026-13697 affects this package: high ▼ security
    • CVE-2026-18149 affects this package: high ▼ security
    • CVE-2026-109383 affects this package: high ▼ security
    • CVE-2023-54404 affects this package: high ▼ security
    • CVE-2026-9679 affects this package: high ▼ security
    • CVE-2026-14643 affects this package: high ▼ security
    • CVE-2026-16728 affects this package: high ▼ security
    • CVE-2026-9678 affects this package: high ▼ security
    • CVE-2026-1525 affects this package: high ▼ security
    • CVE-2026-84947 affects this package: high ▼ security
    • CVE-2026-84890 affects this package: high ▼ security
    • CVE-2026-15157 affects this package: high ▼ security
    • CVE-2026-104850 affects this package: high ▼ security
    • CVE-2026-6733 affects this package: high ▼ security
    • CVE-2026-22036 affects this package: high ▼ security
    • CVE-2026-16729 affects this package: high ▼ security
    • CVE-2026-111768 affects this package: high ▼ security
    • CVE-2026-85014 affects this package: high ▼ security
    • CVE-2026-1528 affects this package: high ▼ security
    • CVE-2026-12151 affects this package: high ▼ security
    • CVE-2026-2229 affects this package: high ▼ security
    • CVE-2026-85008 affects this package: high ▼ security
    • CVE-2026-18540 affects this package: high ▼ security
    • CVE-2026-87029 affects this package: high ▼ security
    • CVE-2026-109841 affects this package: high ▼ security
    • CVE-2026-1526 affects this package: high ▼ security
    • CVE-2026-87018 affects this package: high ▼ security
    • CVE-2026-0621 affects this package: high ▼ security
    • CVE-2026-19534 affects this package: high ▼ security
    • CVE-2026-109932 affects this package: high ▼ security
  • 2 Oct 26 31

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Analysed npm/midnight-nextjs-mcp@0.3.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 40 findings
ID CVE Severity Vector Fix available
GHSA-22jm-h49p-29qw CVE-2026-111767 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L yes
GHSA-345p-7cg4-v4c7 CVE-2026-25536 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N yes
GHSA-46jr-4wx8-v453 CVE-2026-111768 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-6prh-2h8m-c8cw CVE-2026-111769 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-6qxp-vccf-f47h CVE-2026-104850 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-8r9q-7v3j-jr4g CVE-2026-0621 high yes
GHSA-f897-62hf-6gxq high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-rvq5-wwqv-78pq CVE-2026-111771 medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N yes
GHSA-2gqq-gqf2-x968 CVE-2026-84947 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-2jfj-6hjv-fm6j CVE-2026-84933 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-2m5v-pch6-74hx CVE-2026-109383 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-2mjp-6q6p-2qxm CVE-2026-1525 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L yes
GHSA-35p6-xmwp-9g52 CVE-2026-6733 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-3xpg-4rpp-hhhm CVE-2026-84890 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-4992-7rv2-5pvq CVE-2026-1527 medium CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N yes
GHSA-4cwx-7wf7-3272 CVE-2026-13697 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H yes
GHSA-4qv8-2p9j-2685 CVE-2026-109924 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-4w7w-5xrc-9h26 CVE-2026-109829 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-55wc-3pg8-jfw6 CVE-2026-87029 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-8436-99hf-9mmv CVE-2026-85008 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-8xcm-r25x-g524 CVE-2026-16728 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-9fm3-97px-rjf6 CVE-2026-109932 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-f269-vfmq-vjvj CVE-2026-1528 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-f72v-6w45-q472 CVE-2026-109841 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-g8m3-5g58-fq7m CVE-2026-11525 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-g9mf-h72j-4rw9 CVE-2026-22036 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-jr45-8vmc-qm54 CVE-2026-14643 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-m8rv-5g2x-5cg5 CVE-2026-15157 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N yes
GHSA-p88m-4jfj-68fv CVE-2026-9679 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-pmjh-fq2x-6v4x CVE-2026-18149 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-pr7r-676h-xcf6 CVE-2026-9678 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-qrxm-fqhp-jwvm CVE-2026-87018 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-r53p-7pc4-xj5r CVE-2026-18540 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-rfgv-xxqx-mfg5 CVE-2026-19534 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-rx4f-c7p8-82vq CVE-2026-85014 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-v3r7-h72x-cjcm CVE-2026-16729 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-v9p9-hfj2-hcw8 CVE-2026-2229 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-vrm6-8vpv-qv8q CVE-2026-1526 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-vxpw-j846-p89q CVE-2026-12151 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 188 packages
Packages resolved 188
Stale 46
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Install

How do I install the Midnight + Next.js MCP server?

Midnight + Next.js MCP runs locally as an npm package, launched with npx -y midnight-nextjs-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · midnight-nextjs-mcp

# add to Claude Code
claude mcp add fractionestate-midnight-nextjs-mcp -- npx -y midnight-nextjs-mcp
Common questions

What is the Midnight + Next.js MCP server?

Midnight + Next.js MCP is listed in the public MCP registry as io.github.FractionEstate/midnight-nextjs-mcp. Unified MCP server for Midnight blockchain development and Next.js dApps. This page covers its npm package (midnight-nextjs-mcp).

Is the Midnight + Next.js MCP server safe to use?

Midnight + Next.js MCP scores 31 out of 100 on VerifyMCP. We recorded 40 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Is the Midnight + Next.js MCP server still maintained?

Midnight + Next.js MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Midnight + Next.js MCP server under?

Midnight + Next.js MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.