Noderail
NodeRail is a MCP server that enforces provenance and governance for AI-readable knowledge from a local NodeRail repository.
About
NodeRail MCP is a stdio integration that layers provenance and governance on AI-readable knowledge stored in a local NodeRail repo. Developers installing it are usually past the prototype phase: they have skills, specs, or policy docs the agent must treat as canonical, and they need guardrails against stale or unvetted snippets sneaking into answers. You install @noderail/mcp from npm, set NODERAIL_REPO_PATH to your NodeRail workspace, and register the server in Claude Code or Cursor. The server description centers on trust—what content carries lineage versus ad-hoc notes. That aligns with Ship → security more than casual Build docs, though you will maintain the repo during Build. Intermediate complexity comes from maintaining the NodeRail repository structure alongside MCP config. It is governance infrastructure, not a RAG host or GitHub browser.
- Provenance and governance layer focused on AI-readable knowledge trust decisions
- npm package @noderail/mcp v1.0.1 with stdio transport and Node runtime hint
- Requires NODERAIL_REPO_PATH pointing at your local NodeRail repository
- Answers “what should AI trust?” rather than raw file dump without lineage
Noderail by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --env NODERAIL_REPO_PATH=YOUR_NODERAIL_REPO_PATH noderail -- npx -y @noderail/mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Package | @noderail/mcp |
|---|---|
| Transport | STDIO |
| Auth | Required |
What it does
Attach provenance and governance metadata so your agent knows which local knowledge files are authoritative and trustworthy.
Who is it for?
Best when you're running a local NodeRail knowledge base and need MCP access with trust and lineage semantics.
Skip if: Quick RAG over PDFs without governance, or teams unwilling to maintain a NodeRail repo on disk.
What you get
After setup, MCP-backed workflows can discriminate trusted, governed knowledge using your NodeRail repo path.
- MCP access to governed NodeRail knowledge with trust-oriented semantics
- Repeatable local repo path binding for agent sessions
By the numbers
- npm identifier @noderail/mcp version 1.0.1
- Transport stdio; required env NODERAIL_REPO_PATH
- MCP server schema 2025-12-11
Recommended MCP Servers
1Claw VaultHSM-backed vault secrets for AI agents (JIT fetch) plus prompt-injection and threat scanning.2
1passwordMCP server for 1Password service accounts — tools and resources for vaults and credentials18
402sentinel McpAssess an x402 counterparty's risk BEFORE paying: allow/review/block, scored on-chain (Base).1
A2adependencyinspector McpRemote MCP for A2A dependency inspector MCP, structured receipts, audit logs, and reviewer-ready eviA2a Governance Bridge McpA2A Governance Bridge MCP server.A2aidentitytoll McpRemote MCP for A2A caller identity, scope policy, verdict receipts, and audit history.How it compares
Local provenance governance MCP, not cloud RAG and not runtime MCP attack monitoring.
FAQ
Who is noderail for?
Developers and small teams using NodeRail to govern which knowledge an AI agent should trust.
When should I use noderail?
Use it when shipping or hardening agent workflows that must respect provenance on local AI-readable knowledge.
How do I add noderail to my agent?
Install @noderail/mcp, set NODERAIL_REPO_PATH to your local NodeRail repository, configure stdio MCP in your client, and restart the agent.