Remote MCP · Endpoint

well-005-csv-to-table MCP server

No. well-005-csv-to-table answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://well-005-csv-to-table.rainmaker-wells.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.workers.rainmaker-wells.well-005-csv-to-table/csv-to-table
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
120 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
https CSV to headers and rows. x402 $0.005 USDC, Base. As is, no warranty.
Listing
From the official MCP registry (active).
Recent checks of well-005-csv-to-table
CheckedResultHandshake
44 minutes agoHandshake completed120 ms
3 days agoHandshake completed478 ms
12 days agoHandshake completed370 ms
13 days agoHandshake completed312 ms
14 days agoHandshake completed555 ms
15 days agoHandshake completed548 ms
16 days agoHandshake completed515 ms
17 days agoHandshake completed453 ms
18 days agoHandshake completed382 ms
19 days agoHandshake completed845 ms
22 days agoHandshake completed525 ms
25 days agoHandshake completed227 ms
27 days agoHandshake completed64 ms

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

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 well-005-csv-to-table and makes no claim about it beyond what these checks measured.