No-Code Exits
REMOTE · NOCODEEXITS.COM · SCANNED SEP 28
No-code startups for sale, the deal-scoring method behind each pick, and exit stories.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 283 tokens (~47/item across 6 items; 3 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the No-Code Exits MCP server?
No-Code Exits is a hosted endpoint at https://nocodeexits.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · nocodeexits.com
claude mcp add --transport http com-nocodeexits-nocodeexits 'https://nocodeexits.com/api/mcp'
{
"mcpServers": {
"com-nocodeexits-nocodeexits": {
"url": "https://nocodeexits.com/api/mcp"
}
}
} {
"servers": {
"com-nocodeexits-nocodeexits": {
"type": "http",
"url": "https://nocodeexits.com/api/mcp"
}
}
} [mcp_servers.com-nocodeexits-nocodeexits] url = "https://nocodeexits.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-nocodeexits-nocodeexits": {
"type": "remote",
"url": "https://nocodeexits.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-nocodeexits-nocodeexits --url 'https://nocodeexits.com/api/mcp' --transport streamable-http
mcp_servers:
com-nocodeexits-nocodeexits:
url: "https://nocodeexits.com/api/mcp" {
"McpServers": {
"com-nocodeexits-nocodeexits": {
"Transport": "http",
"Url": "https://nocodeexits.com/api/mcp"
}
}
} assistant mcp add com-nocodeexits-nocodeexits -t streamable-http -u 'https://nocodeexits.com/api/mcp'
{
"mcpServers": {
"com-nocodeexits-nocodeexits": {
"type": "http",
"url": "https://nocodeexits.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 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
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 22 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 21 Sept 26 67
First indexed and scored.
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 28 Sept 2026 · Probed https://nocodeexits.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nocodeexits.com | CN=YR2,O=Let's Encrypt,C=US | 20 Sept 2026 | 19 Dec 2026 | RSA 2048 | SHA256-RSA | 5673a60f508c8f368372b1b47a6714bb4cf |
| SANs: nocodeexits.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of nocodeexits.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| nocodeexits.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=(), interest-cohort=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://nocodeexits.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://nocodeexits.com/api/mcp | HTTPS enforced | 308 | https://nocodeexits.com/api/mcp |
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 →
get_daily_picks ~62
Startups for sale from a No-Code Exits Daily Picks issue: name, asking price, MRR, multiple, deal score and the angle. Omit the date for the latest issue.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Issue date, YYYY-MM-DD |
No output schema declared.
No examples provided.
search_exit_stories ~54
Founder exit stories: what was built, on which tools, what it sold for.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results, default 10 |
| query | string | yes | Keyword across founder, startup and description |
No output schema declared.
No examples provided.
search_no_code_tools ~56
Search the No-Code Exits tool directory: what each tool is for, its pricing and its learning curve.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results, default 10 |
| query | string | yes | Tool name or category |
No output schema declared.
No examples provided.
What is the No-Code Exits MCP server?
No-Code Exits is an MCP server listed in the public MCP registry as com.nocodeexits/nocodeexits. No-code startups for sale, the deal-scoring method behind each pick, and exit stories. This page covers its hosted endpoint (https://nocodeexits.com/api/mcp).
Is the No-Code Exits MCP server safe to use?
No-Code Exits scores 70 out of 100 on VerifyMCP. 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 No-Code Exits MCP server expose?
No-Code Exits exposes 3 tools: get_daily_picks, search_no_code_tools, search_exit_stories. Their descriptions and schemas cost roughly 172 tokens of context every time the server is loaded.
Does the No-Code Exits MCP server require authentication?
No. We connected to No-Code Exits without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the No-Code Exits MCP server still maintained?
No-Code Exits is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.