Remote MCP · Endpoint

InvestorMatch (public, no sign-in) MCP server

No. InvestorMatch (public, no sign-in) answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://investormatch.pro/mcp/public

The last check completed an MCP handshake.

Registry name
pro.investormatch/investor-match-public
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
110 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Search InvestorMatch's public directory of VC investors and fundraising guides. No sign-in needed.
Listing
From the official MCP registry (active).
Recent checks of InvestorMatch (public, no sign-in)
CheckedResultHandshake
1 hour agoHandshake completed110 ms
2 days agoHandshake completed117 ms
5 days agoHandshake completed131 ms
7 days agoHandshake completed141 ms
9 days agoHandshake completed519 ms
11 days agoHandshake completed160 ms
13 days agoHandshake completed134 ms
15 days agoHandshake completed117 ms
18 days agoHandshake completed133 ms
19 days agoHandshake completed97 ms
20 days agoHandshake completed247 ms
22 days agoHandshake completed178 ms
23 days agoHandshake completed139 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.

Listing data comes from the official MCP registry. Glide is not affiliated with InvestorMatch (public, no sign-in) and makes no claim about it beyond what these checks measured.