Remote MCP · Endpoint

well-001-extract-table MCP server

No. well-001-extract-table answered an MCP handshake 45 minutes ago.

UpLast checked 45 minutes ago

Server URL

https://well-001-extract-table.rainmaker-wells.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.workers.rainmaker-wells.well-001-extract-table/extract-table-from-pdf
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
447 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Extract tables from a PDF. x402 $0.01 USDC, Base. As is, no warranty.
Listing
From the official MCP registry (active).
Recent checks of well-001-extract-table
CheckedResultHandshake
45 minutes agoHandshake completed447 ms
3 days agoHandshake completed975 ms
12 days agoHandshake completed969 ms
13 days agoHandshake completed693 ms
14 days agoHandshake completed469 ms
15 days agoHandshake completed1.09 s
16 days agoHandshake completed658 ms
17 days agoHandshake completed463 ms
18 days agoHandshake completed403 ms
19 days agoHandshake completed474 ms
22 days agoHandshake completed542 ms
25 days agoHandshake completed664 ms
27 days agoHandshake completed1.03 s

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-001-extract-table and makes no claim about it beyond what these checks measured.