No-Code Exits
REMOTE · NOCODEEXITS.COM
No-code startups for sale, the deal-scoring method behind each pick, and exit stories.
Available components
Last scanned (16 hours ago)
Scores higher than 77% of remote servers
Reachable. Last reached 21 Nov 2026.
Category E-commerce
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 8 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 Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 752 tokens (~62/item across 12 items; 8 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 15 Nov 26 0
- Schema quality: 49 → 62 ▼ functional
- New tool “calculate_payback” functional
- New tool “find_proven_patterns” functional
- New tool “score_my_listing” functional
- New tool “stack_to_exit” functional
- 13 Nov 26 0
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- 12 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 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
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 21 Nov 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. | DS published | 19718 | 13 | Verified |
| nocodeexits.com. | No DS | 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 →
calculate_payback ~76
How many months of profit an asking price takes to pay back, with the price as a multiple of annual profit and of annual revenue.
| Name | Type | Req | Description |
|---|---|---|---|
| monthly_profit | number | yes | Average monthly profit in USD |
| monthly_revenue | number | – | Average monthly revenue in USD. Optional. |
| price | number | yes | Asking price in USD |
No output schema declared.
No examples provided.
find_proven_patterns ~111
Red-ocean validation for an idea: businesses we covered that already make money with the same shape, plus how to reuse that shape for a different audience. Members see every matching Daily Pick, the public sees three.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | Who you want to sell to instead, e.g. 'dentists'. Optional. |
| idea | string | yes | The idea in a few words, e.g. 'directory of wedding venues' |
| limit | number | – | Max matches, default 8 |
No output schema declared.
No examples provided.
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.
list_skills ~37
List the AI and No-Code Exits skills an agent can run or install, with what each does and whether it needs a member key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
score_my_listing ~100
Score your own startup the way the Daily Picks score listings (0 to 100), with points per component and the one thing costing the most.
| Name | Type | Req | Description |
|---|---|---|---|
| asking_price | number | yes | Asking price in USD |
| growth_30d | number | – | MRR growth over the last 30 days, in percent. Optional. |
| margin | number | – | Profit margin in percent. Optional. |
| mrr | number | yes | Monthly recurring revenue in USD |
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 ~58
Search the AI and 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.
stack_to_exit ~70
Which no-code tools the founders we interviewed built on, how many of those businesses make money and how many sold. Pass a tool for its examples, or omit it for the full table.
| Name | Type | Req | Description |
|---|---|---|---|
| tool | string | – | Tool name, e.g. 'Bubble' or 'Softr'. Optional. |
No output schema declared.
No examples provided.
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'
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 80 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 8 tools: get_daily_picks, search_no_code_tools, search_exit_stories, find_proven_patterns, stack_to_exit, and 3 more. Their descriptions and schemas cost roughly 568 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the No-Code Exits MCP server?
VerifyMCP ran 12 checks on No-Code Exits, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about No-Code Exits: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.