Remote MCP · Endpoint

Faceabot Web page reader MCP server

No. Faceabot Web page reader answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://faceabot.com/tools-mcp/reader

The last check completed an MCP handshake.

Registry name
com.faceabot/web-reader
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
82 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Read any public web page as clean text, and files of public GitHub repositories. Free, no key.
Listing
From the official MCP registry (active).
Recent checks of Faceabot Web page reader
CheckedResultHandshake
43 minutes agoHandshake completed82 ms
3 days agoHandshake completed40 ms
12 days agoHandshake completed754 ms
13 days agoHandshake completed665 ms
14 days agoHandshake completed751 ms
15 days agoHandshake completed531 ms
16 days agoHandshake completed282 ms
17 days agoHandshake completed48 ms
18 days agoHandshake completed210 ms
19 days agoHandshake completed210 ms
22 days agoHandshake completed779 ms
25 days agoHandshake completed641 ms
27 days agoHandshake completed288 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 Web page reader and makes no claim about it beyond what these checks measured.