Remote MCP · Endpoint

PacketStream MCP server

No. PacketStream answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://api.packetstream.io/v1/mcp

The last check completed an MCP handshake.

Registry name
io.packetstream/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
236 ms
Tools exposed
2 tools
Uptime, last 30 days
4 checks from 4 checks
Described by its publisher as
Live web search results and web pages as Markdown; page fetches use a residential network.
Listing
From the official MCP registry (active).
Recent checks of PacketStream
CheckedResultHandshake
43 minutes agoHandshake completed236 ms
10 days agoHandshake completed208 ms
10 days agoHandshake completed209 ms
11 days agoHandshake completed259 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 PacketStream and makes no claim about it beyond what these checks measured.