Back to Browse

Nc Protocol MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

Remote MCP server exposing your Node Command fleet (files, shell, processes, browser) to AI hosts.

About

Remote MCP server exposing your Node Command fleet (files, shell, processes, browser) to AI hosts.

Remote endpoints: streamable-http: https://mcp.nodecommand.app/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

Endpoint verified · Open access · No issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

file_system

Applies to the server that hosts this plugin, not to your machine.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "io-github-huseyincig-nc-mcp": {
      "url": "https://mcp.nodecommand.app/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

nc-protocol

Public wire contracts, Model Context Protocol (MCP) tool schemas, and agent protocol definitions for Node Command.

This repository is the canonical source of truth for the public Node Command contracts. It contains strictly declarative schemas and contracts: no proprietary server code, no database schemas, and no secrets.


Namespaces

agent/     Hub ↔ Agent wire protocol (hello / welcome / request / reply / heartbeat)
mcp/       Model-facing MCP surface (tool schemas + canonical tool manifest)
policy/    Public host-policy projection + capability names
browser/   Public browser and egress policy schemas
bindings/  Generated language bindings (JavaScript ESM)

Installation & Consumption

# As an npm dependency
npm install nc-protocol

Import JavaScript bindings directly:

import {
  MCP_TOOL_CONTRACT_VERSION,
  MCP_TOOL_MANIFEST_FINGERPRINT,
  MCP_TOOL_NAMES,
  HOST_POLICY_CAPABILITY_NAMES
} from 'nc-protocol';

JSON schemas can also be imported by subpath:

import helloSchema from 'nc-protocol/agent/hello.schema.json' with { type: 'json' };
import toolsIndex from 'nc-protocol/mcp/tools/index.json' with { type: 'json' };

Testing & Validation

nc-protocol has zero runtime dependencies and uses the native Node.js test runner:

# Clone the repository
git clone https://github.com/huseyincig/nc-protocol.git
cd nc-protocol

# Run test suite
npm test
# Or:
node --test tests/*.mjs

The test suite validates:

  1. Presence of all required namespace files.
  2. Exact matching between tool definitions, mcp/tools/index.json, and tool count.
  3. Cryptographic consistency of the canonical sha256 manifest fingerprint.
  4. Schema parse validity and schema draft conformance.
  5. Binding parity with declarative contract files.

Contributing

See CONTRIBUTING.md for detailed guidelines on how to propose new tools, update schemas, recompute fingerprints, and submit pull requests.


Versioning & Compatibility


License

Apache-2.0 — see LICENSE.

Reviews

No reviews yet

Be the first to review this server!