Remote MCP · Endpoint
Synapze — Financial Intermediary MCP MCP server
Yes, as of 2 hours ago: the server returned an HTTP error.
DownLast checked 2 hours 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
- 27.8% from 18 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 |
|---|---|---|
| 2 hours ago | Failed - the server returned an HTTP error | — |
| 1 day ago | Failed - the server returned an HTTP error | — |
| 2 days ago | Failed - the server returned an HTTP error | — |
| 3 days ago | Failed - the server returned an HTTP error | — |
| 4 days ago | Failed - the server returned an HTTP error | — |
| 5 days ago | Failed - the server returned an HTTP error | — |
| 6 days ago | Failed - the server returned an HTTP error | — |
| 9 days ago | Failed - the server returned an HTTP error | — |
| 11 days ago | Failed - the server returned an HTTP error | — |
| 14 days ago | Failed - the server returned an HTTP error | — |
| 16 days ago | Failed - the server returned an HTTP error | — |
| 18 days ago | Failed - the server returned an HTTP error | — |
| 20 days ago | Failed - the server returned an HTTP error | — |
| 22 days ago | Handshake completed | 291 ms |
| 24 days ago | Handshake completed | 299 ms |
| 26 days ago | Handshake completed | 325 ms |
| 27 days ago | Handshake completed | 321 ms |
| 29 days ago | Handshake completed | 300 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 29.
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.