Remote MCP · Endpoint
Web Content Extract Mcp MCP server
No. Web Content Extract Mcp answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://web-content-extract-mcp.mcpize.run/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.varvararatta/web_content_extract_mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 893 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 4 checks from 4 checks
- Described by its publisher as
- Web Content Extract Mcp connects AI agents to real public APIs via MCP. Tools include
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 893 ms |
| 10 hours ago | Handshake completed | 459 ms |
| 1 day ago | Handshake completed | 1.97 s |
| 2 days ago | Handshake completed | 516 ms |
The last 4 checks. Full history is kept for 30 days; the all-time counter stands at 4 responding of 4.
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 Web Content Extract Mcp and makes no claim about it beyond what these checks measured.