Remote MCP · Endpoint

Behalf (PXP v0) MCP server

No. Behalf (PXP v0) answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://behalf.dropkit.sh/mcp

The last check completed an MCP handshake.

Registry name
io.github.JulesNsenda/behalf
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
324 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Negotiate for your human under PXP: tagged claims, escalation, decision brief, hash-chained ledger
Listing
From the official MCP registry (active).
Recent checks of Behalf (PXP v0)
CheckedResultHandshake
1 hour agoHandshake completed324 ms
1 day agoHandshake completed333 ms
4 days agoHandshake completed302 ms
6 days agoHandshake completed299 ms
9 days agoHandshake completed340 ms
11 days agoHandshake completed298 ms
13 days agoHandshake completed325 ms
15 days agoHandshake completed329 ms
17 days agoHandshake completed303 ms
19 days agoHandshake completed312 ms
21 days agoHandshake completed298 ms
22 days agoHandshake completed319 ms
23 days agoHandshake completed306 ms

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

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 Behalf (PXP v0) and makes no claim about it beyond what these checks measured.