Submit.co
REMOTE · SUBMIT.CO
Where to launch a startup: researched directories, launch platforms, newsletters and press.
Available components
Last scanned (10 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability59
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 866 tokens (~433/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 30 Oct 26 71
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 5 Nov 2026 · Probed https://submit.co/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=submit.co | CN=WE1,O=Google Trust Services,C=US | 30 Sept 2026 | 29 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 98c87e414bb96455135cbc63d5f8d6df |
| SANs: submit.co, *.submit.co | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of submit.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| submit.co. | 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 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://submit.co/mcp | Verified | 200 | |
| http (plaintext) | http://submit.co/mcp | HTTPS enforced | 301 | https://submit.co/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_site Get a site ~66
Look up one site on Submit.co by its domain: what it costs, the link a product gets, who gets in, how much exposure it gets, and where to submit.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The site's domain, e.g. betalist.com. A URL works too |
No output schema declared.
No examples provided.
search_sites Search sites to submit a product to ~249
List launch platforms, directories, communities, newsletters, press and review sites that take product submissions, highest Ahrefs Domain Rating first. Every filter is optional; combine them to narrow the list.
| Name | Type | Req | Description |
|---|---|---|---|
| acceptance | string | – | everyone: every product that fits. reviewed: most get in. selective: only a few are picked |
| backlink | string | – | The link the product gets: dofollow helps SEO |
| exposure | string | – | featured_to_audience: shown on their homepage, newsletter or social. depends_on_votes: visibility depends on upvotes. listing_only: a listing page, little promotion |
| limit | integer | – | Sites per page (default 25) |
| niche | string | – | Products the site is for. general sites take any product |
| offset | integer | – | Sites to skip, from next_offset of the previous page |
| price | string | – | free: free to list, including sites with paid options. free_without_backlink: free without having to link back to them. paid: paid only |
| q | string | – | Part of the site's name or domain, e.g. hunt or betalist |
| type | string | – | Kind of site |
No output schema declared.
No examples provided.
How do I install the Submit.co MCP server?
Submit.co is a hosted endpoint at https://submit.co/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 · submit.co
claude mcp add --transport http co-submit-submit 'https://submit.co/mcp'
What is the Submit.co MCP server?
Submit.co is an MCP server listed in the public MCP registry as co.submit/submit. Where to launch a startup: researched directories, launch platforms, newsletters and press. This page covers its hosted endpoint (https://submit.co/mcp).
Is the Submit.co MCP server safe to use?
Submit.co scores 73 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 Submit.co MCP server expose?
Submit.co exposes 2 tools: search_sites, get_site. Their descriptions and schemas cost roughly 315 tokens of context every time the server is loaded.
Does the Submit.co MCP server require authentication?
No. We connected to Submit.co without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Submit.co MCP server still maintained?
Submit.co is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.