Remote MCP · Endpoint

Jmpr MCP server

No. Jmpr answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/jmpr/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/jmpr
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
100 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
JMPR — the Joint FAO/WHO Meeting on Pesticide Residues.
Listing
From the official MCP registry (active).
Recent checks of Jmpr
CheckedResultHandshake
1 hour agoHandshake completed100 ms
1 day agoHandshake completed145 ms
2 days agoHandshake completed95 ms
3 days agoHandshake completed99 ms
4 days agoHandshake completed89 ms
5 days agoHandshake completed159 ms
7 days agoHandshake completed92 ms
9 days agoHandshake completed656 ms
11 days agoHandshake completed101 ms
14 days agoHandshake completed135 ms
16 days agoHandshake completed54 ms
18 days agoHandshake completed56 ms
20 days agoHandshake completed177 ms
22 days agoHandshake completed59 ms
24 days agoHandshake completed61 ms
26 days agoHandshake completed52 ms
27 days agoHandshake completed71 ms
29 days agoHandshake completed225 ms

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