Remote MCP · Endpoint

WalletProfit MCP server

No. WalletProfit answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://walletprofit.app/mcp

The last check completed an MCP handshake.

Registry name
app.walletprofit/walletprofit
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
169 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Analyse crypto wallets (EVM, Solana, Bitcoin) and compare DeFi lending, borrowing and pool rates.
Listing
From the official MCP registry (active).
Recent checks of WalletProfit
CheckedResultHandshake
2 hours agoHandshake completed169 ms
1 day agoHandshake completed177 ms
3 days agoHandshake completed277 ms
3 days agoHandshake completed148 ms
4 days agoHandshake completed162 ms
5 days agoHandshake completed442 ms
7 days agoHandshake completed320 ms
10 days agoHandshake completed317 ms
12 days agoHandshake completed281 ms
15 days agoHandshake completed321 ms
17 days agoHandshake completed308 ms
19 days agoHandshake completed239 ms
21 days agoHandshake completed172 ms
23 days agoHandshake completed186 ms
25 days agoHandshake completed1.47 s

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

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