Home / MCP registry index / xyz.apexfaucet/apex-x1
APEX Faucet
xyz.apexfaucet/apex-x1 in the official MCP registry.
Endpoint https://apexfaucet.xyz/mcp. Source: github.com/apexfaucet-hub/apex-x1-mcp.
The registry describes it as: Pay-safe is first: one signed check before you send USDC. 226 tools, x402, no key.
On 2026-10-31 we read its 200 tools, but part of what it advertised was cut before our rules saw it: a description or schema past the size we read, more tools than we read, or a tool list split across pages. Nothing in the part we read matched, but the rest was not checked: this is not a clean result.
Tools it advertises
page_extract site_extract get_onto_x1 exit_check arc_faucet_claim leads_find_businesses leads_find_contacts leads_email_pattern leads_verify_domains leads_pricing token_lookup top_tokens holdings recent_trades candles whale_ticker top_traders wallet_profile lp_position lp_add_build swap_build xnt_price agent_tune agent_radio social_feed social_post_how_to safetynet_cards safetynet_how_to_help commodity_markets commodity_price commodity_how_to_trade craft_recipes craft_how_to faucet_metrics agora_list agora_post_instructions agent_welcome_how_to rental_agents rental_plans rental_work_proof hire_agent_how_to agent_vault_status commodity_swap_build city_venues start_here vault_heartbeat referral bridge_assets launchpad impostor_check arc_faucet_status arc_exit_check arc_exit_check_bulk arc_grow arc_agent_status x1_passport arc_x402_stats arc_passport_draft arc_passport_confirm arc_passport_buy and 140 more
Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.
Run this server? Show the check in your README
The badge reflects the latest read: 
[](https://lazaretto.dev/mcp-registry/xyz-apexfaucet-apex-x1)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.
Related
| Citiview Agent Market com.citiviewgroup.mcp/agent-market | 200 tools, nothing matched 2026-10-26 |
| ScorpTech x402 API com.it.scorptech/x402 | 200 tools, nothing matched 2026-10-26 |
| Apex Edge — x402-paid machine services dev.pages.nonsynthetic/apex-edge | 200 tools, nothing matched 2026-10-23 |
| x402 Factory io.github.praneeth12098/x402-factory | 200 tools, nothing matched 2026-10-26 |
| Apex Edge — x402-paid machine services net.nonsynthetic/apex-edge | 200 tools, nothing matched 2026-10-26 |
| Crank Protocol ing.crank/crank | 196 tools, nothing matched 2026-10-28 |