Skip to main content
Glama

APEX on Arc

by xyz.apexfaucet
OverviewDiscussionsAdmin

arc_wallet_history

Wallet history on Arc: the last 50 transfers in and out of an address over about 3 days, decoded (time, direction, from, to, token, amount, USD at the time of the transfer and today) plus net flow per token (accumulating or distributing). USDC counted once from native transfer logs; NFTs listed; impostor USDC/EURC and address poisoning (lookalike addresses, events the sender never signed) flagged. A failed read is refused before payment. $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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
beforeNooptional: a block number; returns the page ending at it (each answer gives next.before)
addressYesArc address (0x...)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / before
      Added value: +{
+  "description": "optional: a block number; returns the page ending at it (each answer gives next.before)",
+  "type": "string"
+}
  2. Added

TDQS

Score is being calculated.

All APEX on Arc toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources