Remote MCP · Endpoint

Faceabot PDF text extractor MCP server

No. Faceabot PDF text extractor answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://pdf.faceabot.com/mcp

The last check completed an MCP handshake.

Registry name
com.faceabot/pdf
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
200 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Read the text of any public PDF, page by page, plus page count and metadata. Free, no key.
Listing
From the official MCP registry (active).
Recent checks of Faceabot PDF text extractor
CheckedResultHandshake
42 minutes agoHandshake completed200 ms
3 days agoHandshake completed360 ms
12 days agoHandshake completed113 ms
12 days agoHandshake completed91 ms
14 days agoHandshake completed193 ms
15 days agoHandshake completed442 ms
16 days agoHandshake completed129 ms
17 days agoHandshake completed99 ms
18 days agoHandshake completed112 ms
19 days agoHandshake completed160 ms
22 days agoHandshake completed114 ms
25 days agoHandshake completed88 ms
27 days agoHandshake completed171 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 Faceabot PDF text extractor and makes no claim about it beyond what these checks measured.