xyz.apexfaucet/apex-web
REMOTE · APEXFAUCET.XYZ · SCANNED SEP 29
A real browser for your agent: a page for $0.009, or 25 pages of a site for $0.14, via x402.
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
remote · apexfaucet.xyz
claude mcp add --transport http xyz-apexfaucet-apex-web 'https://apexfaucet.xyz/api/mcp/web'
{
"mcpServers": {
"xyz-apexfaucet-apex-web": {
"url": "https://apexfaucet.xyz/api/mcp/web"
}
}
} {
"servers": {
"xyz-apexfaucet-apex-web": {
"type": "http",
"url": "https://apexfaucet.xyz/api/mcp/web"
}
}
} [mcp_servers.xyz-apexfaucet-apex-web] url = "https://apexfaucet.xyz/api/mcp/web"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xyz-apexfaucet-apex-web": {
"type": "remote",
"url": "https://apexfaucet.xyz/api/mcp/web",
"enabled": true
}
}
} openclaw mcp add xyz-apexfaucet-apex-web --url 'https://apexfaucet.xyz/api/mcp/web' --transport streamable-http
mcp_servers:
xyz-apexfaucet-apex-web:
url: "https://apexfaucet.xyz/api/mcp/web" {
"McpServers": {
"xyz-apexfaucet-apex-web": {
"Transport": "http",
"Url": "https://apexfaucet.xyz/api/mcp/web"
}
}
} assistant mcp add xyz-apexfaucet-apex-web -t streamable-http -u 'https://apexfaucet.xyz/api/mcp/web'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 29 Sept 26 +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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 29 Sept 2026 · Probed https://apexfaucet.xyz/api/mcp/web
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=apexfaucet.xyz | CN=WE1,O=Google Trust Services,C=US | 17 Sept 2026 | 16 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d70d658fe7f58f0f13c98934bfd25dfc |
| SANs: apexfaucet.xyz, *.apexfaucet.xyz | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of apexfaucet.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| apexfaucet.xyz. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | frame-ancestors 'self'; base-uri 'self'; object-src 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(self), geolocation=(self) |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://apexfaucet.xyz/api/mcp/web | Verified | 200 | |
| http (plaintext) | http://apexfaucet.xyz/api/mcp/web | HTTPS enforced | 301 | https://apexfaucet.xyz/api/mcp/web |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
page_extract ~269
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | the http(s) page to render |
No output schema declared.
No examples provided.
site_extract ~286
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | the page to start from |
No output schema declared.
No examples provided.
web_read ~151
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | comma-separated URLs, up to 10 |
No output schema declared.
No examples provided.
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.