Remote MCP · Endpoint

StartupHub.ai MCP server

No. StartupHub.ai answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.startuphub.ai/api/v1/mcp

The last check completed an MCP handshake.

Registry name
ai.startuphub/startuphub
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
145 ms
Tools exposed
82 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Funding rounds, AI startup and investor search, email discovery, agent-readiness. No API key.
Listing
From the official MCP registry (active).
Recent checks of StartupHub.ai
CheckedResultHandshake
1 hour agoHandshake completed145 ms
11 hours agoHandshake completed238 ms
1 day agoHandshake completed181 ms
2 days agoHandshake completed442 ms
4 days agoHandshake completed153 ms
4 days agoHandshake completed451 ms
5 days agoHandshake completed355 ms
6 days agoHandshake completed160 ms
8 days agoHandshake completed171 ms
11 days agoHandshake completed361 ms
13 days agoHandshake completed385 ms
16 days agoHandshake completed172 ms
18 days agoHandshake completed181 ms
20 days agoHandshake completed214 ms
22 days agoHandshake completed174 ms
24 days agoHandshake completed371 ms

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

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 StartupHub.ai and makes no claim about it beyond what these checks measured.