# arcgate (remote · api.arcgate.dev)

Token search, swap quotes and ready-to-sign swap transactions on Arc, paid per call via x402

- Trust score: 54/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-02

## Components

- remote · `api.arcgate.dev`: 54/100 (this document), [markdown](https://verifymcp.io/servers/dev-arcgate-arcgate/trade-v1-mcp.md), [page](https://verifymcp.io/servers/dev-arcgate-arcgate/trade-v1-mcp)

## Channel facts

- Endpoint: `https://api.arcgate.dev/trade/v1/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-02.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 4129 tokens (~589/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 68/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 4% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the arcgate MCP server?

arcgate is a hosted endpoint at https://api.arcgate.dev/trade/v1/mcp, 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.

### Claude

```bash
claude mcp add --transport http dev-arcgate-arcgate 'https://api.arcgate.dev/trade/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-arcgate-arcgate": {
      "url": "https://api.arcgate.dev/trade/v1/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-arcgate-arcgate": {
      "type": "http",
      "url": "https://api.arcgate.dev/trade/v1/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-arcgate-arcgate]
url = "https://api.arcgate.dev/trade/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-arcgate-arcgate": {
      "type": "remote",
      "url": "https://api.arcgate.dev/trade/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-arcgate-arcgate --url 'https://api.arcgate.dev/trade/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-arcgate-arcgate:
    url: "https://api.arcgate.dev/trade/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-arcgate-arcgate": {
      "Transport": "http",
      "Url": "https://api.arcgate.dev/trade/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-arcgate-arcgate -t streamable-http -u 'https://api.arcgate.dev/trade/v1/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-arcgate-arcgate": {
      "type": "http",
      "url": "https://api.arcgate.dev/trade/v1/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-02 (score 54, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-01 (score 54)

First indexed and scored.

## MCP tools (7)

### `tradeSearch` (~235 tokens)

Resolves a ticker, name, prefix or `0x` address to candidate ERC-20 tokens on Arc.

\- **Cost:** 0.005 USDC per call over x402: the first call gets a 402 with payment requirements in the `PAYMENT-REQUIRED` header (base64 JSON); sign them and retry with a `PAYMENT-SIGNATURE` header carrying the payment payload.
\- **Key inputs:** `query` (required), `limit` (1-25, default 10).
\- **Returns:** each match with its verification status, safety verdicts and USDC/hub pools, most relevant first.
\- **Next:** pass the chosen result's `address` as `sell` or `buy` to POST /trade/v1/quote. Costs 5000 base units (0.005 USDC) per call. Payment goes in params._meta["x402/payment"]; use an x402-aware MCP client (see https://docs.arcgate.dev/#arcgate/description/mcp-for-agents).

Input parameters:

- `limit` (integer)
- `query` (string, required)

### `tradeQuote` (~951 tokens)

Prices a swap between `sell` and `buy` across the indexed venues and stores it under a `quoteId`.

\- **Cost:** 0.01 USDC per call over x402: the first call gets a 402 with payment requirements in the `PAYMENT-REQUIRED` header (base64 JSON); sign them and retry with a `PAYMENT-SIGNATURE` header carrying the payment payload.
\- **`sell` / `buy`:** two different assets (native and ERC-20 USDC count as the same asset; either side may be USDC). Resolve a ticker with POST /trade/v1/search first.
\- **Response shape:** when one side is USDC, `best.type` is `direct`/`two_hop`/`split` and `best.legs` lists one leg per path actually used; `routes[]` lists every discovery candidate. When neither side is USDC, or when a USDC-side allocation can't be expressed as legs, `best.type` is `graph`, `best.legs` is empty, and the execution plan is in `best.graph`. Both shapes support `side: exactIn` and `exactOut`, and both execute the same way through POST /trade/v1/swap.
\- **`amount`:** a human-readable decimal string in the token's own units, e.g. "1.5" for 1.5 USDC, not base units. It is the `sell` amount for `side: exactIn` and the `buy` amount for `side: exactOut`.
\- **Optional:** `side` (exactIn/exactOut), `slippageBps`, split and hop limits, `venues`/`excludeVenues` (ids from GET /trade/v1/venues), `taker`, `ttlSec`.
\- **Executability:** POST /trade/v1/swap executes every quote through ArcgateRouter. `best.executable` is `false`, with warning `graph_execution_unavailable`, when no ArcgateRouter is configured (or, for an Aerodrome edge, no Aerodrome router), or when the operator has disabled a selected path's venue - even with both routers configured. In that last case, POST /trade/v1/swap may still fall back to an executable candidate the quote already priced instead of failing outright.
\- **Readiness:** name the wallet that will trade in `taker` and the answer carries `readiness`, read at the quote's block: whether that wallet holds the input (`balance`), which approval or Permi…

Input parameters:

- `allowSplits` (boolean)
- `amount` (string, required)
- `buy` (string, required)
- `excludeVenues` (array)
- `maxHops`
- `maxSplits` (integer)
- `sell` (string, required)
- `side` (string)
- `slippageBps` (integer)
- `sources` (array)
- `taker`
- `ttlSec` (integer): How long the stored quote (and this response's expiresAt) stays live, in seconds (1-120, default 120). A caller may shorten it to re-quote sooner; it can never lengthen past 120s. Safe to shorten or…
- `venues`

### `tradeSwap` (~1440 tokens)

Turns a stored quote into unsigned transactions for the taker to sign and send. arcgate never signs, broadcasts or holds funds.

\- **Cost:** 0.01 USDC under $1,000; 0.05 USDC from $1,000 to $10,000; above that 0.05 USDC plus 0.5 bps of the amount over $10,000, capped at 5 USDC, size-tiered by the quote's USD notional (the USDC side for a USDC pair, or a token-to-token quote's USD valuation; a quote with no valuation prices at tier 1), over x402 (402 with `PAYMENT-REQUIRED`, retry with `PAYMENT-SIGNATURE`). Charged once per quote: POST /trade/v1/swap/tx, the Permit2 second round below, is free.
\- **Key inputs:** `quoteId` (from POST /trade/v1/quote), `taker`; optional `recipient` (defaults to `taker`), `deadlineSec`, `approval`. Never `permit` - that belongs to POST /trade/v1/swap/tx; sending one here is 400 `invalid_request` (the strict schema rejects the unknown key).
\- **Every quote executes through ArcgateRouter:** it is always the Permit2 `spender` and the ERC-20 `approve` spender below. When every source pool of the route being executed trades native USDC, the swap is funded by `value` instead - no approval transaction and no signature at all.
\- **Permit2 (default, one or two calls):**
  \- Returns `transactions` - an unlimited ERC-20 `approve(Permit2, type(uint256).max)` first, if the token's ERC-20 allowance to Permit2 is below the amount, then the swap, which carries an empty Permit2 signature and is only directly sendable as-is when a Permit2 allowance to ArcgateRouter already covers the amount, in which case `signatures` is empty too. Otherwise it also returns `signatures: [{ kind: "permit2", typedData }]`; sign `typedData` with the taker's key (EIP-712, e.g. viem's `signTypedData`).
  \- **Sign, then call POST /trade/v1/swap/tx** with the same `quoteId`, `taker` and `recipient`, and `permit: { message: typedData.message, signature }`, while the quote is live: free, because this call already paid the swap fee. The first call to it that succeeds uses the rou…

Input parameters:

- `approval` (string)
- `deadlineSec` (integer)
- `quoteId` (string, required)
- `recipient`
- `taker` (string, required)

### `tradeSwapTx` (~745 tokens)

The free Permit2 second round: finishes a POST /trade/v1/swap call whose `signatures` asked the taker to sign a Permit2 `PermitSingle`.

\- **Cost:** free, never x402-gated - a payment header, if one is sent anyway, is ignored and nobody is charged. Only reachable once, right after the paid call that opened it.
\- **Key inputs:** the SAME `quoteId`, `taker` and `recipient` (defaults to `taker`) as the paid POST /trade/v1/swap call, plus `deadlineSec` and the required `permit: { message: signatures[0].typedData.message, signature }` (sign `typedData` with the taker's key, EIP-712, e.g. viem's `signTypedData`). `permit` accepts only `message` and `signature`, end to end - any other field, at any level, is 400 `invalid_request` at parse. The service rebuilds the Permit2 domain itself and checks the signer, spender, token, amount, nonce and both deadlines: a mismatched spender or token, or an amount below `amountIn` (a larger amount is accepted), is 400 `invalid_request`; a stale nonce, an expired `sigDeadline`/`expiration`, or an invalid signature (verified via ERC-1271 on chain for a contract taker) is 422 `swap_reverts`. A contract taker can swap, but POST /trade/v1/receipt only reads transactions the taker sends itself, so it answers `invalid_request` for a Safe, ERC-4337 or batching EIP-7702 wallet: check your own transaction receipt instead.
\- **No pending round:** 409 `no_pending_swap` when this `quoteId`/`taker`/`recipient` never paid, named a different taker or recipient, or already used its one free call - call POST /trade/v1/swap first, which is paid and returns the permit this call takes.
\- **Freshness:** re-quotes and re-simulates exactly like POST /trade/v1/swap, and can answer the SAME 410 `quote_expired`/409 `quote_stale` it would - but never with a fresh `quote` (issue #124's free re-quote is /trade/v1/swap's own paid-quote courtesy, not this free route's).
\- **Attempts:** a permit round (`quoteId`, `taker`, `recipient`) gets at most 5 failed calls; the…

Input parameters:

- `deadlineSec` (integer)
- `permit` (object, required)
- `quoteId` (string, required)
- `recipient`
- `taker` (string, required)

### `tradeReceipt` (~601 tokens)

Tells you whether the transactions POST /trade/v1/swap returned did what the quote promised, once you've sent them. It only reads the chain.

\- **Cost:** free, never x402-gated.
\- **Key inputs:** `quoteId` (the one you called POST /trade/v1/swap with) and `txHashes`, the 1 to 4 transactions you sent for it: the swap, and any approvals. It answers for a quote /trade/v1/swap handed transactions for in the last hour, else 404 `swap_not_found`, and only for that quote's transactions, sent from its `taker`: an approval to the input token, or a swap to ArcgateRouter whose deadline one of the quote's /trade/v1/swap or /trade/v1/swap/tx answers issued and whose output goes to its `recipient`, else 400 `invalid_request`.
\- **Smart-contract wallets:** a Safe, an ERC-4337 account or a batching EIP-7702 wallet sends its transaction from an executor or bundler, or to itself, not from the taker to ArcgateRouter, so this answers 400 `invalid_request` for it. Check that transaction's own receipt and your wallet's success event instead.
\- **Returns:** `result`, from the swap transactions. One that filled decides it: `pass` when `delivered` is at least `minAmountOut`, else `fail` (a round 1 that reverted doesn't undo a round 2 that filled). With none filled: `pending` while one is not mined yet, else `fail`: it reverted or was never mined by 60s after its deadline (status `expired`, or `not_found` when the chain never saw it). Approvals are listed but don't change the result. `delivered` is what `recipient` received of `token` (the output), read from the swap transaction's Transfer logs, in base units. Also `block`, each transaction's `status`, and `reason`, one sentence on a fail or pending. The first result from a mined swap is final: asking again returns it.
\- **Limits:** one chain read per quote every 5s (the same `txHashes` inside that get the last answer; other hashes get 429 `receipt_rate_limited` with `retryAfterSec`), and at most 132 per quote (then 429 `receipt_reads_exhau…

Input parameters:

- `quoteId` (string, required)
- `txHashes` (array, required)

### `tradeVenues` (~80 tokens)

Lists the DEX venues, hub tokens and launchpads this deployment indexes.

\- **Cost:** free, never x402-gated.
\- **Returns:** each venue with an `executable` flag, hubs and launchpads.
\- **Next:** use venue ids in POST /trade/v1/quote's `venues` / `excludeVenues`.

### `health` (~77 tokens)

Reports whether the service is up, with its diagnostics.

\- **Cost:** free, never x402-gated.
\- **Returns:** DB import health, rule set version, the deployed commit, cache/RPC/spend counters and the payer-identity mode.
\- **Next:** call before search/quote/swap to check the service is up.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-arcgate-arcgate/trade-v1-mcp#diagnostics

## Score history

- 2026-10-02: 54
- 2026-10-01: 54

## Common questions

### What is the arcgate MCP server?

arcgate is an MCP server listed in the public MCP registry as dev.arcgate/arcgate. Token search, swap quotes and ready-to-sign swap transactions on Arc, paid per call via x402. This page covers its hosted endpoint (https://api.arcgate.dev/trade/v1/mcp).

### Is the arcgate MCP server safe to use?

arcgate scores 54 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 arcgate MCP server expose?

arcgate exposes 7 tools: tradeSearch, tradeQuote, tradeSwap, tradeSwapTx, tradeReceipt, and 2 more. Their descriptions and schemas cost roughly 4,129 tokens of context every time the server is loaded.

### Does the arcgate MCP server require authentication?

No. We connected to arcgate without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the arcgate MCP server still maintained?

arcgate is still listed as active in the MCP registry. We last reached this channel on 2 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.arcgate.dev/trade/v1/mcp
- Website: https://docs.arcgate.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-arcgate-arcgate/trade-v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-arcgate-arcgate/trade-v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-arcgate-arcgate/trade-v1-mcp