Remote MCP · Endpoint

net.fundz/fundz MCP server

No. net.fundz/fundz answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
101 ms
Tools exposed
32 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.
Website
https://www.fundz.net/
Listing
From the official MCP registry (active).
Recent checks of net.fundz/fundz
CheckedResultHandshake
1 hour agoHandshake completed101 ms
2 days agoHandshake completed357 ms
4 days agoHandshake completed335 ms
7 days agoHandshake completed392 ms
9 days agoHandshake completed81 ms
11 days agoHandshake completed63 ms
13 days agoHandshake completed989 ms
15 days agoHandshake completed104 ms
17 days agoHandshake completed394 ms
19 days agoHandshake completed340 ms
20 days agoHandshake completed405 ms
22 days agoHandshake completed373 ms
23 days agoHandshake completed981 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.