paraswap-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PARASWAP_RPC_URLS_1 | No | JSON-RPC endpoint for chain 1 (Ethereum). Public nodes are used when unset. | |
| PARASWAP_RPC_URLS_8453 | No | JSON-RPC endpoint for chain 8453 (Base). Public nodes are used when unset. | |
| PARASWAP_ALLOWED_CHAINS | No | Comma-separated chain ids the server will serve, e.g. 1,42161. An empty or malformed value refuses to start. Leave unset to use defaults (1,42161,8453). | |
| PARASWAP_RPC_URLS_42161 | No | JSON-RPC endpoint for chain 42161 (Arbitrum One). Public nodes are used when unset. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| build_swap_transactionA | Build a token swap via Paraswap v5 on Ethereum (1), Arbitrum One (42161) or Base (8453). Returns an ORDERED list of raw transactions, each with to/data/value ready for wallet preview and execution: an exact-amount ERC-20 approve when the current allowance is short (preceded by a reset to zero when a partial allowance already exists — USDT-style tokens revert otherwise), then the swap. Execute them in order; do not reorder, skip or batch. Quotes are fetched fresh on every call and expire in minutes: build right before executing. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clearly and specifically stated.
The single tool uses a clear verb_noun pattern ('build_swap_transaction'). There are no other tools to introduce inconsistency.
One tool is too few for a server that might be expected to provide a broader range of swap-related operations (e.g., quoting, token info). The scope feels thin.
The tool covers the core swap workflow by returning ordered transactions including approval and swap. However, it lacks separate quote retrieval or token discovery capabilities, which are minor gaps for a swap-focused server.