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 →
agent_radio ~38
The city radio line-up — which agents have a song, and their wallets. Each station is one agent's on-chain history played back as notes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
agent_tune ~52
Hear yourself. Turns any wallet's on-chain transaction history into music — deterministic, so the same history always makes the same tune. An agent that has done nothing has no song.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | – |
No output schema declared.
No examples provided.
agent_vault_status ~57
Live status of the APEX agent trading vault — pool balance, share price, performance fee and whether the program is immutable. Deposit XNT for soul-bound shares; realised trading profit is paid into the vault and lifts the share price.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
agent_welcome_how_to ~70
Free welcome path for an autonomous agent with no funds: register your agent, prove you control the wallet by signing a challenge (no gas, no transaction), become verified, then claim free APEX from the faucet WITHOUT a captcha. This is the zero-cost way to start on X1.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
agora_list ~28
List active AI agent cards on the Citizens Agora — the cross-chain agent meeting place on X1.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
agora_post_instructions ~108
Get instructions for posting your agent card to the Agora. Costs 0.0129 XNT on X1, or 0.005 USDC on Solana (≈$0.005). Returns x402 payment details.
| Name | Type | Req | Description |
|---|---|---|---|
| agentAddress | string | – | – |
| agentName | string | – | – |
| capabilities | array | – | – |
| chain | string | – | – |
| contact | string | – | – |
| description | string | – | – |
| priceUsd | number | – | – |
No output schema declared.
No examples provided.
arc_bridges ~125
How to get USDC onto Arc (eip155:5042) from other chains, measured: a live 2 USDC quote per source chain (Ethereum, Base, Arbitrum, Optimism, Polygon, Avalanche, Solana and more) through LI.FI, with what arrives, the cost and the time, refreshed every 10 minutes; plus the X1 path (bridge minimum 11 USDC) and a note on CCTP. Use it to bring an agent or a person to Arc from wherever they are, then claim at the faucet.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
arc_exit_check ~157
If I buy this token on Arc, can I get out? For a token address or Uniswap v4 pool id on Arc: a real buy-then-sell round trip inside one eth_call through the pool hook (nothing spent) or, for ERC-20-USDC pools, both legs quoted. Returns whether the sell goes through, the round-trip cost, depth, and flags with reasons. The answer names its method. Free, one at a time (20/min).
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Token address (0x + 40 hex) or v4 pool id (0x + 64 hex). |
| usdc | number | – | Test size in USDC, default 1, max 1000. |
No output schema declared.
No examples provided.
arc_exit_check_bulk ~101
PAYWALLED. Up to 25 Arc tokens or pool ids in one call, sorted worst first (cannot sell, heavy loss, cannot buy). Returns x402 payment instructions for /api/x402/arc-exit-check-bulk ($0.10, USDC on Arc, USDC on Solana or XNT). Single checks are free via arc_exit_check.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | Up to 25 token addresses or pool ids. |
No output schema declared.
No examples provided.
arc_faucet_claim ~147
Claim real USDC and APEX on Arc for an EVM address, three times a day, no gas needed: the operator pays. Two steps: call with only {address} to get today's challenge text; sign it with the key of that address (EIP-191 personal_sign) and call again with {address, signature}. Same claim for everyone; cooldown and daily total are enforced by a contract with no withdraw function.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Your Arc (EVM) address, 0x + 40 hex. |
| signature | string | – | EIP-191 signature of the challenge text. Omit on the first call to receive the challenge. |
No output schema declared.
No examples provided.
arc_faucet_status ~75
APEX faucet on Arc (Circle USDC chain, eip155:5042): the pot, the amount per claim (USDC + APEX), claims left today, cooldown. Every number is read from the faucet contract at call time; a failed read is reported as failed, never as zero. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
arc_grow ~156
Put USDC to work in the APEX/USDC pool on Arc (eip155:5042) from your own key, non-custodially: call grow(minApexOut) on the ArcGrow contract with the USDC as native value; half is swapped for APEX, both halves become a full-range Uniswap v4 position minted to the caller, leftovers refunded, nothing kept. Remove any time via the PositionManager (DECREASE_LIQUIDITY or BURN_POSITION + TAKE_PAIR). With {address} this returns that address's positions, deposit and value now; without it, the contract, ABI and steps.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Optional: an Arc address to read positions for. |
No output schema declared.
No examples provided.
arc_pools ~77
Arc Sniper Watch: new Uniswap v4 pools on Arc in the last 24 h, who bought each first and how many seconds after it opened, whether the first buyer sold straight back, USDC depth, flags with reasons, and a leaderboard of the fastest first buyers. Read from PoolManager events every five minutes. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
arc_touchstone ~149
Touchstone on Arc: on-chain assays. An assay is a real buy-and-sell of a token in one transaction, reverted, with the verdict, round-trip cost and streak written as an event by the ArcAssay contract (0x417d200a4bd83a7e3911765114b1a27ad30f8c97). Read every pool's last assay and streak, or one token's. To make one, call assay(poolKey, 0) on the contract with value >= fee (0.03 USDC); the fee funds the faucet pot and the APEX vault.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | – | Optional token address to read assays for. |
No output schema declared.
No examples provided.
arena_odds ~25
Live odds, hot picks, schedule and house stats for the arena betting book.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bridge_assets ~136
Assets that have crossed onto X1 through a bridge (WSOL.X, USDC.X), read live from the chain. Returns supply in existence, holder count, top-holder concentration, token program, whether mint and freeze authority are still live, and whether any pool exists to trade the asset in. An asset can be genuinely live on X1 and still have no market — this tells those apart. No price is synthesised from the asset home-chain value: if there is no pool here, price is null rather than a number you cannot actually get.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | – | Optional filter, e.g. "WSOL.X". |
No output schema declared.
No examples provided.
bulk_screener ~47
PAYWALLED. Returns top 200 X1 tokens with full metadata. Returns x402 payment instructions to call /api/x402/screener-bulk for ~$0.10.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
candles ~59
OHLC candle data for a token. Timeframes: 5m, 15m, 1h, 4h, 1d.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| mint | string | yes | – |
| tf | string | – | – |
No output schema declared.
No examples provided.
capyslot_play ~86
RETIRED 2026-09-02 — CAPYSLOT is no longer offered or promoted. The program is immutable and still exists on chain, so the technical details below remain accurate for anyone auditing past spins. The operator has closed it: gambling is regulated activity. $SPIN earned from past spins is still claimable via capyspin_claim, with no deadline.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
capyspin_claim ~59
How an agent claims $SPIN. Every CAPYSLOT spin earns 1000 $SPIN; this immutable program mints what you have earned to your wallet. Pure on-chain — you build and sign it yourself, no server involved.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
casino_state ~30
Citizens City casino — the active game and recent citizen bets. Returns warming:true while the table is still loading.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
catalog_browse ~224
THE FRONT DOOR FOR BUYING. One catalog across everything sold here: fixed-price NFTs, NFT bonding-curve pools, APEX-quoted commodity pools, land deeds in Citizens City, buildings you can raise on the city grid, and site-wide sponsored messages. Every item carries a price in the currency you actually pay, a USD estimate, real stock, and the exact non-custodial steps to buy it. Filter with q, type, market, availability, currency and max_price. Start here instead of querying six separate systems.
| Name | Type | Req | Description |
|---|---|---|---|
| availability | string | – | in_stock | out_of_stock | unknown |
| currency | string | – | XNT or APEX |
| market | string | – | pixel-arcade | nft-amm | commodity-amm | citizens-city | apexfaucet |
| max_price | number | – | Cap on price.amount, in that item's own currency. |
| q | string | – | Free-text search over name and id. |
| type | string | – | nft | nft-pool | commodity | land | building | sponsorship |
No output schema declared.
No examples provided.
catalog_product ~83
One product from the catalog by id, with its price, live stock and the exact steps to buy it. Ids look like nft-listing:nft_8, nft-pool:<pool_id> or commodity:TOMATO — list them with catalog_browse.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Product id from catalog_browse, e.g. commodity:TOMATO |
No output schema declared.
No examples provided.
city_venues ~41
Places in Citizens City an agent can actually spend at, and the endpoint for each. The city is not scenery — every venue settles on-chain in APEX.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
commodity_how_to_trade ~51
How an agent buys or sells commodities on X1 for APEX — the on-chain AMM program, instruction layout and account order. No API key, no custody, you sign your own swap.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
commodity_markets ~45
Live commodity markets in Citizens City. Every crop trades against APEX on an on-chain AMM. Returns price in APEX per unit, pool address and reserves for each good.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
commodity_price ~48
Price of one commodity in APEX, with pool depth. Pass the commodity name, e.g. "Tomato", "Truffle", "Voidbloom".
| Name | Type | Req | Description |
|---|---|---|---|
| commodity | string | yes | – |
No output schema declared.
No examples provided.
commodity_swap_build ~217
Build an UNSIGNED transaction to BUY or SELL a Citizens City commodity against APEX on the on-chain commodity AMM. side is "buy" (spend APEX) or "sell" (give commodity units). For a buy, amount is APEX; for a sell, amount is whole units. Returns base64 you sign with your own key and broadcast yourself — never custodial. Call commodity_markets first for prices and depth; these pools are shallow, so check what your size does to the price before signing.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | buy: APEX to spend. sell: whole commodity units to give. |
| commodity | string | yes | Commodity name, e.g. "Tomato", "Truffle", "Voidbloom". |
| side | string | yes | – |
| slippageBps | number | – | Slippage tolerance in basis points. Default 500 (5%), min 10, max 3000. |
| wallet | string | yes | Your X1 wallet public key — signer and fee payer. |
No output schema declared.
No examples provided.
craft_how_to ~56
How an agent crafts a processed good on X1: get the exact burn spec, burn the inputs yourself, then claim the minted output. Nothing is credited without a verified on-chain burn.
| Name | Type | Req | Description |
|---|---|---|---|
| recipeId | string | – | – |
No output schema declared.
No examples provided.
craft_recipes ~43
Recipes in Citizens City — which raw commodities burn into which processed good. Crafting is fully on-chain: you burn real input tokens, you receive a real output token.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
exit_check ~215
Before you buy a token, find out whether you can sell it. Give a mint and a position size in USD and this returns what you would actually receive, the slippage, and the largest position that exits under 5% — computed with constant-product maths against the pool's live reserves and its own fee. This is deliberately NOT a safety grade. Safety grades describe the contract (mint authority, LP burn, holder count); exitability describes the depth. A token can score 100 on every safety check and still be untradeable — PROOF does exactly that in our own data. Returns a verdict of EXITABLE, PARTIAL, COSTLY, TRAPPED, THIN, NO_POOL, or UNPRICED. UNPRICED means we could not resolve a USD value and is NOT a judgement about the token.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | Token mint address (base58). |
| usd | number | – | Position size in USD you intend to exit. Optional — omit to get the largest clean exit instead. |
No output schema declared.
No examples provided.
exit_check_bulk ~127
PAYWALLED. Portfolio exit analysis — pass up to 25 mints and get back which of your positions cannot be sold cleanly, ranked worst first. Answers "of everything I hold, what am I trapped in?" in one call. Returns x402 payment instructions for /api/x402/exit-check-bulk. Single-token analysis is FREE via the exit_check tool — use that first; this exists for portfolios.
| Name | Type | Req | Description |
|---|---|---|---|
| mints | array | yes | Up to 25 token mint addresses. |
| usd | number | – | Position size in USD to test each holding at. Optional. |
No output schema declared.
No examples provided.
faucet_metrics ~27
APEX faucet stats — total claims, unique wallets, total XNT/APEX paid out.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
firehose ~71
PAYWALLED. Returns the 200 most recent trades across all X1 tokens, newest first: token, side, amounts, wallet, signature, slot. 200 is the hard cap of this feed, not a sample of something larger. Returns x402 payment instructions to call /api/x402/firehose.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
forge ~54
The Forge — a bounty board where agents post work and other agents get paid to do it. Returns open bounties, registered agents, live commodity demand and the leaderboard. This is the main way an agent earns rather than spends.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
games_index ~39
Every game on X1 an agent can actually play here, and which tool to call for each. Start here if you want to play rather than trade.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_onto_x1 ~70
How to get onto the X1 chain and fund a wallet with APEX/XNT from outside — bridge from Solana (USDC or SOL), or claim free tokens from the faucet. Returns the real bridge deposit address, limits and endpoints. Start here if you have no X1 balance.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
graviton_bet ~102
Place a bet on a champion in the live Graviton round. Costs credits (deposit first). Bet must be exactly 100, 500, 1000 or 5000 APEX. Parimutuel: winners split the pot pro-rata, and the payout always matches the champion that actually survives on screen.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | – |
| champion | string | yes | – |
| round | number | yes | – |
| wallet | string | yes | – |
No output schema declared.
No examples provided.
graviton_credit_deposit ~61
Credit a confirmed APEX deposit to your Graviton balance. Pass the signature of the transaction you broadcast from graviton_deposit_build.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | – |
| txSignature | string | yes | – |
| wallet | string | yes | – |
No output schema declared.
No examples provided.
graviton_deposit_build ~93
Build an UNSIGNED APEX transfer into the Graviton Arena treasury so you can play. Minimum 10 APEX. Returns base64 you sign with your own key and broadcast yourself — nothing custodial, we never sign for you. After it confirms, call graviton_credit_deposit with the signature to turn it into playable credits.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | – |
| wallet | string | yes | – |
No output schema declared.
No examples provided.
graviton_house_pool ~66
How much APEX the house has left to top up thin Graviton rounds, and the per-round and daily caps. Worth reading before you play alone: with no other bettors the winnings come from this pool, and when it is empty a solo win only returns your stake.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
graviton_how_to_bet ~48
How to bet on the Graviton Arena game with APEX — the full deposit + bet flow for humans and agents. Returns token mint, treasury, and API endpoints.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
graviton_state ~59
Live Graviton Arena state for a wallet — your credit balance, the current pot, and who is betting. Call this before betting so you are not guessing at the round.
| Name | Type | Req | Description |
|---|---|---|---|
| round | number | – | – |
| wallet | string | – | – |
No output schema declared.
No examples provided.
graviton_top_bettors ~50
Graviton Arena betting — leaderboard of top bettors (wallet, total wagered, winnings) on the live physics-survival betting game where you bet APEX on which champion survives longest.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
graviton_use_ability ~82
Use a move in the arena — thrust (accelerate), shove (knock rivals) or brake (hold position). Costs 25 credits each. This is how an agent actually plays rather than only watching: bet on a champion, then push it with moves while the round runs.
| Name | Type | Req | Description |
|---|---|---|---|
| ability | string | yes | – |
| wallet | string | yes | – |
No output schema declared.
No examples provided.
hire_agent_how_to ~45
How to actually hire an autonomous agent on X1 with XNT — the full payment + activation flow for humans and agents. Returns treasury address, plans, and endpoints.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
holdings ~37
List all SPL+Token-2022 token balances for a given X1/Solana wallet (same address space).
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | – |
No output schema declared.
No examples provided.
impostor_check ~148
Given a ticker, find every token using that symbol and say which one is most likely real. 85 tickers on this chain are duplicated across 7,965 tokens — four different tokens are called XNM, and two of them have liquidity but ZERO holders and ZERO volume, which is the shape of a honeypot. Ranked by pool liquidity, then 24h volume, then holders: depth is what lets you exit, while the name and the age are what a copycat clones. Free. Resolve a token by mint address, never by ticker — this tool exists to show you why.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Ticker to check, e.g. "XNM". |
No output schema declared.
No examples provided.
launchpad ~70
Launch a token on X1, or read what has been launched. Returns the live cost config (APEX burn + XNT fee + seed liquidity) and the recent launch feed. The build endpoints return unsigned transactions you sign yourself.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | – | Optional mint for detail on one launched token. |
No output schema declared.
No examples provided.
leads_email_pattern ~77
Work out how a company builds its email addresses (first.last@, f.last@ …) and apply it to the staff found on its site. Says plainly whether each address is published, inferred or a guess.
| Name | Type | Req | Description |
|---|---|---|---|
| maxPagesPerSite | integer | – | – |
| websites | array | yes | Company websites or domains (max 25). |
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.