Remote MCP · Endpoint
Synapze — Financial Intermediary MCP MCP server
Yes, as of 1 hour ago: the server returned an HTTP error.
DownLast checked 1 hour ago
Server URL
https://mcp.synapze.eu/v1/registry
The last check failed: the server returned an HTTP error.
- Registry name
- eu.synapze/financial-intermediary-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 94.1% from 17 checks
- Described by its publisher as
- Connect AI agents to licensed financial intermediaries in France: insurance, credit, wealth.
- Website
- https://mcp.synapze.eu/
- Repository
- https://github.com/ycdvll/synapze-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Failed - the server returned an HTTP error | — |
| 2 days ago | Handshake completed | 291 ms |
| 4 days ago | Handshake completed | 299 ms |
| 5 days ago | Handshake completed | 325 ms |
| 7 days ago | Handshake completed | 321 ms |
| 8 days ago | Handshake completed | 300 ms |
| 9 days ago | Handshake completed | 315 ms |
| 12 days ago | Handshake completed | 278 ms |
| 13 days ago | Handshake completed | 314 ms |
| 15 days ago | Handshake completed | 328 ms |
| 17 days ago | Handshake completed | 294 ms |
| 18 days ago | Handshake completed | 287 ms |
| 19 days ago | Handshake completed | 283 ms |
| 20 days ago | Handshake completed | 304 ms |
| 20 days ago | Handshake completed | 302 ms |
| 21 days ago | Handshake completed | 287 ms |
| 23 days ago | Handshake completed | 326 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 16 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 Synapze — Financial Intermediary MCP and makes no claim about it beyond what these checks measured.