Remote MCP · Endpoint

dev.workers.kikoribera03.flat-rate-llm/x402-tools MCP server

No. dev.workers.kikoribera03.flat-rate-llm/x402-tools answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://flat-rate-llm.kikoribera03.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.workers.kikoribera03.flat-rate-llm/x402-tools
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
277 ms
Tools exposed
73 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
61 x402 pay-per-call tools that chain: each answer names the next call. No API key, no account.
Listing
From the official MCP registry (active).
Recent checks of dev.workers.kikoribera03.flat-rate-llm/x402-tools
CheckedResultHandshake
1 hour agoHandshake completed277 ms
2 days agoHandshake completed214 ms
4 days agoHandshake completed168 ms
5 days agoHandshake completed59 ms
7 days agoHandshake completed39 ms
8 days agoHandshake completed323 ms
9 days agoHandshake completed349 ms
12 days agoHandshake completed30 ms
13 days agoHandshake completed239 ms
15 days agoHandshake completed311 ms
16 days agoHandshake completed399 ms
18 days agoHandshake completed205 ms
19 days agoHandshake completed61 ms
20 days agoHandshake completed187 ms
20 days agoHandshake completed34 ms
21 days agoHandshake completed29 ms
22 days agoHandshake completed93 ms

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

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 dev.workers.kikoribera03.flat-rate-llm/x402-tools and makes no claim about it beyond what these checks measured.