# xyz.apexfaucet/apex-web (remote · apexfaucet.xyz)

A real browser for your agent: a page for $0.009, or 25 pages of a site for $0.14, via x402.

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-29

## Components

- remote · `apexfaucet.xyz`: 64/100 (this document), [markdown](https://verifymcp.io/servers/xyz-apexfaucet-apex-web/api-mcp-web.md), [page](https://verifymcp.io/servers/xyz-apexfaucet-apex-web/api-mcp-web)

## Channel facts

- Endpoint: `https://apexfaucet.xyz/api/mcp/web`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-29.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 788 tokens (~262/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the xyz.apexfaucet/apex-web MCP server?

xyz.apexfaucet/apex-web is a hosted endpoint at https://apexfaucet.xyz/api/mcp/web, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http xyz-apexfaucet-apex-web 'https://apexfaucet.xyz/api/mcp/web'
```

### Cursor

```json
{
  "mcpServers": {
    "xyz-apexfaucet-apex-web": {
      "url": "https://apexfaucet.xyz/api/mcp/web"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "xyz-apexfaucet-apex-web": {
      "type": "http",
      "url": "https://apexfaucet.xyz/api/mcp/web"
    }
  }
}
```

### Codex

```toml
[mcp_servers.xyz-apexfaucet-apex-web]
url = "https://apexfaucet.xyz/api/mcp/web"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xyz-apexfaucet-apex-web": {
      "type": "remote",
      "url": "https://apexfaucet.xyz/api/mcp/web",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add xyz-apexfaucet-apex-web --url 'https://apexfaucet.xyz/api/mcp/web' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  xyz-apexfaucet-apex-web:
    url: "https://apexfaucet.xyz/api/mcp/web"
```

### Netclaw

```json
{
  "McpServers": {
    "xyz-apexfaucet-apex-web": {
      "Transport": "http",
      "Url": "https://apexfaucet.xyz/api/mcp/web"
    }
  }
}
```

### Vellum

```bash
assistant mcp add xyz-apexfaucet-apex-web -t streamable-http -u 'https://apexfaucet.xyz/api/mcp/web'
```

### Other

```json
{
  "mcpServers": {
    "xyz-apexfaucet-apex-web": {
      "type": "http",
      "url": "https://apexfaucet.xyz/api/mcp/web"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-29 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-28 (score 63, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-25 (score 62, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 61)

First indexed and scored.

## MCP tools (3)

### `page_extract` (~269 tokens)

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.

Input parameters:

- `full` (boolean): true asks for the paid full text. Without a payment you get a 402 carrying the price and every rail we accept; sign it and call again with `payment`.
- `payment` (string): a signed x402 payment (the same base64 payload you would put in the PAYMENT-SIGNATURE header). Pass it here and the purchase completes inside this tool call - you never have to leave MCP.
- `url` (string, required): the http(s) page to render

### `site_extract` (~286 tokens)

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.

Input parameters:

- `full` (boolean): true asks for the paid crawl. Without a payment you get a 402 carrying the price and every rail we accept; sign it and call again with `payment`.
- `pages` (number): how many pages, default 10, hard cap 25
- `payment` (string): a signed x402 payment (the same base64 payload you would put in the PAYMENT-SIGNATURE header). Pass it here and the purchase completes inside this tool call.
- `url` (string, required): the page to start from

### `web_read` (~151 tokens)

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`.

Input parameters:

- `payment` (string): a signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.
- `urls` (string, required): comma-separated URLs, up to 10

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/xyz-apexfaucet-apex-web/api-mcp-web#diagnostics

## Score history

- 2026-09-29: 64
- 2026-09-28: 63
- 2026-09-27: 63
- 2026-09-26: 62
- 2026-09-25: 62
- 2026-09-24: 61

## Common questions

### What is the xyz.apexfaucet/apex-web MCP server?

xyz.apexfaucet/apex-web is an MCP server listed in the public MCP registry as xyz.apexfaucet/apex-web. A real browser for your agent: a page for $0.009, or 25 pages of a site for $0.14, via x402. This page covers its hosted endpoint (https://apexfaucet.xyz/api/mcp/web).

### Is the xyz.apexfaucet/apex-web MCP server safe to use?

xyz.apexfaucet/apex-web scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the xyz.apexfaucet/apex-web MCP server expose?

xyz.apexfaucet/apex-web exposes 3 tools: page_extract, site_extract, web_read. Their descriptions and schemas cost roughly 706 tokens of context every time the server is loaded.

### Does the xyz.apexfaucet/apex-web MCP server require authentication?

No. We connected to xyz.apexfaucet/apex-web without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the xyz.apexfaucet/apex-web MCP server still maintained?

xyz.apexfaucet/apex-web is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://apexfaucet.xyz/api/mcp/web
- Website: https://github.com/apexfaucet-hub/apex-x1-mcp
- Changelog RSS feed: https://verifymcp.io/servers/xyz-apexfaucet-apex-web/api-mcp-web.xml
- Changelog JSON feed: https://verifymcp.io/servers/xyz-apexfaucet-apex-web/api-mcp-web.json
- HTML version of this page: https://verifymcp.io/servers/xyz-apexfaucet-apex-web/api-mcp-web