Remote MCP · Endpoint

Kawal MCP server

No. Kawal answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://kawal-three.vercel.app/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.PugarHuda/kawal
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
466 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Evidence about ERC-8004 agents on BNB Smart Chain, gathered by calling them. No key.
Listing
From the official MCP registry (active).
Recent checks of Kawal
CheckedResultHandshake
1 hour agoHandshake completed466 ms
2 days agoHandshake completed148 ms
4 days agoHandshake completed864 ms
5 days agoHandshake completed147 ms
7 days agoHandshake completed419 ms
8 days agoHandshake completed380 ms
9 days agoHandshake completed407 ms
12 days agoHandshake completed322 ms
13 days agoHandshake completed407 ms
15 days agoHandshake completed1.28 s
17 days agoHandshake completed1.18 s
18 days agoHandshake completed1.56 s
19 days agoHandshake completed1.30 s
20 days agoHandshake completed386 ms
20 days agoHandshake completed333 ms
21 days agoHandshake completed325 ms
22 days agoHandshake completed345 ms

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

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