Remote MCP · Endpoint

PJELLY Deals MCP server

No. PJELLY Deals answered an MCP handshake 16 minutes ago.

UpLast checked 16 minutes ago

Server URL

https://www.peanutbutterjelly.io/mcp

The last check completed an MCP handshake.

Registry name
io.peanutbutterjelly/deals
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
811 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Honest buying guides for crypto exchanges and hardware wallets, with disclosed affiliate links.
Listing
From the official MCP registry (active).
Recent checks of PJELLY Deals
CheckedResultHandshake
16 minutes agoHandshake completed811 ms
8 days agoHandshake completed796 ms
9 days agoHandshake completed521 ms
11 days agoHandshake completed680 ms
12 days agoHandshake completed994 ms
13 days agoHandshake completed698 ms
14 days agoHandshake completed918 ms
14 days agoHandshake completed709 ms
16 days agoHandshake completed866 ms
19 days agoHandshake completed976 ms
21 days agoHandshake completed1.72 s
24 days agoHandshake completed2.48 s
26 days agoHandshake completed1.35 s
28 days agoHandshake completed1.48 s

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