Remote MCP · Endpoint

Axiom Solana Token Risk MCP server

No. Axiom Solana Token Risk answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://axiom-risk-mcp.vercel.app/mcp

The last check completed an MCP handshake.

Registry name
app.vercel.axiom-risk-mcp/solana-token-risk
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
87 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Solana SPL token risk checks: free preview tool plus links to paid x402 (USDC) full reports.
Listing
From the official MCP registry (active).
Recent checks of Axiom Solana Token Risk
CheckedResultHandshake
1 day agoHandshake completed87 ms
2 days agoHandshake completed136 ms
2 days agoHandshake completed117 ms
4 days agoHandshake completed83 ms
5 days agoHandshake completed60 ms
6 days agoHandshake completed77 ms
7 days agoHandshake completed66 ms
8 days agoHandshake completed320 ms
10 days agoHandshake completed145 ms
12 days agoHandshake completed69 ms
15 days agoHandshake completed104 ms
17 days agoHandshake completed62 ms
19 days agoHandshake completed129 ms
21 days agoHandshake completed121 ms

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

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