Developer · Remote MCP server
Nodecel
Vibe deployment for nodecel - deploy, roll back, diagnose, and manage apps and domains from chat.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.contextser.mcp/nodecel- Version
- 1.1.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-07-05
- Updated
- 2026-07-05
- Publisher
- com.contextser.mcp
- Namespace
- Namespace verified by the MCP Registry via the domain mcp.contextser.com or a parent domain of it · how
- Website
- mcp.nodecel.com
- Repository
- github.com/contextser/nodecel-cli (folder mcp)
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.nodecel.com | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Nodecel
Nodecel is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.nodecel.com, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| No-Code ExitsNo-code startups for sale, the deal-scoring method behind each pick, and exit stories. | Remote · HTTPLive check: ✓ handshake |
| No-Shell Agent Architect MCPTurns vague automation requests into tool stacks, prompts, QA checks, and human boundaries. | Remote · HTTPLive check: ✓ handshake |
| Nockchain MCPMoved to io.github.winter0x/nockchain-mcp. This entry is no longer updated. | Local · stdio |
| Node RuntimeThis package is intended for demonstration only. Maintained by JFrog Security. | Local · stdio |
| Nodegrove VRAM: can I run it?Can this LLM run on my GPU? VRAM, speed ceiling and what fits instead, for any model and GPU. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| nodriver - undetected browser automationUndetected anti-bot Chrome automation. 70 tools, parallel isolated browsers. | Local · stdio |
| NofaxHuman-in-the-loop approvals and notifications for AI coding agents through a local stdio MCP server. | Local · stdio |
| noisefloor - is this number real?Is this number real, or is it noise? Peek-safe A/B tests, change detection, honest forecasts. | Local · stdio |