Remote MCP · Endpoint

com.kenoodl/verify MCP server

No. com.kenoodl/verify answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://kenoodl.com/mcp

The last check completed an MCP handshake.

Registry name
com.kenoodl/verify
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
97 ms
Tools exposed
31 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Runs your code against a contract; HELD or BROKE at the exact input. Deterministic. 0.10 USDC/call.
Listing
From the official MCP registry (active).
Recent checks of com.kenoodl/verify
CheckedResultHandshake
1 hour agoHandshake completed97 ms
18 hours agoHandshake completed96 ms
2 days agoHandshake completed90 ms
3 days agoHandshake completed101 ms
4 days agoHandshake completed111 ms
5 days agoHandshake completed221 ms
6 days agoHandshake completed148 ms
7 days agoHandshake completed159 ms
10 days agoHandshake completed116 ms
13 days agoHandshake completed185 ms
15 days agoHandshake completed165 ms
17 days agoHandshake completed211 ms
19 days agoHandshake completed123 ms
21 days agoHandshake completed117 ms
23 days agoHandshake completed108 ms
25 days agoHandshake completed181 ms
27 days agoHandshake completed43 ms
28 days agoHandshake completed262 ms
29 days agoHandshake completed365 ms

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

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