Remote MCP · Endpoint

PDF Table Extractor (Tanod) MCP server

No. PDF Table Extractor (Tanod) answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://tanod.dev/mcp/pdf-tables

The last check completed an MCP handshake.

Registry name
dev.tanod/pdf-tables
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
497 ms
Tools exposed
1 tool
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Pull tables out of a PDF as rows and cells, ready for a spreadsheet or a data pipeline.
Listing
From the official MCP registry (active).
Recent checks of PDF Table Extractor (Tanod)
CheckedResultHandshake
6 hours agoHandshake completed497 ms
10 days agoHandshake completed343 ms
11 days agoHandshake completed519 ms
11 days agoHandshake completed337 ms
13 days agoHandshake completed1.00 s
15 days agoHandshake completed311 ms
15 days agoHandshake completed315 ms
16 days agoHandshake completed308 ms
17 days agoHandshake completed317 ms
19 days agoFailed - the connection was refused or dropped—
22 days agoHandshake completed579 ms
24 days agoHandshake completed874 ms
27 days agoHandshake completed301 ms
29 days agoHandshake completed314 ms

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

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 PDF Table Extractor (Tanod) and makes no claim about it beyond what these checks measured.