Remote MCP · Endpoint

Crypto Bot Audit + Market Data (x402 paid) MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://labored-safari-islamic.ngrok-free.dev/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.github.kaminariouji/x402-audit-agent
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
146 tools
Uptime, last 30 days
50.0% from 18 checks
Described by its publisher as
x402 pay-per-call: 146 MCP tools, no account or key. USDC on Base + Solana, $0.001-$0.01/call.
Listing
From the official MCP registry (active).
Recent checks of Crypto Bot Audit + Market Data (x402 paid)
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
1 day agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
3 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
6 days agoFailed - the server returned an HTTP error—
9 days agoCredentials required—
11 days agoCredentials required—
14 days agoCredentials required—
16 days agoCredentials required—
18 days agoCredentials required—
20 days agoFailed - the connection was refused or dropped—
22 days agoCredentials required—
24 days agoHandshake completed524 ms
26 days agoHandshake completed507 ms
27 days agoFailed - the server returned an HTTP error—
29 days agoHandshake completed513 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 17 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 Crypto Bot Audit + Market Data (x402 paid) and makes no claim about it beyond what these checks measured.