Remote MCP · Endpoint
io.github.Amalgix-io/Amalgix MCP server
No. io.github.Amalgix-io/Amalgix answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://amalgix.io/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.Amalgix-io/Amalgix
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 291 ms
- Tools exposed
- 8 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Cross-model evidence pipeline for financial filings & contracts. x402 pay-per-call.
- Website
- https://amalgix.io/
- Repository
- https://github.com/Amalgix-io/Amalgix
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 291 ms |
| 11 hours ago | Handshake completed | 344 ms |
| 1 day ago | Handshake completed | 323 ms |
| 2 days ago | Handshake completed | 346 ms |
| 4 days ago | Handshake completed | 348 ms |
| 4 days ago | Handshake completed | 311 ms |
| 5 days ago | Handshake completed | 130 ms |
| 6 days ago | Handshake completed | 305 ms |
| 8 days ago | Handshake completed | 556 ms |
| 11 days ago | Handshake completed | 318 ms |
| 13 days ago | Handshake completed | 316 ms |
| 16 days ago | Handshake completed | 321 ms |
| 18 days ago | Handshake completed | 325 ms |
| 20 days ago | Handshake completed | 555 ms |
| 22 days ago | Handshake completed | 371 ms |
| 24 days ago | Handshake completed | 348 ms |
| 26 days ago | Handshake completed | 311 ms |
| 27 days ago | Handshake completed | 291 ms |
| 29 days ago | Handshake completed | 128 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 31 responding of 31.
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 io.github.Amalgix-io/Amalgix and makes no claim about it beyond what these checks measured.