Remote MCP · Endpoint

WebExtract MCP server

No. WebExtract answered an MCP handshake 4 days ago.

UpLast checked 4 days ago

Server URL

https://api.webextract.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.webextract/extract
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
673 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Web page to clean Markdown or fixed-schema JSON (product/price, tables). Free 20 calls/day.
Website
https://webextract.dev/
Listing
From the official MCP registry (active).
Recent checks of WebExtract
CheckedResultHandshake
4 days agoHandshake completed673 ms
4 days agoHandshake completed317 ms
5 days agoHandshake completed726 ms
7 days agoHandshake completed810 ms
8 days agoHandshake completed720 ms
9 days agoHandshake completed723 ms
10 days agoHandshake completed755 ms
11 days agoHandshake completed793 ms
12 days agoHandshake completed1.35 s
15 days agoHandshake completed695 ms
18 days agoHandshake completed1.82 s
20 days agoHandshake completed746 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with WebExtract and makes no claim about it beyond what these checks measured.