LI.FI MCP Skill

Use this skill to run LI.FI MCP operations through uxc.

Reuse the uxc skill for generic protocol discovery, auth binding, envelope parsing, and error handling.

Prerequisites

• - uxc is installed and available in PATH.
• Network access to https://mcp.li.quest/mcp.
• Optional: a LI.FI API key for higher rate limits.

Core Workflow

1. 1. Verify endpoint and protocol with help-first probing:

1. 2. Optional auth setup for higher rate limits:

1. 3. Use a fixed link command by default:

1. 4. Inspect operation schema before execution:

1. 5. Prefer discovery first, then route/quote, then execution-precheck queries.

Capability Map

• - Chain and token discovery:

• - Route discovery and provider availability:

• - Quotes and route planning:

• - Wallet prechecks:

• - Monitoring and service checks:

Always inspect host help and operation help in the current endpoint version before relying on an operation name or argument shape.

Recommended Usage Pattern

1. 1. Discover chain IDs dynamically:

1. 2. Resolve token addresses before quoting:

1. 3. Check whether a route exists before asking for a quote:

1. 4. Generate the quote:

1. 5. Validate execution preconditions:

1. 6. Use get-status only after the externally signed transaction has been broadcast.

Guardrails

• - Keep automation on JSON output envelope; do not rely on --text.
• Parse stable fields first: ok, kind, protocol, data, error.
• Use lifi-mcp-cli as the default command path.
• INLINECODE52 is equivalent to uxc https://mcp.li.quest/mcp <operation> ... when the same auth binding is configured.
• Use direct uxc "<endpoint>" ... only as a temporary fallback when link setup is unavailable.
• Prefer key=value for simple arguments and positional JSON for nested objects.
• This endpoint is read-only from the agent perspective:

• - Do not present get-quote or get-step-transaction as executed trades; they are execution plans only.
• Before suggesting an ERC20 route as ready to execute, check allowance if the route needs approval.
• Prefer get-routes only when the user explicitly wants multiple alternatives; default to get-quote for the best route.
• In live testing, chain lookup tools accepted names, but token/balance/allowance tools were more reliable with numeric chain IDs. Prefer numeric IDs after discovery.

Tested Real Scenario

The endpoint was verified through uxc host discovery and returned a live MCP tool list including:

• - INLINECODE62
• INLINECODE63
• INLINECODE64
• INLINECODE65
• INLINECODE66
• INLINECODE67
• INLINECODE68
• INLINECODE69
• INLINECODE70
• INLINECODE71
• INLINECODE72
• INLINECODE73
• INLINECODE74
• INLINECODE75

This confirms the skill target is a real hosted MCP surface accessible via UXC.

References

• - Invocation patterns: