Remote MCP · Endpoint

Interfibra MCP server

No. Interfibra answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://interfibra.it/api/mcp

The last check completed an MCP handshake.

Registry name
it.interfibra/copertura
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
295 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Copertura fibra e FWA per indirizzo in Italia, offerte Interfibra con costi e link di attivazione
Listing
From the official MCP registry (active).
Recent checks of Interfibra
CheckedResultHandshake
1 hour agoHandshake completed295 ms
1 day agoHandshake completed311 ms
2 days agoHandshake completed305 ms
3 days agoHandshake completed294 ms
4 days agoHandshake completed297 ms
5 days agoHandshake completed529 ms
6 days agoHandshake completed293 ms
9 days agoHandshake completed371 ms
11 days agoHandshake completed290 ms
14 days agoHandshake completed295 ms
16 days agoHandshake completed290 ms
18 days agoHandshake completed292 ms
20 days agoHandshake completed342 ms
22 days agoHandshake completed353 ms
24 days agoHandshake completed291 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

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 Interfibra and makes no claim about it beyond what these checks measured.