1inch MCP
REMOTE · API.1INCH.COM · SCANNED SEP 22
Doc search, intent & cross-chain swaps, limit orders, portfolio, spot prices, gas & all APIs.
Available components
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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (swap). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 7640 tokens (~347/item across 22 items; 10 tools + 12 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 Management94
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the 1inch MCP server?
1inch MCP is a hosted endpoint at https://api.1inch.com/mcp/protocol, 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 · api.1inch.com
claude mcp add --transport http com-1inch-business-mcp 'https://api.1inch.com/mcp/protocol'
{
"mcpServers": {
"com-1inch-business-mcp": {
"url": "https://api.1inch.com/mcp/protocol"
}
}
} {
"servers": {
"com-1inch-business-mcp": {
"type": "http",
"url": "https://api.1inch.com/mcp/protocol"
}
}
} [mcp_servers.com-1inch-business-mcp] url = "https://api.1inch.com/mcp/protocol"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-1inch-business-mcp": {
"type": "remote",
"url": "https://api.1inch.com/mcp/protocol",
"enabled": true
}
}
} openclaw mcp add com-1inch-business-mcp --url 'https://api.1inch.com/mcp/protocol' --transport streamable-http
mcp_servers:
com-1inch-business-mcp:
url: "https://api.1inch.com/mcp/protocol" {
"McpServers": {
"com-1inch-business-mcp": {
"Transport": "http",
"Url": "https://api.1inch.com/mcp/protocol"
}
}
} assistant mcp add com-1inch-business-mcp -t streamable-http -u 'https://api.1inch.com/mcp/protocol'
{
"mcpServers": {
"com-1inch-business-mcp": {
"type": "http",
"url": "https://api.1inch.com/mcp/protocol"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 17 Sept 26 0
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “aqua” rewrote its description, which is the text the model reads security
- “aqua” dropped the required parameter “deadline” ▼ functional
- “aqua” dropped the required parameter “exactIn” ▼ functional
- “aqua” reworded the description of “action” cosmetic
- “aqua” reworded the description of “strategy” cosmetic
- “aqua” dropped the optional parameter “amount” cosmetic
- “aqua” dropped the optional parameter “taker” cosmetic
- “aqua” dropped the optional parameter “threshold” cosmetic
- “aqua” dropped the optional parameter “tokenIn” cosmetic
- “aqua” dropped the optional parameter “tokenOut” cosmetic
- 16 Sept 26 −1
- Stability: pass → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “aqua” rewrote its description, which is the text the model reads security
- Tool “walletconnect” rewrote its description, which is the text the model reads security
- Tool “aqua” is now declared destructive security
- Schema quality: 313 → 353 ▼ functional
- “aqua” added a required parameter “confirmed”, so existing callers break ▼ functional
- “aqua” added a required parameter “deadline”, so existing callers break ▼ functional
- “aqua” added a required parameter “exactIn”, so existing callers break ▼ functional
- “aqua” added a required parameter “feeBpsIn”, so existing callers break ▼ functional
- “aqua” added a required parameter “priceRange”, so existing callers break ▼ functional
- “aqua” added a required parameter “tokens”, so existing callers break ▼ functional
- “aqua” added an optional parameter “amount” cosmetic
- “aqua” added an optional parameter “execute” cosmetic
- “aqua” added an optional parameter “openingPrice” cosmetic
- “aqua” added an optional parameter “previewRef” cosmetic
- “aqua” added an optional parameter “strategy” cosmetic
- “aqua” added an optional parameter “taker” cosmetic
- “aqua” added an optional parameter “threshold” cosmetic
- “aqua” added an optional parameter “tokenIn” cosmetic
- “aqua” added an optional parameter “tokenOut” cosmetic
- “aqua” added an optional parameter “walletSessionToken” cosmetic
- “aqua” reworded the description of “action” cosmetic
- “aqua” reworded the description of “app” cosmetic
- “aqua” reworded the description of “chainId” cosmetic
- “aqua” reworded the description of “maker” cosmetic
- “aqua” reworded the description of “strategyHash” cosmetic
- “walletconnect” reworded the description of “action” cosmetic
- 26 Aug 26 +7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 −6
- Stability: 0.97 → pass security
- Tool “walletconnect” rewrote its description, which is the text the model reads security
- Schema quality: excellent → unverified ▼ functional
- 22 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “debug” rewrote its description, which is the text the model reads security
- Tool “orderbook” rewrote its description, which is the text the model reads security
- Tool “product_api” rewrote its description, which is the text the model reads security
- Tool “swap” rewrote its description, which is the text the model reads security
- New tool “authenticate” functional
- 21 Aug 26 0
- Tool “product_api” rewrote its description, which is the text the model reads security
- 20 Aug 26 0
- Tool “walletconnect” rewrote its description, which is the text the model reads security
- “walletconnect” reworded the description of “walletSessionToken” cosmetic
- 19 Aug 26 0
- New resource “x402-payments” functional
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 22 Sept 2026 · Probed https://api.1inch.com/mcp/protocol
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=1inch.com | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 13 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ce222ec1b17533ca0e100fd8c4a38351 |
| SANs: 1inch.com, *.1inch.com | ||||||
| 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 secure
Validation of api.1inch.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| 1inch.com. | present | 2371 | 13 | Verified |
| api.1inch.com. | Verified address RRset verified with the apex keys |
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=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self';script-src 'self';style-src 'self';img-src 'self' data: https:;connect-src 'self';font-src 'self';object-src 'none';media-src 'self';frame-src 'none';base-uri 'self';form-action 'self';frame-ancestors 'self';script-src-attr 'none';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.1inch.com/mcp/protocol | Verified | 200 | |
| http (plaintext) | http://api.1inch.com/mcp/protocol | HTTPS enforced | 301 | https://api.1inch.com/mcp/protocol |
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 →
aqua ~920
1inch Aqua (shared-liquidity market making): position analytics plus maker position writes. Write actions (OAuth, or WalletConnect + signed 1inch ToS (pass walletSessionToken after MCP session rotation); non-custodial — the user's wallet signs): create_position (two-phase: call once for a preview + previewRef, then again with confirmed:true), close_position (confirmed:true; closing is permanent). Anonymous writes execute only via WalletConnect (execute=false is rejected). REQUIRED: "action" — read actions (no OAuth): maker_stats, list_maker_strategies, strategy_overview, strategy_activity, strategy_volume, list_opened. Read the resource file://1inch-mcp/guides/aqua-workflow for per-action examples, priceRange semantics, and maker position flows. Raw HTTP: product_api with path "/aqua/v1.0/strategies/...".
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Invalid or missing "action" parameter. Must be one of: "maker_stats", "list_maker_strategies", "strategy_overview", "strategy_activity", "strategy_volume", "list_opened", "create_position", "close_po… |
| address | string | – | Maker EVM address (maker_stats, list_maker_strategies). |
| app | string | – | App / AquaSwapVMRouter address (strategy_* reads, close_position). |
| chainId | – | yes | EVM chain ID (number) for single-strategy / write actions, or an array of chain IDs for list/stats filters. |
| confirmed | boolean | yes | create_position: omit to preview, pass true with previewRef to encode (create_position is two-phase: call without confirmed to receive a preview and previewRef (no calldata); review it, then call aga… |
| cursor | string | – | Opaque pagination cursor from a previous response. |
| execute | boolean | – | Optional. When a WalletConnect session is active, defaults to true: the transaction is sent via the wallet (user confirms the prompt). Authenticated sessions may set execute=false to return calldata… |
| feeBpsIn | integer | yes | Optional taker fee in basis points for create_position (1-500). |
| granularity | string | – | Volume series bucket (strategy_volume). |
| limit | integer | yes | Page size for list/activity/volume actions. |
| maker | string | – | Maker EVM address (strategy_* reads, create_position). |
| openingPrice | string | – | Opening price as a positive decimal string (token1 per token0, whole units). An XYC position opens at amount1 / amount0, so the preview derives it from the leg amounts when both tokens' decimals are… |
| previewRef | string | – | Short-TTL preview reference returned by the create_position preview call. Pass it back together with confirmed: true to encode; a stale, used, or mismatched ref is refused (no silent re-encode). |
| priceRange | object | yes | Optional concentrated-liquidity range for create_position (rawPriceMin/rawPriceMax in 1e18). |
| sort | string | – | Sort direction for list/activity/volume (asc|desc). |
| status | array | yes | Filter by lifecycle status for list_maker_strategies (e.g. ["open"]). |
| strategy | string | – | Encoded strategy/order bytes (close_position). |
| strategyHash | string | – | Strategy hash (strategy_* reads, close_position). |
| tokens | – | yes | create_position: exactly two legs [{ token, amount }, { token, amount }] (amount in smallest units, as a string). close_position: array of token addresses to withdraw. |
| walletSessionToken | string | – | Optional durable WalletConnect token from walletconnect connect. Anonymous writes must pass it after MCP session rotation (or after any walletconnect call that already used it on this session). Ignor… |
No output schema declared.
No examples provided.
authenticate ~77
Call this to start or confirm 1inch Business login. HTTP 401 means you are still anonymous (initialize 200 is not login). After OAuth, call again until the result is authenticated: true with organizationId. Then use swap, orderbook, product_api, or debug. Do not treat a PaymentRequired / x402 result as login.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
debug ~337
[Requires authentication] Call the authenticate tool first to start or confirm 1inch Business login (initialize 200 is still anonymous). If authenticate or this tool returns HTTP 401, complete OAuth, then retry. Look up production API request logs for your 1inch Business organization to troubleshoot integration issues. Results are always scoped to your authenticated organization. Two modes: 1) By request id: pass requestId (the x-request-id header returned on 1inch API responses). Optionally narrow startTime/endTime (defaults: last 24 hours ending now). 2) Logs in a time window: omit requestId and pass both startTime and endTime (RFC3339). Optionally set logLevel ("info", "warn", or "error") to filter by severity; omit to return all levels. Limits: each call covers at most a 24-hour window; how far back you can query depends on your plan's log retention.
| Name | Type | Req | Description |
|---|---|---|---|
| endTime | string | – | RFC3339 end of query window. Defaults to now when omitted. |
| limit | number | – | Max log lines (max 100) |
| logLevel | string | – | Filter by log level: "info", "warn", or "error". Omit to return all levels. Only applies to time-window mode (ignored when requestId is set). |
| requestId | string | – | Production x-request-id (or correlation id) to find logs for. When set, searches JSON logs for this value scoped to your organization. |
| startTime | string | – | RFC3339 start of query window. With requestId, defaults to 24h before endTime. |
No output schema declared.
No examples provided.
get_example ~92
Get the full source code of an SDK example. Use list_examples first to see available examples.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | – | Optional: specific file path to retrieve (e.g., 'src/evm/swap-native.ts'). If omitted, returns all files. |
| name | string | yes | Example name (e.g., '@1inch-examples/intent-swap', '@1inch-examples/limit-order') |
No output schema declared.
No examples provided.
list_examples ~27
List all available SDK code examples. Returns example names that can be used with get_example tool.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
orderbook ~575
[Requires authentication] Call the authenticate tool first to start or confirm 1inch Business login (initialize 200 is still anonymous). If authenticate or this tool returns HTTP 401, complete OAuth, then retry. Limit orders via the 1inch Orderbook API (v4.1). IMPORTANT: The "action" parameter is REQUIRED. Must be one of: "build", "create", "list", "cancel". Actions with example parameters: 1. build (recommended first step): { "action": "build", "chain": 1, "makerAsset": "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48", "takerAsset": "0xdAC17F958D2ee523a2206206994597C13D831ec7", "makingAmount": "1000000", "takingAmount": "990000", "makerAddress": "0x..." } Optional: expirationSeconds (default 604800 = 7 days). With an active WalletConnect session, the order is signed and submitted automatically (set execute=false to return typed data only). 2. create (after signing typedData from build): { "action": "create", "chain": 1, "orderHash": "0x...", "signature": "0x...", "orderData": { ... } } 3. list (query orders): - By maker: { "action": "list", "chain": 1, "listMode": "by_maker", "makerAddress": "0x..." } - By hash: { "action": "list", "chain": 1, "listMode": "by_hash", "orderHash": "0x..." } - Browse: { "action": "list", "chain": 1, "listMode": "all", "limit": 10 } 4. cancel (inspect + guidance): { "action": "cancel", "chain": 1, "orderHash": "0x..." } Typical flow: build -> sign typedData -> create (or one build call when WalletConnect is connected — order signed and submitted automatically). The maker asset may require a one-time ERC-20 approval for the Limit Order Protocol; it costs native gas even though the limit order itself is gasless. When a build response includes an "approval" block, tell the user upfront (approval.estimatedCost holds the estimated cost in native units) and broadcast the included approveTx before signing. With WalletConnect, the approve is sent automatically — "approvalTxSent": true means the first wallet prompt w…
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
product_api ~1,508
[Requires authentication] Call the authenticate tool first to start or confirm 1inch Business login (initialize 200 is still anonymous). If authenticate or this tool returns HTTP 401, complete OAuth, then retry. Call any 1inch product API endpoint using the authenticated user's credentials (base URL is the unified gateway, e.g. https://api.1inch.com). Call authenticate first. Anonymous sessions get HTTP 401 (OAuth), not x402. After a real org login, quota-exhausted routes may return a PaymentRequired tool result; retry with a signed payment in _meta["x402/payment"] (batch-settlement scheme only — see file://1inch-mcp/guides/x402-payments). Do not treat PaymentRequired as login. Optional: if your client can read MCP resources, file://1inch-mcp/guides/api-index has live Swagger links and extra gateway notes (mirrors business.1inch.com/portal/llms.txt). Common chain IDs: Ethereum=1, BNB=56, Polygon=137, Arbitrum=42161, Optimism=10, Base=8453, Avalanche=43114, Gnosis=100, zkSync=324, Linea=59144, Sonic=146, Unichain=130, Cronos=25, Monad=10143, Solana=501 (where applicable). Gateway products (use these path prefixes with this tool): - Portfolio: /portfolio/portfolio/v5.0/... — example path="/portfolio/portfolio/v5.0/general/current_value", query={"addresses":"0x..."}; token metrics path="/portfolio/portfolio/v5.0/tokens/metrics", query={"addresses":"0x...","timerange":"1year"} - Balance: /balance/v1.2/{chainId}/... — example path="/balance/v1.2/1/balances/0x..." - Spot Price: /price/v1.1/{chainId} — example path="/price/v1.1/1", method="POST", body={"tokens":["0x..."],"currency":"USD"} - Token: /token/v1.4/{chainId}/... — example path="/token/v1.4/1/search", query={"query":"USDC"} (prefer v1.4; older v1.2 chain search is deprecated in OpenAPI) - Token Details: /token-details/v1.0/details/{chain}/{tokenAddress} — example path="/token-details/v1.0/details/1/0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48" - Gas Price: /gas-price/v1.6/{chainId} — example path="/gas-price/v…
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | Request body for POST requests |
| method | string | – | HTTP method |
| path | string | yes | API path (e.g. /portfolio/portfolio/v5.0/general/current_value — unified gateway prefix) |
| query | object | – | Query parameters as key-value pairs |
No output schema declared.
No examples provided.
search ~80
Search 1inch documentation and API reference
| Name | Type | Req | Description |
|---|---|---|---|
| include_body | boolean | – | Include full document body in results (default true). Set to false for smaller responses. |
| limit | number | – | Maximum results per collection (default 10) |
| page | number | – | Page number for pagination (default 1) |
| query | string | yes | Search query string |
No output schema declared.
No examples provided.
swap ~1,000
[Requires authentication] Call the authenticate tool first to start or confirm 1inch Business login (initialize 200 is still anonymous). If authenticate or this tool returns HTTP 401, complete OAuth, then retry. Swap tokens via 1inch. Supports classic (on-chain), Fusion (intent/gasless), and cross-chain swaps. Omit preferredType and the tool picks a type for you; set preferredType (classic, fusion, crosschain) to choose explicitly. When quoteOnly returns a `recommended` type and that type is available, present **only** that type to the user. Do not mention, compare, or suggest other swap types unless the user explicitly asks to compare alternatives. ERC-20 source tokens may require a one-time approval transaction before the swap can proceed; the approval costs native gas on the source chain even for gasless Fusion/cross-chain swaps. When a response includes an `approval` block, tell the user upfront (approval.estimatedCost holds the estimated cost in native units). Usage modes: 1. **Quote** (quoteOnly=true): Returns only one swap type and its quote. If you pass `preferredType` explicitly (classic, fusion, or crosschain), the response returns that exact type (when a quote for it is available). If `preferredType` is omitted, the tool compares classic, Fusion, and cross-chain internally and picks the best one. The chosen type is echoed as `recommended`. 2. **Execute** (default): Returns data to sign. Response type depends on swap mode: - Classic → {type:"classic", step:"approve"|"swap", tx:{to,data,value}} → sign with eth_sendTransaction, wait for receipt. If step="approve", sign the approve tx first, then call swap again for the actual swap tx. - Fusion → {type:"fusion", orderHash, typedData} → sign typedData with eth_signTypedData_v4, then call this tool again with signedOrder=<signature> and orderHash. - Cross-chain → {type:"crosschain", orderHash, typedData, srcChain, dstChain} → same as Fusion: sign typedData, then submit with signedOrder. 3. **Submit…
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount in wei/smallest unit. Pass large amounts as a string to avoid precision loss. |
| chain | integer | yes | Chain ID (e.g. 1 for Ethereum, 8453 for Base) |
| dst | string | yes | Destination token address or symbol (e.g. ETH, 0x...) |
| dstChain | integer | – | Destination chain for cross-chain swap |
| execute | boolean | – | Optional. When a WalletConnect session is active, defaults to true: classic approve/swap txs, Fusion/cross-chain EIP-712 sign+submit, and native escrow sends are handled via the wallet (user confirms… |
| from | string | yes | Wallet address executing the swap |
| gasPrice | string | – | Network gas price in wei (optional; omit for fast default) |
| orderHash | string | – | Order hash for submit mode |
| preferredType | string | – | Preferred swap type; the tool picks one if omitted |
| preset | string | – | Order preset for fusion/cross-chain: fast (quicker fill), medium, slow (better rate) |
| quoteOnly | boolean | – | If true, return quote comparison only (no tx/order) |
| signedOrder | string | – | Signed EIP-712 order (submit mode) |
| slippage | number | – | Slippage tolerance in % (default 0.5) |
| src | string | yes | Source token address or symbol (e.g. USDC, 0x...) |
No output schema declared.
No examples provided.
walletconnect ~1,601
Pair and use an EVM and/or Solana wallet via WalletConnect v2. **No authentication required** — available to every user (including unauthenticated/anonymous). Non-custodial: the server never holds keys and the user approves every signature/transaction in their own wallet. **Pairing proposal** is controlled per request via optional `pairingTarget` on `action: "connect"`: `eth` (default, eip155 only), `solana`, or `both`. Many mobile wallets fail if eip155 and solana are proposed together; prefer `eth` or `solana` unless the user needs both in one session. **Every call must include `action`** (string). **Connect QR (critical for assistants):** On `action: "connect"`, successful responses return **(1) an MCP `type: "image"` PNG** of the pairing QR (render this even if the host has no `resources/read`), then **(2) optional `resource_link`**, then **(3) text JSON** with `pairingQrResourceUri`, `presentation`, `nextSteps`, `url`, optional `mobileDeeplinks`, etc. **Desktop / scan UX:** show the image content block first. **Mobile / no-camera:** follow `nextSteps`; when present, `mobileDeeplinks` lists HTTPS `url` (+ `nativeUrl`) per curated WalletConnect wallet. Raw `wc:` (`url` / `walletConnectLinkForUser`) remains fallback. **Avoid calling `connect` again while pairing is still in progress** unless the user must reset — pass `walletSessionToken` to resume the same pairing after MCP session rotation. **Flow:** (1) `connect` as above. (2) User approves in the wallet (EVM only, Solana only, or both). (3) `status` until `kind` is `session` — optional `evm` / `solana` blocks; `address`/`chains` remain legacy EVM when EVM is connected. (4) `sign` / `send_transaction` or swap `execute=true` (swap execute remains EVM unless extended elsewhere). `kind: "pending"` on `status` is success — keep polling. **Actions (exact JSON shapes):** - **connect** — `{ "action": "connect", "sessionTtlDays"?: number, "pairingTarget"?: "eth" | "solana" | "both", "walletSessionToken"?: string }`…
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Required. One of: connect (start pairing), status (session info), sign (EVM + Solana WC methods), send_transaction (EVM eth_sendTransaction or Solana solana_signAndSendTransaction), accept_terms (wri… |
| address | string | – | Optional; only with action "accept_terms". EVM address that signs the Terms-of-Use acceptance; must belong to the active WalletConnect session. When omitted, the session's primary EVM account is used. |
| chainId | integer | – | Optional; only when action is "sign" and method is personal_sign (EVM numeric chain id). Must be omitted for eth_signTypedData_v4, Solana methods, send_transaction, and other actions. |
| method | string | – | Required when action is "sign". EVM: personal_sign | eth_signTypedData_v4. Solana: solana_signMessage | solana_signTransaction. Omit for connect, status, send_transaction, disconnect. |
| pairingTarget | string | – | Optional; only with action "connect". What to advertise in the WalletConnect proposal: "eth" (eip155 only, default), "solana" only, or "both". Many mobile wallets fail if eip155 and solana are propos… |
| params | array | – | Required when action is "sign": exactly two items. personal_sign: [message, 0xAddress]. eth_signTypedData_v4: [0xSigner, typedDataJsonString]. solana_signMessage: [message, pubkey]. solana_signTransa… |
| sessionTtlDays | integer | – | Optional; only with action "connect". How long to persist this WalletConnect client state in Redis (days). Server clamps to [1, WALLETCONNECT_SESSION_TTL_DAYS_MAX] and defaults when omitted. |
| solanaChainId | string | – | Optional; only when action is "sign" and method is solana_signMessage or solana_signTransaction. CAIP-2 string (e.g. solana:5eykt4…). When omitted, the server uses the first Solana chain on the sessi… |
| tx | object | – | Required when action is "send_transaction". EVM or Solana shape — see `tx` field descriptions. Omit for connect, status, sign, disconnect. |
| walletSessionToken | string | – | Optional durable token for ANONYMOUS (unauthenticated) sessions. `connect` mints a fresh token; store it and pass it back on status/sign/send_transaction/accept_terms/disconnect (and on a later `conn… |
No output schema declared.
No examples provided.
What is the 1inch MCP server?
1inch MCP is listed in the public MCP registry as com.1inch.business/mcp. Doc search, intent & cross-chain swaps, limit orders, portfolio, spot prices, gas & all APIs. This page covers its hosted endpoint (https://api.1inch.com/mcp/protocol).
Is the 1inch MCP server safe to use?
1inch MCP scores 81 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 1inch MCP server expose?
1inch MCP exposes 10 tools: search, list_examples, get_example, authenticate, swap, and 5 more. Their descriptions and schemas cost roughly 6,217 tokens of context every time the server is loaded.
Does the 1inch MCP server require authentication?
No. We connected to 1inch MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the 1inch MCP server still maintained?
1inch MCP is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.