Remote MCP · Endpoint

SubmitMyStartup MCP server

No. SubmitMyStartup answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://submitmystartup.com/mcp

The last check completed an MCP handshake.

Registry name
com.submitmystartup/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
394 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Find where to submit your startup. Searches a free list of directories with real submission results.
Listing
From the official MCP registry (active).
Recent checks of SubmitMyStartup
CheckedResultHandshake
1 hour agoHandshake completed394 ms
2 days agoHandshake completed77 ms
5 days agoHandshake completed898 ms
7 days agoHandshake completed121 ms
9 days agoHandshake completed178 ms
11 days agoHandshake completed1.06 s
13 days agoHandshake completed113 ms
15 days agoHandshake completed71 ms
17 days agoHandshake completed67 ms
19 days agoHandshake completed88 ms
20 days agoHandshake completed136 ms
21 days agoHandshake completed1.15 s
23 days agoHandshake completed77 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with SubmitMyStartup and makes no claim about it beyond what these checks measured.