Remote MCP · Endpoint

Oneinfo Storage MCP server

No. Oneinfo Storage answered an MCP handshake 23 minutes ago.

UpLast checked 23 minutes ago

Server URL

https://gateway.pipeworx.io/oneinfo-storage/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/oneinfo-storage
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.57 s
Tools exposed
46 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Italian regulated disclosures direct from 1INFO — keyless, same-day-fresh.
Listing
From the official MCP registry (active).
Recent checks of Oneinfo Storage
CheckedResultHandshake
23 minutes agoHandshake completed1.57 s
8 days agoHandshake completed948 ms
9 days agoHandshake completed219 ms
11 days agoHandshake completed502 ms
12 days agoHandshake completed327 ms
13 days agoHandshake completed167 ms
14 days agoHandshake completed95 ms
15 days agoHandshake completed96 ms
16 days agoHandshake completed628 ms
19 days agoHandshake completed573 ms
21 days agoHandshake completed1.29 s
24 days agoHandshake completed373 ms
26 days agoHandshake completed167 ms
28 days agoHandshake completed54 ms

The last 14 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 Oneinfo Storage and makes no claim about it beyond what these checks measured.