Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

xyz.apexfaucet/apex-arc

REMOTE · APEXFAUCET.XYZ · SCANNED SEP 25

Arc for agents: free USDC, ERC-8004 agent passports, watchtower, exit checks, x402 tools. 38 tools.

Available components

63 Trust /100
Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 5103 tokens (~134/item across 38 items; 38 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 92% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 38 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 39 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the xyz.apexfaucet/apex-arc MCP server?

xyz.apexfaucet/apex-arc is a hosted endpoint at https://apexfaucet.xyz/api/mcp/arc, 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

# add to Claude Code
claude mcp add --transport http xyz-apexfaucet-apex-arc 'https://apexfaucet.xyz/api/mcp/arc'
// .cursor/mcp.json
{
  "mcpServers": {
    "xyz-apexfaucet-apex-arc": {
      "url": "https://apexfaucet.xyz/api/mcp/arc"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "xyz-apexfaucet-apex-arc": {
      "type": "http",
      "url": "https://apexfaucet.xyz/api/mcp/arc"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.xyz-apexfaucet-apex-arc]
url = "https://apexfaucet.xyz/api/mcp/arc"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xyz-apexfaucet-apex-arc": {
      "type": "remote",
      "url": "https://apexfaucet.xyz/api/mcp/arc",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add xyz-apexfaucet-apex-arc --url 'https://apexfaucet.xyz/api/mcp/arc' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  xyz-apexfaucet-apex-arc:
    url: "https://apexfaucet.xyz/api/mcp/arc"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "xyz-apexfaucet-apex-arc": {
      "Transport": "http",
      "Url": "https://apexfaucet.xyz/api/mcp/arc"
    }
  }
}
# add to Vellum
assistant mcp add xyz-apexfaucet-apex-arc -t streamable-http -u 'https://apexfaucet.xyz/api/mcp/arc'
// mcp.json
{
  "mcpServers": {
    "xyz-apexfaucet-apex-arc": {
      "type": "http",
      "url": "https://apexfaucet.xyz/api/mcp/arc"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 25 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “arc_agent_status” rewrote its description, which is the text the model reads security
    • Tool “arc_exit_check_bulk” rewrote its description, which is the text the model reads security
    • Tool “arc_grow” rewrote its description, which is the text the model reads security
    • Tool “arc_x402_stats” rewrote its description, which is the text the model reads security
    • Tool coverage: 100% → 92% ▼ functional
    • Schema quality: 1131 → 5103 ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
    • New tool “arc_agent_market” functional
    • New tool “arc_agent_reputation” functional
    • New tool “arc_agent_search” functional
    • New tool “arc_catalogue_search” functional
    • New tool “arc_cctp_cost” functional
    • New tool “arc_contract_check” functional
    • New tool “arc_counterparty” functional
    • New tool “arc_deployers” functional
    • New tool “arc_facilitators” functional
    • New tool “arc_fee_flow” functional
    • New tool “arc_fresh_launches” functional
    • New tool “arc_gas” functional
    • New tool “arc_graveyard” functional
    • New tool “arc_hook_risk” functional
    • New tool “arc_impostors” functional
    • New tool “arc_passport_buy” functional
    • New tool “arc_passport_confirm” functional
    • New tool “arc_passport_draft” functional
    • New tool “arc_passport_status” functional
    • New tool “arc_payment_check” functional
    • New tool “arc_rpc_status” functional
    • New tool “arc_stablecoins” functional
    • New tool “arc_verdict” functional
    • New tool “arc_wallet” functional
    • New tool “erc8004_how_to” functional
    • New tool “get_onto_arc” functional
    • New tool “x402_accept_on_arc_how_to” functional
    • New tool “x402_inspect” functional
  • 24 Sept 26 63

    First indexed and scored.

Diagnostics

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 25 Sept 2026 · Probed https://apexfaucet.xyz/api/mcp/arc

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/api/mcp/arc Verified 200
http (plaintext) http://apexfaucet.xyz/api/mcp/arc HTTPS enforced 301 https://apexfaucet.xyz/api/mcp/arc
MCP tools · 38 exposed · ~5,015 tokens

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 →

Tool Tokens
arc_agent_market ~130

The agent economy on Arc, mapped: every agent in the ERC-8004 registry that publishes a registration file, with its owner, services and whether it takes x402. $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`.

NameTypeReqDescription
paymentstring–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.

arc_agent_reputation ~93

What other wallets have said about an Arc agent on chain: every ERC-8004 reputation entry for it (who gave it, the value, the tags, whether it was revoked) and the registry's own summary. Includes the weekly uptime records the APEX Watchtower writes. Free, 200 calls a day.

NameTypeReqDescription
agentIdintegeryesthe agent id in Arc's ERC-8004 registry

No output schema declared.

No examples provided.

arc_agent_search ~133

Find an agent on Arc by what it is called or where it answers: searches every agent in Arc's ERC-8004 registry that the APEX Watchtower checks each hour, and returns its id, status, uptime over measured hours, whether it can be paid on Arc and its main endpoint. Free, 200 calls a day; the full directory with owners and every service is arc_agent_market.

NameTypeReqDescription
payableOnlyboolean–only agents a standard client can pay on Arc
querystringyeswords from its name or endpoint, e.g. "oracle", "mcp", "news"

No output schema declared.

No examples provided.

arc_agent_status ~255

Does this Arc agent actually answer? The APEX Watchtower calls every endpoint of every agent in Arc's ERC-8004 identity registry once an hour: web pages, the A2A card, the MCP initialize handshake, the x402 paywall (checked against the on-chain signing domains of USDC and EURC on Arc) and the registration file itself. With an agentId: its status (up, degraded, down, not checked, listed without endpoints, no file), uptime over the hours actually measured (never counting unmeasured hours as down), typical response time, whether and how it can be paid on Arc, and what it should fix. Call it before you pay or hire an agent. Without an agentId: the counts for the whole registry. Free. Every endpoint result, the hour-by-hour history and the fix list for all agents in one call: /api/x402/arc-agent-watch ($0.004).

NameTypeReqDescription
agentIdinteger–The agent id in the Arc ERC-8004 identity registry (0x8004A169FB4a3325136EB29fA0ceB6D2e539a432). Omit for the whole-registry counts.

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_catalogue_search ~153

Who sells this on Arc, and for how much? Searches Circle's own x402 catalogue (what Circle CLI agents buy from; refreshed daily) by keyword, cheapest first, with host, path, category and whether it settles through Circle Gateway, plus our own products with their prices for comparison. Use it to price a service before you build or buy it. Free.

NameTypeReqDescription
limitinteger–up to 40 (default 15)
maxPricenumber–optional price cap in USD
networkstring–arc (default), base, polygon, solana or any
querystring–keywords, e.g. "scrape", "token price", "email"

No output schema declared.

No examples provided.

arc_cctp_cost ~131

What bringing USDC into Arc over Circle CCTP really costs, measured from arrivals: every arrival with the amount credited and the fee taken, and observed fees by size. $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`.

NameTypeReqDescription
paymentstring–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.

arc_contract_check ~87

Before you approve, pay or trust a contract on Arc: is it really a contract, can someone change its code (EIP-1967 proxy implementation, admin and beacon slots), who is its owner(), and what token it says it is. Read live from the chain. Free, 200 calls a day.

NameTypeReqDescription
addressstringyes0x contract address on Arc

No output schema declared.

No examples provided.

arc_counterparty ~159

Who is this Arc address as a trader? How often it is the first buyer into a new pool, how fast it enters, USDC in versus out, positions it is stuck in, and the flags. Facts from the chain, never a label. $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`.

NameTypeReqDescription
addressstringyes0x address on Arc
paymentstring–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.

arc_deployers ~123

Who launched what on Arc and whether any of it ever traded: every repeat creator with their launches and the swap fees those launches earned. $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`.

NameTypeReqDescription
paymentstring–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.

arc_exit_check ~158

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 (ten a minute).

NameTypeReqDescription
querystringyesToken address (0x + 40 hex) or v4 pool id (0x + 64 hex).
usdcnumber–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.025, USDC on Arc, USDC on Solana or XNT). Single checks are free via arc_exit_check.

NameTypeReqDescription
idsarrayyesUp to 25 token addresses or pool ids.

No output schema declared.

No examples provided.

arc_facilitators ~109

Who settles x402 payments on Arc, measured on the chain: every relayer that spent an EIP-3009 authorization on Arc USDC, with its label where one is published, how many settlements, payers and payees, volume, and the shape of its flow (direct, circular, concentrated, self or contract). Plus Circle's two facilitators and what each needs. Free.

NameTypeReqDescription
limitinteger–how many relayers (default 15, max 60)

No output schema declared.

No examples provided.

arc_faucet_claim ~202

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. The day's claims open in three parts (00:00, 08:00, 16:00 UTC) and one connection claims at most once every 8 hours; a refusal names the time. The reply includes nextClaimAt (unix seconds) and claimNumber.

NameTypeReqDescription
addressstringyesYour Arc (EVM) address, 0x + 40 hex.
signaturestring–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 ~110

APEX faucet on Arc (Circle USDC chain, eip155:5042): the pot, the amount per claim (USDC + APEX), claims left today and left right now (the day's claims open in three parts, at 00:00, 08:00 and 16:00 UTC; nextReleaseAt says when), 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_fee_flow ~131

Arc launchpad fee vaults: every vault holding USDC now, its creator and token, and how much it changed since our previous scan. Fees only accrue from real swaps. $0.025 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`.

NameTypeReqDescription
paymentstring–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.

arc_fresh_launches ~126

Arc launches in real time, each with a sell verdict from a real round trip, so you see the new pools that can actually be exited. $0.003 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`.

NameTypeReqDescription
paymentstring–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.

arc_gas ~125

What a transaction on Arc actually costs, measured from real receipts rather than quoted from the docs: percentiles per transaction kind, with the sample sizes. $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`.

NameTypeReqDescription
paymentstring–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.

arc_graveyard ~129

The Arc pool graveyard: every pool we measured with its state (empty or alive) and lifetime volume, so you know which ones nothing can be sold into. $0.025 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`.

NameTypeReqDescription
paymentstring–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.

arc_grow ~205

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, and priceCheck: APEX's price on Arc against its price on X1. While they are more than 10% apart, do not deposit (half the USDC would buy APEX at that premium); our own page refuses then.

NameTypeReqDescription
addressstring–Optional: an Arc address to read positions for.

No output schema declared.

No examples provided.

arc_hook_risk ~156

What a Uniswap v4 hook on Arc is allowed to do, read from the permission bits in its address with no chain call: whether it runs on swaps or can rewrite amounts. A capability, not a verdict. $0.003 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`.

NameTypeReqDescription
hookstringyes0x hook address from the pool key
paymentstring–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.

arc_impostors ~132

Every token symbol on Arc worn by more than one contract, with how many contracts share it and the canonical address where one is verified. Identity is the contract, never the symbol. $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`.

NameTypeReqDescription
paymentstring–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.

arc_passport_buy ~174

An agent buys its own ERC-8004 identity on Arc with a signature alone: $0.99 over x402, paid in USDC on Arc or Base. We host a correct registration file, mint the identity and hand it to the wallet that signed the payment, never to a typed address, and answer with the agentId and both transactions. Call once without `payment` to get the x402 terms, sign them, call again with `payment`. A refused input is never charged.

NameTypeReqDescription
descriptionstringyes–
imagestring––
namestringyes–
paymentstring–a signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.
servicesarray––

No output schema declared.

No examples provided.

arc_passport_confirm ~120

Finish a free Arc Agent Passport: after your wallet sent the register() transaction from arc_passport_draft, pass the draft slug and the transaction hash. We read the receipt on Arc (never the caller's word), fill the file with the new agentId and return the passport page, its share picture, the watchtower check-up and its tower in Arc City. Free.

NameTypeReqDescription
slugstringyesthe 12-character id from arc_passport_draft
txstringyes0x hash of your register() transaction

No output schema declared.

No examples provided.

arc_passport_draft ~198

Give an agent an ERC-8004 identity on Arc for free. Pass its name, what it does and where it can be reached; we write a correct registration file, host it, check that its endpoints answer, and return the unsigned register() transaction for Arc's identity registry. The wallet that sends it owns the agent from the first block (about 0.004 USDC of gas; one claim from arc_faucet_claim covers it). Then call arc_passport_confirm with the transaction hash. No key ever leaves your side.

NameTypeReqDescription
descriptionstringyeswhat the agent does, 10-400 characters
imagestring–optional https link to a picture
namestringyes2-48 characters
servicesarray–optional endpoints: [{name: web|A2A|MCP|x402|OASF|ENS|DID|email, endpoint}]

No output schema declared.

No examples provided.

arc_passport_status ~77

Look up an Arc Agent Passport by agentId or draft slug: its registration file, owner, endpoints, whether it is active, and its links (passport page, share picture, hourly check-up, tower in Arc City). Free.

NameTypeReqDescription
refstringyesagentId (a number) or the 12-character draft slug

No output schema declared.

No examples provided.

arc_payment_check ~181

Did that Arc payment really land? Payer, recipient, amount in both of Arc's transfer forms (the ERC-20 view and the native log), confirmation and gas, checked against what you expected. $0.003 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`.

NameTypeReqDescription
expectstring–optional expected amount in USDC, e.g. 1.50
paymentstring–a signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.
tostring–optional expected recipient
txstringyes0x transaction hash on Arc

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_rpc_status ~71

Which Arc RPC is answering right now, and how fast: the latest block, how far each one lags and its response time, measured this minute from our server. Arc's official RPC throttles in a way that reads like a bug ("Request exceeds defined limit"); use this to pick another. Free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

arc_stablecoins ~50

How many stablecoins exist on Arc right now, read from the contracts: USDC and EURC total supply, their addresses and the EIP-712 signing domains a payment signs against. 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.

NameTypeReqDescription
tokenstring–Optional token address to read assays for.

No output schema declared.

No examples provided.

arc_verdict ~170

Should you buy this Arc pool? One call, one 0-100 answer from the hook's permissions, a real sell probe and what happened to earlier buyers, with every input shown. $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`.

NameTypeReqDescription
paymentstring–a signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.
poolstring–Uniswap v4 pool id on Arc (pass this or token)
tokenstring–token contract address on Arc (pass this or pool)

No output schema declared.

No examples provided.

arc_wallet ~92

Everything public about one Arc address in one call: USDC (native, 18 decimals) and EURC and APEX balances, whether it is a contract, how many ERC-8004 agent identities it owns and which agents, and whether it sells over x402 on Arc. Read live from the chain. Free, 200 calls a day.

NameTypeReqDescription
addressstringyes0x address on Arc

No output schema declared.

No examples provided.

arc_x402_stats ~221

Who actually pays whom on Arc. Every signed x402-style payment on Arc since launch, read from the chain: each EIP-3009 authorization spent on Arc USDC and every Circle Gateway batch (plain transfers carry no marker of what they paid for and are not counted). Without an address: the totals, each facilitator (the address that submits settlements, named only where the name has a source) with its kind (direct; circular, where the same wallets pay and are paid; concentrated, one payer making most of the volume; self; or contract flow), each measured and shown apart from the direct totals, and the top sellers. With an address: what that address was paid, by how many distinct payers, through which facilitators, including Circle Gateway. Free. Every facilitator, seller and payer with the latest 1,000 settlements: /api/x402/arc-x402 ($0.004).

NameTypeReqDescription
addressstring–Optional Arc address (0x + 40 hex) to look up as a seller or payer.

No output schema declared.

No examples provided.

erc8004_how_to ~74

How ERC-8004 works on Arc, from the spec and the deployed contracts: register an agent (and the one-call shortcuts), the registration file fields, proving your endpoint domain, pointing payments at an agentWallet, writing and reading reputation, and what explorers like 8004scan read. Free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_onto_arc ~79

How to get USDC onto Arc, every route we know works: a free claim at our faucet (a signature, no gas), bridges measured live, Circle CCTP and what it really costs at small size, Circle Gateway balances, and Circle's Onramp Kit for apps that let people pay by card or Apple Pay. Free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

x402_accept_on_arc_how_to ~80

How to accept x402 payments on Arc, from what we verified on chain while doing it ourselves: the USDC and EURC signing domains, what a settlement leaves in the logs, what one costs in gas, and your three ways to settle (yourself, Circle Facilitator Service, Circle Gateway nanopayments). Free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

x402_inspect ~129

How do I pay this URL? Point it at any x402 paywall and get its terms read for you: protocol version, every network and asset it accepts with the real amount, the address it pays, and how to pay each option (EIP-3009 signature, Circle Gateway batch, Solana fee payer). It also lists what is wrong with the paywall, e.g. a missing signing domain. Free, 100 calls a day.

NameTypeReqDescription
methodstring–GET (default) or POST
urlstringyesthe https URL of the paid resource

No output schema declared.

No examples provided.

Common questions

What is the xyz.apexfaucet/apex-arc MCP server?

xyz.apexfaucet/apex-arc is an MCP server listed in the public MCP registry as xyz.apexfaucet/apex-arc. Arc for agents: free USDC, ERC-8004 agent passports, watchtower, exit checks, x402 tools. 38 tools. This page covers its hosted endpoint (https://apexfaucet.xyz/api/mcp/arc).

Is the xyz.apexfaucet/apex-arc MCP server safe to use?

xyz.apexfaucet/apex-arc scores 63 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 xyz.apexfaucet/apex-arc MCP server expose?

xyz.apexfaucet/apex-arc exposes 38 tools: arc_faucet_claim, arc_faucet_status, arc_exit_check, arc_exit_check_bulk, arc_agent_status, and 33 more. Their descriptions and schemas cost roughly 5,015 tokens of context every time the server is loaded.

Does the xyz.apexfaucet/apex-arc MCP server require authentication?

No. We connected to xyz.apexfaucet/apex-arc without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the xyz.apexfaucet/apex-arc MCP server still maintained?

xyz.apexfaucet/apex-arc is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.