Remote MCP · Endpoint
GMCA Certainty Matrix Validate MCP server
No. GMCA Certainty Matrix Validate answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://gmca-researchapp.web.app/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.tridevils/gmca-certainty-matrix-validate
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 170 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 17.6% from 17 checks
- Described by its publisher as
- GMCA Certainty Matrix Validate: 11 vragen om een project te screenen vóór investering.
- Website
- https://gmca.be/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 170 ms |
| 2 days ago | Handshake completed | 185 ms |
| 4 days ago | Handshake completed | 167 ms |
| 5 days ago | Failed - the response was not JSON-RPC | — |
| 7 days ago | Failed - the response was not JSON-RPC | — |
| 8 days ago | Failed - the response was not JSON-RPC | — |
| 9 days ago | Failed - the response was not JSON-RPC | — |
| 12 days ago | Failed - the response was not JSON-RPC | — |
| 13 days ago | Failed - the response was not JSON-RPC | — |
| 15 days ago | Failed - the response was not JSON-RPC | — |
| 17 days ago | Failed - the response was not JSON-RPC | — |
| 18 days ago | Failed - the response was not JSON-RPC | — |
| 19 days ago | Failed - the response was not JSON-RPC | — |
| 20 days ago | Failed - the response was not JSON-RPC | — |
| 20 days ago | Failed - the response was not JSON-RPC | — |
| 21 days ago | Failed - the response was not JSON-RPC | — |
| 23 days ago | Failed - the response was not JSON-RPC | — |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 3 responding of 17.
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 GMCA Certainty Matrix Validate and makes no claim about it beyond what these checks measured.