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.

Neo.mjs Neural Link

NPM · NEO-NEURAL-LINK

Live runtime inspection, component tree, VDOM, state, and hot-patching bridge for Neo.mjs apps.

Available components

+4 this week 64 Trust /100

Last scanned (6 hours ago)

Scores higher than 31% of npm servers

Category Developer Tools

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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 32 of 102 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability42
  • AI-judged instruction clarity (poor).Fail
  • Tool/resource definitions use about 2063 tokens (~34/item across 60 items; 60 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage66
  • 90% of tools have a non-trivial description (not blank, and not just the tool's name).Partial
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (72% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute_dock_operation" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 60 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 3 Nov 26 +4
    • Stability: unverified → 0.27 ▲ functional
  • 27 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 26 Oct 26 45

    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/neo-neural-link@1.0.0

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 →

Dependencies 102 packages
Packages resolved 102
Stale 32
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 60 exposed · ~2,063 tokens

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 →

Tool Tokens
reload_page ~19

Reload Page

NameTypeReqDescription
sessionIdstring––

No output schema declared.

No examples provided.

remove_component ~27

Remove Component

NameTypeReqDescription
componentIdstringyes–
sessionIdstring––

No output schema declared.

No examples provided.

replay_transaction ~35

Replay Transaction

NameTypeReqDescription
archiveIdstringyes–
groupIdstring––
sessionIdstring––

No output schema declared.

No examples provided.

restore_perspective ~36

Restore Perspective

NameTypeReqDescription
componentIdstringyes–
namestringyes–
sessionIdstring––

Structured output declared, but exposes no named fields.

No examples provided.

save_transaction ~42

Save Transaction

NameTypeReqDescription
groupIdstring––
namestring––
sessionIdstring––
txIdstringyes–

No output schema declared.

No examples provided.

set_instance_properties ~35

Set Instance Properties

NameTypeReqDescription
idstringyes–
propertiesobjectyes–
sessionIdstring––

No output schema declared.

No examples provided.

set_route ~34

Set Route

NameTypeReqDescription
hashstringyes–
sessionIdstring––
windowIdstring––
NameTypeReqDescription
hashstring––
statusstring––

No examples provided.

simulate_event ~28

Simulate DOM Event

NameTypeReqDescription
eventsarrayyes–
sessionIdstring––
NameTypeReqDescription
resultbooleanyes–

No examples provided.

undo ~27

Undo Last Mutation

NameTypeReqDescription
groupIdstring––
sessionIdstring––

No output schema declared.

No examples provided.

verify_component_consistency ~31

Verify Component Consistency

NameTypeReqDescription
componentIdstringyes–
sessionIdstring––

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Neo.mjs Neural Link MCP server?

Neo.mjs Neural Link runs locally as an npm package, launched with npx -y neo-neural-link. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · neo-neural-link

# add to Claude Code
claude mcp add neomjs-neural-link -- npx -y neo-neural-link
Common questions

What is the Neo.mjs Neural Link MCP server?

Neo.mjs Neural Link is an MCP server listed in the public MCP registry as io.github.neomjs/neural-link. Live runtime inspection, component tree, VDOM, state, and hot-patching bridge for Neo.mjs apps. This page covers its npm package (neo-neural-link).

Is the Neo.mjs Neural Link MCP server safe to use?

Neo.mjs Neural Link scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting 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.

What tools does the Neo.mjs Neural Link MCP server expose?

Neo.mjs Neural Link exposes 60 tools: healthcheck, get_mcp_tool_handbook, check_namespace, find_instances, get_namespace_tree, and 55 more. Their descriptions and schemas cost roughly 2,063 tokens of context every time the server is loaded.

Is the Neo.mjs Neural Link MCP server still maintained?

Neo.mjs Neural Link 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 Neo.mjs Neural Link MCP server under?

Neo.mjs Neural Link declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.