An MCP server for NEAR intent swaps using the Defuse Protocol one-click SDK.
The server implements 5 clearly named, well-described tools for NEAR intent swaps with comprehensive parameter documentation. Tool names follow the verb_noun convention (GET_, EXECUTE_, CHECK_). All parameters have type definitions and descriptions. However, output schemas are not explicitly documented in the source code, and error handling strategies are not visible. The tool descriptions are exceptionally detailed (150-300+ chars each) with explicit WHEN to use guidance and step numbering that aids multi-step planning. Parameter enums are properly constrained (EXACT_INPUT/EXACT_OUTPUT, recipientType, etc.). All tools include dependency hints ('use GET_NEAR_SWAP_TOKENS first' for discovery). The main weakness is the absence of documented return schemas and error recovery guidance in the source.
[STEP 5] Check the current execution status of a NEAR intent swap. Returns the swap state (PENDING_DEPOSIT, PROCESSING, SUCCESS, REFUNDED, FAILED, etc.) along with detailed transaction information. Use this to monitor swap progress after initiating the swap, and continue polling until the swap is complete.
[STEP 4] Submit a deposit transaction hash to initiate the swap after sending funds to the deposit address. This notifies the 1Click service that funds have been sent and triggers the swap execution process. Use this after users have sent their funds to the deposit address from the full quote response.
[STEP 2] Get a full quote with deposit address for a NEAR intent swap. This requires recipient and refund addresses and returns a unique deposit address where users can send their funds to initiate the swap. Use this when users are ready to proceed with the swap after checking the simple quote. NOTE: If users provide simple token names (e.g., 'ETH', 'USDC'), first use GET_NEAR_SWAP_TOKENS to discover the exact token IDs required for this API.
[STEP 1] Get a simple quote for a NEAR intent swap between different chains and assets. This is a dry run that doesn't require any addresses - perfect for users who want to check swap rates and fees before committing to a swap. Use this when users want to explore swap options without providing recipient addresses. NOTE: If users provide simple token names (e.g., 'ETH', 'USDC'), first use GET_NEAR_SWAP_TOKENS to discover the exact token IDs required for this API.
Output schemas not documented in source code. While parameter input schemas are well-defined (types, descriptions, enums), return types and response structures are not explicitly declared. This forces LLMs to guess what fields to expect from responses and complicates downstream chaining.
Error handling and recovery guidance not visible in tool definitions. No error classification (retryable vs. user-fixable vs. fatal), no actionable error messages, no recovery steps. Tools rely on upstream SDK error handling.
EXECUTE_NEAR_SWAP (write operation) lacks confirmation/dry-run pattern. This is a state-modifying tool that submits deposits to initiate swaps. No dry-run option documented, no confirmation step, no rollback guidance if the swap fails after execution.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | C | 64 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 49 | - | v1 |
[DISCOVERY] Get a list of tokens currently supported by the 1Click API for NEAR Intents. Returns token metadata including blockchain, contract address, current USD price, symbol, decimals, and price update timestamp. Use this to help users discover available tokens before requesting quotes.
Parameter cardinality not enforced. GET_NEAR_SWAP_FULL_QUOTE has 14 parameters, several optional with interdependencies (e.g., recipientType determines valid recipient formats, refundType depends on refundTo). Undocumented parameter relationships could lead to silent misuse.
Result limits not documented. GET_NEAR_SWAP_TOKENS returns a list of supported tokens with no declared pagination, limit, or total count. Large token lists could bloat context without constraint guidance.