Developer · Remote MCP server
No-Code Exits
No-code startups for sale, the deal-scoring method behind each pick, and exit stories.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.nocodeexits/nocodeexits- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-21
- Updated
- 2026-09-21
- Publisher
- com.nocodeexits
- Namespace
- Namespace verified by the MCP Registry via the domain nocodeexits.com · how
- Website
- nocodeexits.com
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://nocodeexits.com/api/mcp | 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 200)
- Handshake
- nocodeexits 1.0.0 · protocol 2025-06-18
- Tools discovered
- 3:
get_daily_picks,search_no_code_tools,search_exit_stories - Checked on
- 2026-10-05
How to connect No-Code Exits
No-Code Exits is a remote MCP server: there is nothing to install. Its endpoint is https://nocodeexits.com/api/mcp, 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 |
|---|---|
| Nis2 Incident Runbook LintReads your incident-response runbook and says which of the three Article 23 clocks it gets wrong. | Local · stdio |
| nittimProduction-safety audits for AI-generated code, with a fix for every finding. | Remote · HTTPLive check: ✓ handshake |
| nlqdb - analytical memory for AI agentsAnalytical memory for AI agents: a real Postgres queried in plain English over MCP. One command. | Remote · HTTPLive check: sign-in required |
| No CrdDynamic pod spawner & proxy for ephemeral AI agent workspaces on Kubernetes without CRDs. | Local · stdio |
| 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 |
| NodecelVibe deployment for nodecel - deploy, roll back, diagnose, and manage apps and domains from chat. | Remote · HTTPLive check: sign-in required |