Remote MCP · Endpoint

mcp-x402 — MCP server for agents with autonomous USDC/RLUSD payments MCP server

No. mcp-x402 — MCP server for agents with autonomous USDC/RLUSD payments answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.Timwal78/mcp-x402
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
294 ms
Tools exposed
3 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
85+ pay-per-call MCP tools: trading, federal grants/contracts, SEC, FTD. x402 USDC/RLUSD. No keys.
Repository
https://github.com/timwal78/SML_Portfolio
Listing
From the official MCP registry (active).
Recent checks of mcp-x402 — MCP server for agents with autonomous USDC/RLUSD payments
CheckedResultHandshake
1 hour agoHandshake completed294 ms
1 day agoHandshake completed352 ms
2 days agoHandshake completed116 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with mcp-x402 — MCP server for agents with autonomous USDC/RLUSD payments and makes no claim about it beyond what these checks measured.