Remote MCP · Endpoint
ITEON MCP Server MCP server
No. ITEON MCP Server answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://api.iteon.pl/api/v1/mcp/public
The last check completed an MCP handshake.
- Registry name
- pl.iteon/mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-11-25
- Handshake latency
- 436 ms
- Tools exposed
- 8 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Polski software house B2B: 5 public + 7 OAuth 2.1 private MCP tools (AI estimate, draft, risk).
- Repository
- https://github.com/ITEONpl/iteon-apps
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 436 ms |
| 1 day ago | Handshake completed | 347 ms |
| 2 days ago | Handshake completed | 380 ms |
| 3 days ago | Handshake completed | 367 ms |
| 4 days ago | Handshake completed | 378 ms |
| 5 days ago | Handshake completed | 383 ms |
| 6 days ago | Handshake completed | 628 ms |
| 8 days ago | Handshake completed | 392 ms |
| 11 days ago | Handshake completed | 352 ms |
| 13 days ago | Handshake completed | 366 ms |
| 15 days ago | Handshake completed | 583 ms |
| 18 days ago | Handshake completed | 392 ms |
| 20 days ago | Handshake completed | 157 ms |
| 22 days ago | Handshake completed | 364 ms |
| 24 days ago | Handshake completed | 365 ms |
| 26 days ago | Handshake completed | 347 ms |
| 27 days ago | Handshake completed | 367 ms |
| 29 days ago | Handshake completed | 391 ms |
| 29 days ago | Handshake completed | 408 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 29 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 ITEON MCP Server and makes no claim about it beyond what these checks measured.