Lets an agent pay for x402 APIs in USDC on Arc, under a spending policy it cannot change.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
arc_quoteAsk what a URL costs without paying. Returns price in USDC, seller address, network, whether the seller batches via Circle Gateway, the rail that would be used, the policy decision and the seller's ERC-8004 identity. Returns null if the resource is free.Ask what a URL costs without paying. Returns price in USDC, seller address, network, whether the seller batches via Circle Gateway, the rail that would be used, the policy decision and the seller's ERC-8004 identity. Returns null if the resource is free.
No input schema was published for this tool.
arc_payFetches the URL. If the server answers 402, CRA AGENT checks the spending policy, verifies the seller, signs a gas-free nanopayment through Circle Gateway (or a standard x402 payment), retries the request and records the outcome in the ledger. Returns the response body plus a receipt. Policy reject…Fetches the URL. If the server answers 402, CRA AGENT checks the spending policy, verifies the seller, signs a gas-free nanopayment through Circle Gateway (or a standard x402 payment), retries the request and records the outcome in the ledger. Returns the response body plus a receipt. Policy reject…
No input schema was published for this tool.
arc_balanceUSDC in the wallet and in the Circle Gateway balance used for nanopayments, on the configured Arc network.USDC in the wallet and in the Circle Gateway balance used for nanopayments, on the configured Arc network.
No input schema was published for this tool.
arc_depositMoves USDC from the wallet into the Circle Gateway balance so nanopayments can be signed. On-chain transaction (needs a little USDC for gas on Arc).Moves USDC from the wallet into the Circle Gateway balance so nanopayments can be signed. On-chain transaction (needs a little USDC for gas on Arc).
No input schema was published for this tool.
arc_ledgerThe last N payment attempts by this agent with amount, seller, status, latency and transaction, plus today's spend.The last N payment attempts by this agent with amount, seller, status, latency and transaction, plus today's spend.
No input schema was published for this tool.
arc_proofGateway settles in batches, so the transfer to the seller reaches the chain after the response. This matches settled payments in the ledger to the on-chain USDC transfer that carried them and stores the transaction hash.Gateway settles in batches, so the transfer to the seller reaches the chain after the response. This matches settled payments in the ledger to the on-chain USDC transfer that carried them and stores the transaction hash.
No input schema was published for this tool.
arc_verify_receiptVerifies a receipt another agent hands over: recovers who signed it, checks it is the agent named inside, and redoes the arithmetic to confirm the payment fitted the limits it states. It proves the agent's key issued the statement and that nothing was altered; it does not prove the payment settled,…Verifies a receipt another agent hands over: recovers who signed it, checks it is the agent named inside, and redoes the arithmetic to confirm the payment fitted the limits it states. It proves the agent's key issued the statement and that nothing was altered; it does not prove the payment settled,…
No input schema was published for this tool.
arc_policyThe limits this rail enforces for the agent. Read-only: limits are set by the operator in the environment, not by the model.The limits this rail enforces for the agent. Read-only: limits are set by the operator in the environment, not by the model.
No input schema was published for this tool.
arc_job_createFor work that is too large or too slow for a per-call payment. Creates a job with a provider (seller) and an evaluator; the provider then sets the budget, you fund it with arc_job_fund, the provider submits, the evaluator completes or rejects. Costs gas in USDC.For work that is too large or too slow for a per-call payment. Creates a job with a provider (seller) and an evaluator; the provider then sets the budget, you fund it with arc_job_fund, the provider submits, the evaluator completes or rejects. Costs gas in USDC.
No input schema was published for this tool.
arc_job_fundMoves the job's budget (set by the provider) from the agent wallet into the escrow contract. The spending policy is applied to the budget as one payment, with the provider as counterparty. Recorded in the ledger on the escrow rail.Moves the job's budget (set by the provider) from the agent wallet into the escrow contract. The spending policy is applied to the budget as one payment, with the provider as counterparty. Recorded in the ledger on the escrow rail.
No input schema was published for this tool.
arc_job_statusClient, provider, evaluator, budget, expiry and state (Open, Funded, Submitted, Completed, Rejected, Expired).Client, provider, evaluator, budget, expiry and state (Open, Funded, Submitted, Completed, Rejected, Expired).
No input schema was published for this tool.
arc_job_decideAs the job's evaluator: complete releases the escrow to the provider, reject returns it to the client. The reason is stored on-chain as a hash.As the job's evaluator: complete releases the escrow to the provider, reject returns it to the client. The reason is stored on-chain as a hash.
No input schema was published for this tool.
arc_job_submitAs the job's provider: submits the keccak256 hash of the deliverable and moves the job to Submitted.As the job's provider: submits the keccak256 hash of the deliverable and moves the job to Submitted.
No input schema was published for this tool.
13 of 13 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Lets an agent pay for x402 APIs in USDC on Arc, under a spending policy it cannot change.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
44 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+32 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies, optionalDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.