Remote MCP · Endpoint

KushBitx AgentProof MCP server

No. KushBitx AgentProof answered an MCP handshake 33 minutes ago.

UpLast checked 33 minutes ago

Server URL

https://kushbitx.com/mcp

The last check completed an MCP handshake.

Registry name
com.kushbitx/agentproof
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
160 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Safety checks for AI agents paying on Base: free SpendGuard, paid x402 token risk and preflight.
Listing
From the official MCP registry (active).
Recent checks of KushBitx AgentProof
CheckedResultHandshake
33 minutes agoHandshake completed160 ms
3 days agoHandshake completed205 ms
13 days agoHandshake completed138 ms
13 days agoHandshake completed154 ms
15 days agoHandshake completed132 ms
16 days agoHandshake completed96 ms
17 days agoHandshake completed122 ms
18 days agoHandshake completed94 ms
18 days agoHandshake completed101 ms
20 days agoHandshake completed132 ms
22 days agoHandshake completed158 ms
25 days agoHandshake completed124 ms
27 days agoHandshake completed236 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 KushBitx AgentProof and makes no claim about it beyond what these checks measured.