Remote MCP · Endpoint
eyeot ERP MCP server
No. eyeot ERP answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://erp.eyeot.fr/api/v1/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.Termi24/eyeot-erp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2024-11-05
- Handshake latency
- 646 ms
- Tools exposed
- 33 tools
- Uptime, last 30 days
- 4 checks from 4 checks
- Described by its publisher as
- ERP français avec serveur MCP natif : plus de 1 800 actions métier auto-générées via OpenAPI.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 646 ms |
| 10 hours ago | Handshake completed | 264 ms |
| 1 day ago | Handshake completed | 270 ms |
| 2 days ago | Handshake completed | 284 ms |
The last 4 checks. Full history is kept for 30 days; the all-time counter stands at 4 responding of 4.
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 eyeot ERP and makes no claim about it beyond what these checks measured.