Remote MCP · Endpoint

app.founderhood/founderhood MCP server

No. app.founderhood/founderhood answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://founderhood.app/api/mcp

The last check completed an MCP handshake.

Registry name
app.founderhood/founderhood
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
396 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search indie founders and online businesses by city/country, and submit listings to Founderhood.
Listing
From the official MCP registry (active).
Recent checks of app.founderhood/founderhood
CheckedResultHandshake
43 minutes agoHandshake completed396 ms
8 days agoHandshake completed554 ms
9 days agoHandshake completed230 ms
11 days agoHandshake completed493 ms
12 days agoHandshake completed528 ms
13 days agoHandshake completed627 ms
14 days agoHandshake completed464 ms
14 days agoHandshake completed663 ms
16 days agoHandshake completed486 ms
19 days agoHandshake completed683 ms
21 days agoHandshake completed455 ms
24 days agoHandshake completed523 ms
26 days agoHandshake completed508 ms
28 days agoHandshake completed477 ms

The last 14 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 app.founderhood/founderhood and makes no claim about it beyond what these checks measured.