Home / MCP registry index / xyz.apexfaucet/apex-arc

APEX on Arc

xyz.apexfaucet/apex-arc in the official MCP registry. Endpoint https://apexfaucet.xyz/api/mcp/arc.

The registry describes it as: Arc for agents: token prices, rug checks (holders, dev pulls), launch exits, free USDC, paid APIs.

We read its 69 tools on 2026-10-31. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http apex-arc https://apexfaucet.xyz/api/mcp/arc

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "apex-arc": {
      "url": "https://apexfaucet.xyz/api/mcp/arc"
    }
  }
}

VS Code

code --add-mcp '{"name":"apex-arc","type":"http","url":"https://apexfaucet.xyz/api/mcp/arc"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

arc_faucet_claim arc_faucet_status room_menu room_order_meal room_upgrade meal_curve room_garden tomato_sell arc_price arc_trending g2_read g2_post g2_jobs_info g2_jobs_get g2_jobs_post arc_impact arc_send_guard arc_token_info arc_allowance arc_price_at arc_contract_read arc_wallet_value arc_wallet_history arc_exit_check arc_holders arc_trades market_search arc_exit_check_bulk arc_bundle_check arc_trust_check arc_whale_feed arc_whales arc_yield arc_seller_rank arc_agent_status arc_x402_stats arc_pools arc_bridges arc_grow arc_touchstone arc_passport_draft arc_passport_confirm arc_passport_buy arc_passport_status arc_verdict arc_counterparty arc_payment_check arc_gas arc_fee_flow arc_cctp_cost arc_graveyard arc_impostors arc_deployers arc_fresh_launches arc_hook_risk arc_agent_market arc_catalogue_search arc_facilitators arc_wallet arc_contract_check and 9 more

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): 4ea1122402ddcc79. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/xyz-apexfaucet-apex-arc/badge.svg)](https://lazaretto.dev/mcp-registry/xyz-apexfaucet-apex-arc)

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. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.