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
3.89 s
Tools exposed
3 tools
Uptime, last 30 days
94.1% from 17 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 completed3.89 s
2 days agoHandshake completed802 ms
4 days agoHandshake completed736 ms
5 days agoHandshake completed734 ms
7 days agoHandshake completed775 ms
8 days agoHandshake completed795 ms
9 days agoHandshake completed754 ms
12 days agoHandshake completed729 ms
13 days agoHandshake completed729 ms
15 days agoHandshake completed775 ms
17 days agoHandshake completed740 ms
18 days agoHandshake completed739 ms
19 days agoHandshake completed735 ms
20 days agoHandshake completed1.13 s
20 days agoHandshake completed777 ms
21 days agoFailed - the request timed out—
22 days agoHandshake completed797 ms

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