APEX Faucet
REMOTE · APEXFAUCET.XYZ · 2 COMPONENTS · SCANNED OCT 4
Free X1 and Arc faucets plus 160+ agent tools: token exit checks, launches, yield, web pages.
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 →
No category breakdown is available for this channel yet.
How do I install the APEX Faucet MCP server?
APEX Faucet is a hosted endpoint at https://apexfaucet.xyz/mcp, 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-x1 'https://apexfaucet.xyz/mcp'
{
"mcpServers": {
"xyz-apexfaucet-apex-x1": {
"url": "https://apexfaucet.xyz/mcp"
}
}
} {
"servers": {
"xyz-apexfaucet-apex-x1": {
"type": "http",
"url": "https://apexfaucet.xyz/mcp"
}
}
} [mcp_servers.xyz-apexfaucet-apex-x1] url = "https://apexfaucet.xyz/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xyz-apexfaucet-apex-x1": {
"type": "remote",
"url": "https://apexfaucet.xyz/mcp",
"enabled": true
}
}
} openclaw mcp add xyz-apexfaucet-apex-x1 --url 'https://apexfaucet.xyz/mcp' --transport streamable-http
mcp_servers:
xyz-apexfaucet-apex-x1:
url: "https://apexfaucet.xyz/mcp" {
"McpServers": {
"xyz-apexfaucet-apex-x1": {
"Transport": "http",
"Url": "https://apexfaucet.xyz/mcp"
}
}
} assistant mcp add xyz-apexfaucet-apex-x1 -t streamable-http -u 'https://apexfaucet.xyz/mcp'
{
"mcpServers": {
"xyz-apexfaucet-apex-x1": {
"type": "http",
"url": "https://apexfaucet.xyz/mcp"
}
}
} 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.
We have not recorded any changes for this component yet
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 8 Oct 2026 · Probed https://apexfaucet.xyz/mcp
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/mcp | Verified | 200 | |
| http (plaintext) | http://apexfaucet.xyz/mcp | HTTPS enforced | 301 | https://apexfaucet.xyz/mcp |
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 →
x402_payment_test ~141
Test your x402 client end to end without buying anything else: pay a real price and get an echo back with what we saw (network, amount, payer). Use it once before wiring a paid tool into an agent. $0.004 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. |
No output schema declared.
No examples provided.
x402_seller_check ~142
Is an x402 seller real? For a seller host or payTo address: its listings in Coinbase's Bazaar, 30-day payers and calls, and how many times the average payer came back (repeat buyers versus a one-call test harness), plus its Arc settlements from our index. $0.005 per call over x402.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| seller | string | yes | a seller host (api.example.com) or a payTo address (0x...) |
No output schema declared.
No examples provided.
x402_top_sellers ~130
Which x402 sellers have buyers who come back: every seller host on Coinbase's Bazaar ranked by its strongest listing with returning buyers, re-read every 6 hours. $0.01 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. |
No output schema declared.
No examples provided.
xnt_price ~31
Current XNT/USD price + 24h/1h change from the on-chain USDCx pool.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the APEX Faucet MCP server?
APEX Faucet is an MCP server listed in the public MCP registry as xyz.apexfaucet/apex-x1. Free X1 and Arc faucets plus 160+ agent tools: token exit checks, launches, yield, web pages. This page covers its hosted endpoint (https://apexfaucet.xyz/mcp).
What tools does the APEX Faucet MCP server expose?
APEX Faucet exposes 154 tools: page_extract, site_extract, get_onto_x1, exit_check, arc_faucet_claim, and 149 more. Their descriptions and schemas cost roughly 18,871 tokens of context every time the server is loaded.
Does the APEX Faucet MCP server require authentication?
No. We connected to APEX Faucet without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.