Remote MCP · Endpoint

dev.rendraputra/100pro-token-risk MCP server

No. dev.rendraputra/100pro-token-risk answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://x402.rendraputra.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.rendraputra/100pro-token-risk
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
774 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Read-only risk tools: token screen, contract source, wallet. $0.10 USDC on Base.
Listing
From the official MCP registry (active).
Recent checks of dev.rendraputra/100pro-token-risk
CheckedResultHandshake
1 hour agoHandshake completed774 ms
1 day agoHandshake completed945 ms
2 days agoHandshake completed747 ms
3 days agoHandshake completed734 ms
4 days agoHandshake completed757 ms
5 days agoHandshake completed737 ms
6 days agoHandshake completed883 ms
9 days agoHandshake completed781 ms
11 days agoHandshake completed835 ms
14 days agoHandshake completed716 ms
16 days agoHandshake completed743 ms
18 days agoHandshake completed741 ms
20 days agoHandshake completed3.89 s
22 days agoHandshake completed802 ms
24 days agoHandshake completed736 ms
26 days agoHandshake completed734 ms
27 days agoHandshake completed775 ms
29 days agoHandshake completed795 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 28 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 dev.rendraputra/100pro-token-risk and makes no claim about it beyond what these checks measured.