io.github.Noderail/noderail
NPM · @NODERAIL/MCP · SCANNED SEP 25
Provenance and governance layer for AI-readable knowledge. NodeRail answers what AI should trust.
Available components
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
- 49 of 145 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 169 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability84
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 636 tokens (~106/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
How do I install the io.github.Noderail/noderail MCP server?
io.github.Noderail/noderail runs locally as an npm package, launched with npx -y @noderail/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 · @noderail/mcp
claude mcp add noderail-noderail -- npx -y @noderail/mcp
{
"mcpServers": {
"noderail-noderail": {
"command": "npx",
"args": [
"-y",
"@noderail/mcp"
]
}
}
} {
"servers": {
"noderail-noderail": {
"command": "npx",
"args": [
"-y",
"@noderail/mcp"
]
}
}
} codex mcp add noderail-noderail -- npx -y @noderail/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"noderail-noderail": {
"type": "local",
"command": [
"npx",
"-y",
"@noderail/mcp"
],
"enabled": true
}
}
} openclaw mcp add noderail-noderail --command npx --arg -y --arg @noderail/mcp
mcp_servers:
noderail-noderail:
command: "npx"
args: ["-y", "@noderail/mcp"] {
"McpServers": {
"noderail-noderail": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@noderail/mcp"
]
}
}
} assistant mcp add noderail-noderail -t stdio -c npx -a -y @noderail/mcp
{
"mcpServers": {
"noderail-noderail": {
"command": "npx",
"args": [
"-y",
"@noderail/mcp"
]
}
}
} 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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 −3
- Stability: pass → 0.80 functional
- 23 Sept 26 +1
- Stability: 0.97 → pass security
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +2
- CVE-2026-82562 no longer affects this package ▲ security
- CVE-2026-82417 no longer affects this package ▲ security
- Known CVEs: fail → pass ▲ security
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 25 Sept 2026 · Analysed npm/@noderail/mcp@1.0.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 →
Dependencies 145 packages
| Packages resolved | 145 |
|---|---|
| Deprecated | 1 |
| Stale | 48 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
noderail_get_field ~102
Get a Field node by ID or name with full provenance. Returns scope, governance, canonical registry, lineage, citation, and a content preview. If neither field_id nor field_name is provided, lists all available fields.
| Name | Type | Req | Description |
|---|---|---|---|
| field_id | string | – | node_id of the Field node (e.g. NR-20260224-HCS-001) |
| field_name | string | – | Human-readable field name (e.g. "Human Capacity Science") |
No output schema declared.
No examples provided.
noderail_get_lineage ~71
Get the version history and full lineage chain for a node. Returns declared parents, forked_from, adopted_from, declared children, and nodes discovered by reverse-lookup that reference this node as a parent or fork source.
| Name | Type | Req | Description |
|---|---|---|---|
| node_id | string | yes | The node_id to trace lineage for |
No output schema declared.
No examples provided.
noderail_get_node ~71
Get any node by ID with full content — all frontmatter fields and the complete Markdown body.
| Name | Type | Req | Description |
|---|---|---|---|
| include_body | boolean | – | Include full Markdown body (default: true) |
| node_id | string | yes | The unique node_id (e.g. NR-20260224-HCS-001) |
No output schema declared.
No examples provided.
noderail_get_trust_status ~179
Provenance gate: generate a full trust report for a node. Returns: • evidence_level — HIGH / MEDIUM / LOW / CONTESTED / DEPRECATED • canonical_status — whether the node is registered in its field's canonical registry • permitted_use — license, citation requirements, and use guidance • warnings — ordered list of trust concerns • recommendation — clear AI action guidance (SUITABLE / PILOT / DRAFT / CAUTION / DO NOT USE) • provenance — DOI, lineage, maintainer, and validation coverage MCP answers: what can AI access? NodeRail answers: what should AI trust? Always call this tool before citing a node in authoritative AI outputs.
| Name | Type | Req | Description |
|---|---|---|---|
| node_id | string | yes | The node_id to evaluate |
No output schema declared.
No examples provided.
noderail_list_nodes ~76
List all nodes in the NodeRail knowledge graph with status and version. Filter by field, node_type, or status.
| Name | Type | Req | Description |
|---|---|---|---|
| field | string | – | Filter by field name (e.g. "Human Capacity Science") |
| node_type | string | – | Filter by node type |
| status | string | – | Filter by status |
No output schema declared.
No examples provided.
noderail_search_nodes ~137
Search NodeRail nodes by keyword (scans title, tags, body text, and node_id) or filter by author/maintainer name. At least one parameter must be provided.
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | – | Filter by creator, maintainer, or contributor name |
| field | string | – | Restrict search to a specific field |
| limit | integer | – | Maximum results to return (default: 10, max: 50) |
| node_type | string | – | Restrict search to a node type |
| query | string | – | Keyword or phrase to search in title, tags, body, and node_id |
No output schema declared.
No examples provided.
What is the io.github.Noderail/noderail MCP server?
io.github.Noderail/noderail is an MCP server listed in the public MCP registry as io.github.Noderail/noderail. Provenance and governance layer for AI-readable knowledge. NodeRail answers what AI should trust. This page covers its npm package (@noderail/mcp).
Is the io.github.Noderail/noderail MCP server safe to use?
io.github.Noderail/noderail scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 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 io.github.Noderail/noderail MCP server expose?
io.github.Noderail/noderail exposes 6 tools: noderail_get_field, noderail_list_nodes, noderail_get_node, noderail_get_lineage, noderail_search_nodes, noderail_get_trust_status. Their descriptions and schemas cost roughly 636 tokens of context every time the server is loaded.
Is the io.github.Noderail/noderail MCP server still maintained?
io.github.Noderail/noderail is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.