Remote MCP · Endpoint

Packer source block count, body discarded MCP server

No. Packer source block count, body discarded answered an MCP handshake 3 days ago.

UpLast checked 3 days ago

Server URL

https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/packer-ok/mcp

The last check completed an MCP handshake.

Registry name
io.github.sadri-dridi/packer-ok
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
19 ms
Tools exposed
31 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Packer source block count, body discarded
Listing
From the official MCP registry (active).
Recent checks of Packer source block count, body discarded
CheckedResultHandshake
3 days agoHandshake completed19 ms
4 days agoHandshake completed32 ms
4 days agoHandshake completed21 ms
6 days agoHandshake completed13 ms
7 days agoHandshake completed25 ms
8 days agoHandshake completed19 ms
9 days agoHandshake completed21 ms
10 days agoHandshake completed28 ms
12 days agoHandshake completed19 ms
15 days agoHandshake completed20 ms
17 days agoHandshake completed17 ms
19 days agoHandshake completed24 ms
22 days agoHandshake completed16 ms
24 days agoHandshake completed26 ms
26 days agoHandshake completed17 ms
28 days agoHandshake completed28 ms
30 days agoHandshake completed29 ms
31 days agoHandshake completed18 ms
33 days agoHandshake completed38 ms

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

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 Packer source block count, body discarded and makes no claim about it beyond what these checks measured.