Remote MCP · Endpoint

net.fundz/fundz MCP server

No. net.fundz/fundz answered an MCP handshake 38 minutes ago.

UpLast checked 38 minutes ago

Server URL

https://mcp-app.fundz.net/

The last check completed an MCP handshake.

Registry name
net.fundz/fundz
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
84 ms
Tools exposed
42 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
SEC-sourced funding rounds, acquisitions, exec moves, hiring and investor signals. 7 keyless tools.
Listing
From the official MCP registry (active).
Recent checks of net.fundz/fundz
CheckedResultHandshake
38 minutes agoHandshake completed84 ms
3 days agoHandshake completed421 ms
13 days agoHandshake completed352 ms
13 days agoHandshake completed136 ms
15 days agoHandshake completed130 ms
16 days agoHandshake completed161 ms
17 days agoHandshake completed370 ms
18 days agoHandshake completed89 ms
18 days agoHandshake completed56 ms
20 days agoHandshake completed101 ms
22 days agoHandshake completed357 ms
25 days agoHandshake completed335 ms
27 days agoHandshake completed392 ms

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

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