Remote MCP · Endpoint

TokenSafe by PromptVault MCP server

No. TokenSafe by PromptVault answered an MCP handshake 4 hours ago.

UpLast checked 4 hours ago

Server URL

https://promptvault-x402.onrender.com/mcp

The last check completed an MCP handshake.

Registry name
com.onrender.promptvault-x402/tokensafe
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
132 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Free token risk check (Base/Solana) + info on paid x402 reports. Not financial advice.
Listing
From the official MCP registry (active).
Recent checks of TokenSafe by PromptVault
CheckedResultHandshake
4 hours agoHandshake completed132 ms
10 days agoHandshake completed314 ms
11 days agoHandshake completed172 ms
11 days agoHandshake completed282 ms
13 days agoHandshake completed295 ms
14 days agoHandshake completed127 ms
15 days agoHandshake completed116 ms
16 days agoHandshake completed138 ms
17 days agoHandshake completed130 ms
19 days agoHandshake completed330 ms
22 days agoHandshake completed148 ms
24 days agoHandshake completed263 ms
26 days agoHandshake completed319 ms
29 days agoHandshake completed132 ms

The last 14 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 TokenSafe by PromptVault and makes no claim about it beyond what these checks measured.