Remote MCP · Endpoint
io.github.Christianwieprecht/amadeus-agent-intelligence MCP server
No. io.github.Christianwieprecht/amadeus-agent-intelligence answered an MCP handshake 4 days ago.
UpLast checked 4 days ago
Server URL
https://amadeusonline.de/amadeus/mcp/
The last check completed an MCP handshake.
- Registry name
- io.github.Christianwieprecht/amadeus-agent-intelligence
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 303 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 93.8% from 16 checks
- Described by its publisher as
- Live-Status, Aenderungen und neu entdeckte Server im MCP-/Agenten-Oekosystem.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 4 days ago | Handshake completed | 303 ms |
| 4 days ago | Handshake completed | 307 ms |
| 5 days ago | Handshake completed | 302 ms |
| 7 days ago | Handshake completed | 303 ms |
| 8 days ago | Handshake completed | 308 ms |
| 9 days ago | Handshake completed | 306 ms |
| 10 days ago | Handshake completed | 1.25 s |
| 10 days ago | Handshake completed | 308 ms |
| 12 days ago | Handshake completed | 304 ms |
| 15 days ago | Handshake completed | 309 ms |
| 17 days ago | Handshake completed | 360 ms |
| 20 days ago | Failed - the server returned an HTTP error | — |
| 22 days ago | Handshake completed | 304 ms |
| 24 days ago | Handshake completed | 315 ms |
| 26 days ago | Handshake completed | 301 ms |
| 28 days ago | Handshake completed | 323 ms |
| 30 days ago | Handshake completed | 296 ms |
| 32 days ago | Handshake completed | 303 ms |
| 33 days ago | Handshake completed | 302 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 25 responding of 26.
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.Christianwieprecht/amadeus-agent-intelligence and makes no claim about it beyond what these checks measured.