mcpbeat Sign in

APEX web reader MCP Server

by apexfaucet Your server? Claim it
answering

APEX web reader is answering right now. Last checked 13 min ago. It exposes 3 tools.

A real browser for your agent: a page to clean text for $0.009, a 25-page site for $0.14. x402.

Uptime history 18 days of history · worst day 0%
18 days agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
222 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 3

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 25 September 2026. No other catalogue keeps this.

25 Sep 2 tool descriptions were rewritten page_extract, site_extract
25 Sep a tool appeared web_read

APEX web reader does not always answer

Over the last week it answered 82.7% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add apex-web --transport http https://apexfaucet.xyz/api/mcp/web
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "apex-web": {
      "url": "https://apexfaucet.xyz/api/mcp/web"
    }
  }
}
~/.codex/config.toml
[mcp_servers.apex-web]
url = "https://apexfaucet.xyz/api/mcp/web"
.cursor/mcp.json
{
  "mcpServers": {
    "apex-web": {
      "url": "https://apexfaucet.xyz/api/mcp/web"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "apex-web": {
      "url": "https://apexfaucet.xyz/api/mcp/web"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

page
page_extract
Render any public web page in a real headless Chrome and return its text. JavaScript runs first, so docs sites and single-page apps that a plain fetch returns empty come back complete. $0.009 per call (x402 on Arc/Base/Solana/X1): the full text and every outbound link. Without a payment the call returns the price and every rail we accept. Refuses private and reserved addresses and our own hosts, so it cannot be used as a proxy into a network. Sites that put a bot wall in front of their pages (Cloudflare, DataDome and the like) answer with a challenge rather than the page: the call then FAILS with `http-403` or `bot-challenge` and says so, rather than charging you for a spinner.
site
site_extract
Render a whole section of a site - up to 25 pages - in one call and get every page back as clean text, with JavaScript executed. Same host only; robots.txt is obeyed and anything it disallows is skipped and named. FREE: the crawl PLAN - exactly which pages would be fetched and what robots.txt allows - so you can see what you would get before paying. PAID ($0.14, x402 on Arc/Base/Solana/X1): every page rendered and returned. It costs more than one page because it is up to 25 real browser renders, not a lookup. If a bot wall on the site lets the first page through but blocks the rest, the call fails with `poor-yield` and names every page it could not render, instead of billing you for a list of failures.
web
web_read
Read up to 10 web pages as clean text in one call: title, description and readable body, with the final URL. A plain fetch (no JavaScript); for a rendered page use page_extract. $0.003 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without `payment` for the terms, sign them with your own wallet, call again with `payment`.

Endpoints

URLTransportStateLatencyChecked
https://apexfaucet.xyz/api/mcp/web streamable-http answering 537 ms 13 min ago

Alternatives to APEX web reader

same job, measured the same way
Browsentic
by imshaikot

Agentic browser harness: your agent CLI in your real, signed-in browser, from a side panel or MCP.

615 installs/wk local only
Val
by nyx-intelligence

QA agent for vibecoded apps. Real browser checks, your AI fixes them. Ship to green.

25 installs/wk local only
Pagewatch
by pagelens

Read a URL as clean markdown, screenshot a website, url to PDF. Web access for agents, no signup.

75 installs/wk 5 tools answering
oassis — web for agents
by oassis

Read, map and crawl the web, and drive a real browser. Pay per call, no key, no signup.

14 tools answering
Wick
by wickproject

Browser-grade web access for AI agents. Fetches any webpage, returns clean markdown.

47 installs/wk local only
Wick
by myleshorton

Browser-grade web access for AI agents. Fetches any webpage, returns clean markdown.

local only
Feedthrough
by feedthrough

Debug bridge inside your web app: an agent reads the DOM, console and network. Any browser.

102 installs/wk local only
WebPeel
by jakeliume

Fetch any web page as clean, AI-ready markdown with smart HTTP-to-browser escalation.

274 installs/wk local only

APEX web reader — questions

Answers built from our own checks of this server.

What can APEX web reader do?
It exposes 3 tools, read directly from the server on our last check. Among them: page_extract, site_extract, web_read. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is APEX web reader working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 222 ms. The bar chart above shows every period we have measured.
How do I connect APEX web reader?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does APEX web reader need an API key?
No. APEX web reader completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is APEX web reader?
It answers our handshake in 222 ms on average, which is faster than 59% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.