Remote MCP · Endpoint

Vc Finder MCP server

No. Vc Finder answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://gateway.pipeworx.io/vc-finder/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/vc-finder
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
57 ms
Tools exposed
54 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
vc-finder — VC / angel investor graph (Bruce ask 2026-09-29; built private-first, PUBLIC since…
Listing
From the official MCP registry (active).
Recent checks of Vc Finder
CheckedResultHandshake
43 minutes agoHandshake completed57 ms
3 days agoHandshake completed197 ms
12 days agoHandshake completed113 ms
13 days agoHandshake completed1.08 s
14 days agoHandshake completed1.62 s
15 days agoHandshake completed943 ms
16 days agoHandshake completed1.79 s
17 days agoHandshake completed790 ms
18 days agoHandshake completed218 ms
20 days agoHandshake completed179 ms
22 days agoHandshake completed297 ms
25 days agoHandshake completed74 ms
27 days agoHandshake completed230 ms

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

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