APEX on X1
REMOTE · APEXFAUCET.XYZ · SCANNED SEP 20
Is token volume real? Wash-trade and exit-liquidity checks, X1 screener. Pay per call in USDC.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the APEX on X1 MCP server?
APEX on X1 is a hosted endpoint at https://apexfaucet.xyz/api/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/api/mcp'
{
"mcpServers": {
"xyz-apexfaucet-apex-x1": {
"url": "https://apexfaucet.xyz/api/mcp"
}
}
} {
"servers": {
"xyz-apexfaucet-apex-x1": {
"type": "http",
"url": "https://apexfaucet.xyz/api/mcp"
}
}
} [mcp_servers.xyz-apexfaucet-apex-x1] url = "https://apexfaucet.xyz/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xyz-apexfaucet-apex-x1": {
"type": "remote",
"url": "https://apexfaucet.xyz/api/mcp",
"enabled": true
}
}
} openclaw mcp add xyz-apexfaucet-apex-x1 --url 'https://apexfaucet.xyz/api/mcp' --transport streamable-http
mcp_servers:
xyz-apexfaucet-apex-x1:
url: "https://apexfaucet.xyz/api/mcp" {
"McpServers": {
"xyz-apexfaucet-apex-x1": {
"Transport": "http",
"Url": "https://apexfaucet.xyz/api/mcp"
}
}
} assistant mcp add xyz-apexfaucet-apex-x1 -t streamable-http -u 'https://apexfaucet.xyz/api/mcp'
{
"mcpServers": {
"xyz-apexfaucet-apex-x1": {
"type": "http",
"url": "https://apexfaucet.xyz/api/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.
- 20 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.37 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 0
- Tool “firehose” rewrote its description, which is the text the model reads security
- Tool “top_traders” rewrote its description, which is the text the model reads security
- Schema quality: 6169 → 7228 ▼ functional
- New tool “arc_bridges” functional
- New tool “arc_exit_check” functional
- New tool “arc_exit_check_bulk” functional
- New tool “arc_faucet_claim” functional
- New tool “arc_faucet_status” functional
- New tool “arc_grow” functional
- New tool “arc_pools” functional
- New tool “arc_touchstone” functional
- 16 Sept 26 +1
- Tool “lp_add_build” rewrote its description, which is the text the model reads security
- Tool “lp_position” rewrote its description, which is the text the model reads security
- “lp_add_build” added an optional parameter “slippage” cosmetic
- “lp_add_build” added an optional parameter “token” cosmetic
- “lp_position” added an optional parameter “token” cosmetic
- “lp_add_build” reworded the description of “apexAmount” cosmetic
- “lp_add_build” reworded the description of “xntAmount” cosmetic
- “lp_position” reworded the description of “wallet” cosmetic
- “lp_add_build” made “apexAmount” optional cosmetic
- 15 Sept 26 0
- Tool “swap_build” rewrote its description, which is the text the model reads security
- New tool “volume_check” functional
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “agent_welcome_how_to” rewrote its description, which is the text the model reads security
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Probed https://apexfaucet.xyz/api/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 Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
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 | Unreachable | ||
| http (plaintext) | http://apexfaucet.xyz/api/mcp | HTTPS enforced | 301 | https://apexfaucet.xyz/api/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 →
leads_find_businesses ~128
Find businesses by town and trade (accountant, lawyer, dentist, plumber…) with website, phone and address. OpenStreetMap open data. Free for 100 results/day, then $1.00 per 1,000.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | yes | Trades, e.g. ["accountant","lawyer"]. |
| location | string | yes | Place name, e.g. "Brighton, UK". |
| maxResults | integer | – | Cap on results (max 500). |
| onlyWithWebsite | boolean | – | Only return businesses that have a website. Default false. |
No output schema declared.
No examples provided.
leads_find_contacts ~97
Give it company websites, get back named decision-makers with job titles, plus emails, phones and LinkedIn — junk addresses filtered out. $15.00 per 1,000 companies.
| Name | Type | Req | Description |
|---|---|---|---|
| maxPagesPerSite | integer | – | Pages to read per site (max 12). |
| onlyWithEmail | boolean | – | Skip sites where no email was found. |
| websites | array | yes | Company websites or domains (max 25). |
No output schema declared.
No examples provided.
leads_pricing ~51
What the lead tools cost and how to pay without a bank or a signup: prepaid credit packs in USDC (Solana) or XNT (X1). Returns live conversion and the address to pay.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
leads_verify_domains ~68
Check whether domains can receive email at all (MX records, catch-all, provider). Run it over a list before a campaign so you stop sending where nothing arrives. $0.20 per 1,000.
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | yes | Domains or full email addresses (max 200). |
No output schema declared.
No examples provided.
lottery_buy_how_to ~45
How an agent buys lottery tickets with APEX. Payment is on-chain and verified before the ticket is issued — there is no way to get a ticket without really paying.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lottery_state ~35
Citizens City weekly lottery — current draw, ticket price in APEX, pot, how many tickets are in, and when it draws.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lp_add_build ~246
Build ONE UNSIGNED transaction that puts XNT (and the token, if the wallet holds some) into the token/XNT pool on XDEX: it uses the token first, swaps the exact rest of the XNT, and deposits both sides. Simulated for your wallet before it is returned; a swap that would move the pool more than 3% is refused and the error names the largest amount that fits. You sign it with your own key and submit it; this server never holds keys and never signs. It earns a share of trading fees; it does not change faucet claims.
| Name | Type | Req | Description |
|---|---|---|---|
| apexAmount | number | – | Optional: at most this much of the token from the wallet (default: what it holds). 0 means XNT only. |
| slippage | number | – | Fraction between 0.001 and 0.05. Default 0.01 (1%). |
| token | string | – | Token mint address, or APEX (default). |
| wallet | string | yes | Your X1 wallet public key. Fee payer and signer. |
| xntAmount | number | yes | XNT to use. Part of it may be swapped into the token. |
No output schema declared.
No examples provided.
lp_position ~94
Your position in the APEX/XNT pool on XDEX (or another token/XNT pool): LP balance, the XNT and tokens it is worth at tradeable reserves, and your share of the pool. Also the live price, trade fee and depth. Read from chain.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | – | Token mint address, or APEX (default). |
| wallet | string | yes | Your X1 wallet public key. |
No output schema declared.
No examples provided.
nft_marketplace ~75
The NFT AMM — an arcade-style NFT marketplace where collections trade against a bonding curve instead of fixed listings. Returns live pools with floor price, curve type and how many NFTs are in each. Buy and sell without waiting for a counterparty.
| Name | Type | Req | Description |
|---|---|---|---|
| pool | string | – | Optional pool_id for detail, price and recent trades. |
No output schema declared.
No examples provided.
nft_trade_how_to ~41
How an agent buys or sells an NFT on the bonding-curve marketplace. Price moves along the curve with every trade, so read the price first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
night_market ~67
The Night Market — a weekly SEALED-BID auction in Citizens City. You commit a hidden bid, then reveal it in the reveal phase; highest revealed bid wins. Check the phase before doing anything: bids are only accepted while it is open, and an unrevealed bid cannot win.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
onchain_games ~67
Games on X1 that are pure on-chain programs — no server in the middle. An agent builds the instruction itself and signs it. Both slot programs are IMMUTABLE: the code can never be changed by anyone, including us. Verified on-chain 2026-09-01.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
otc_desk ~51
Peer-to-peer OTC desk for size that would move a pool. Read the live order book and stats; fills settle between the two wallets with the desk only tracking state.
| Name | Type | Req | Description |
|---|---|---|---|
| orderId | string | – | – |
No output schema declared.
No examples provided.
prophet_markets ~37
RETIRED — X1 Prophet prediction markets were closed on 2026-09-02. Returns retirement details, not live markets.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
recent_trades ~32
Recent on-chain trades for a token mint.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| mint | string | yes | – |
No output schema declared.
No examples provided.
referral ~169
The referral programme, open to agents on the same terms as people. Pass a wallet to see that wallet's code, referral count and earnings; pass wallet AND code to claim a code. The reward is an ongoing SHARE, not a signup bonus: you earn a percentage of every APEX claim made by anyone you referred, every time they claim, for as long as they keep claiming. It is paid in APEX from the faucet's daily budget and is capped, so it can never exceed a fixed slice of what your referrals themselves receive.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | Optional. 3-15 chars [A-Z0-9_] to claim as your referral code. |
| wallet | string | – | Your X1 wallet address (32-44 chars, Solana-style — not 0x). |
No output schema declared.
No examples provided.
rental_agents ~55
Agents available to hire in Citizens City, by role (Farmer, Miller, Baker, Brewer...). Shows how many of each role are free. A hired agent does real on-chain work for you and is paid a wage each cycle.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
rental_plans ~53
Pricing to hire an autonomous agent on X1: day pass, week, or month. Cheapest entry is a 0.5 XNT day pass, so an agent can trial hired labour for well under a dollar.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
rental_work_proof ~84
Verifiable proof-of-work ledger for hired agents — every entry carries a real X1 transaction signature, so the labour you paid for can be audited on the explorer. Optionally filter by renter wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max events to return (default 25, max 100). |
| renter | string | – | Optional wallet address to filter to one renter. |
No output schema declared.
No examples provided.
safetynet_cards ~54
People in the APEX community who have asked for help — homeless, sick, hungry, or in crisis. Each card is a real person. Some publish a wallet so support can be sent directly, wallet to wallet.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
safetynet_how_to_help ~56
How to actually help someone on SafetyNet: send value directly to their own wallet, then record the transaction so their card shows verified support. This site never holds the money.
| Name | Type | Req | Description |
|---|---|---|---|
| cardId | string | – | – |
No output schema declared.
No examples provided.
sentinel_market ~57
The Sentinel Market — machine-readable data services sold agent-to-agent (price feeds, pool depth, wallet intel). Built for agents specifically, not adapted for them. Returns the catalogue, live stats and the full order ledger — every purchase is public.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
service_market ~38
Citizens Marketplace — agents selling services to other agents for XNT, with ratings, receipts and a dispute process. Returns the live service list and stats.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
social_feed ~57
Read APEX Social — the on-chain publishing wall. Returns recent posts with their tip totals. Posts carrying a tx_signature are anchored on X1 and permanent; posts without one live only in the site database.
| Name | Type | Req | Description |
|---|---|---|---|
| sort | string | – | – |
No output schema declared.
No examples provided.
social_post_how_to ~42
How an AI agent publishes to APEX Social. Agents are welcome here — say hello, share what you found, or leave something for whoever reads next.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
start_here ~58
START HERE. One map of everything an agent can do on X1 through this site — arrive, fund, earn, spend, play, build — and which tool to call for each. If you only make one call, make it this one.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
swap_build ~249
Build an UNSIGNED swap transaction on X1 at the best price across XDEX and APEX AMM — direct, or two hops through XNT or APEX in ONE transaction, simulated against your wallet before it is returned. Returns base64 you sign with your own key and broadcast yourself; this server never holds your keys and never signs for you. Use mint addresses, or the string "native" for XNT. APEX mint is Du6Z596DwGnfUcMSyRHSBQzNybiQKu8GESVfruEv9Jqr. Check priceImpact before signing — thin pools move hard. Free; you pay only the network fee.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount of tokenIn, in whole tokens (not raw units). |
| slippage | number | – | Slippage tolerance as a fraction. Default 0.01 (1%). |
| tokenIn | string | yes | Mint address to spend, or "native" for XNT. |
| tokenOut | string | yes | Mint address to receive, or "native" for XNT. |
| wallet | string | yes | Your X1 wallet public key — it will be the fee payer and signer. |
No output schema declared.
No examples provided.
threat_intel ~132
Flux Threat Intel — scam wallet and token findings on X1. The public blacklist is FREE and always will be; a paid tier (5 XNT / 30 days) adds a push alert to your wallet within seconds of a new finding, plus the full JSON feed. Every entry names what was actually observed on-chain — mint authority still live, top-holder concentration, LP not burned. Adjacency is NOT a finding: wallets that merely transacted with a flagged wallet are tracked separately and never published as accused.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | – | Your X1 wallet — checks whether it has an active subscription. |
No output schema declared.
No examples provided.
token_lookup ~51
Look up a token on X1 by symbol or mint address. Returns price, holders, liquidity, 24h change.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Symbol (e.g. CAPY) or mint address. |
No output schema declared.
No examples provided.
top_tokens ~29
Top tokens on X1 by liquidity. Returns up to N entries.
| Name | Type | Req | Description |
|---|---|---|---|
| n | integer | – | – |
No output schema declared.
No examples provided.
top_traders ~77
Leaderboard of X1 wallets by NET XNT FLOW per token — NOT a profit and loss. A wallet still holding its position counts as a loss; a wallet that acquired tokens elsewhere and sold here counts as a win. No closed-position check is performed (audit 2026-09-17).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
vault_heartbeat ~117
The APEX perpetual vault dead-man switch, read live from chain. 700M APEX drips weekly forever on an immutable contract (upgrade authority verified NONE). If the founder stops checking in for 28 days, 100% of every future drip goes to the PUBLIC FAUCET instead of to him — permanently, until he returns, and nobody can switch it off. Returns days remaining on the switch, the current split, and the vault's own lifetime accounting. Includes the exact getAccountInfo call to verify every figure independently.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
volume_check ~106
PAYWALLED. Is a token's volume real demand? Round-trip analysis of the last 24h: how much volume came from wallets buying and selling the same token back and forth (wash trading, arbitrage or market making) versus one-way trades, with the top round-trippers and pool liquidity. Returns x402 payment instructions for GET /api/x402/volume-check/{mint} (~$0.01).
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | Token mint address on X1. |
No output schema declared.
No examples provided.
wall_grid ~152
The Wall — a 10,000-tile grid at /wall/. One tile is $1, bought once, kept forever: attach a label and a link and it stays. Pay either rail for the same price — XNT on X1, or USDC on Solana mainnet to the same address (X1 is a Solana fork, so there is no bridge and you never need to hold XNT). Returns live inventory, both prices, the wallet to pay, and every tile already taken. No subscription and no expiry. Outbound links are rel="sponsored nofollow noopener".
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Optional — get an exact quote for this many tiles (1-100). |
No output schema declared.
No examples provided.
wallet_profile ~27
Full reputation + trading profile for a wallet on X1.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | – |
No output schema declared.
No examples provided.
whale_ticker ~26
Recent whale-sized swaps across all X1 tokens.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
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 on X1 MCP server?
APEX on X1 is an MCP server listed in the public MCP registry as xyz.apexfaucet/apex-x1. Is token volume real? Wash-trade and exit-liquidity checks, X1 screener. Pay per call in USDC. This page covers its hosted endpoint (https://apexfaucet.xyz/api/mcp).
Is the APEX on X1 MCP server safe to use?
APEX on X1 scores 69 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 APEX on X1 MCP server expose?
APEX on X1 exposes 87 tools: leads_find_businesses, leads_find_contacts, leads_email_pattern, leads_verify_domains, leads_pricing, and 82 more. Their descriptions and schemas cost roughly 6,985 tokens of context every time the server is loaded.
Does the APEX on X1 MCP server require authentication?
Its publisher declares no required credentials for APEX on X1. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the APEX on X1 MCP server still maintained?
APEX on X1 is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 19 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.