ClawHub

LI.FI MCP Skill

v1.0.0

Use the LI.FI MCP server through UXC for cross-chain route discovery, bridge/DEX availability checks, token and chain lookup, gas/balance/allowance checks, q...

⭐ 0· 116·1 current·1 all-time
by@jolestar
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description match the actual instructions: all operations target https://mcp.li.quest/mcp via the uxc helper and the documented commands (get-quote, get-chains, get-token, get-status, etc.) are relevant to cross-chain discovery, quotes, and monitoring.
✓
Instruction Scope
SKILL.md confines the agent to discovery and read-only queries. It explicitly warns the skill will not sign or broadcast transactions and advises precheck steps. No instructions tell the agent to read arbitrary local files or exfiltrate data; only an optional env var (LIFI_API_KEY) is suggested for auth.
✓
Install Mechanism
This is an instruction-only skill with no install spec. That is low-risk: nothing is downloaded or written to disk by the skill package itself. It does require an external helper (uxc) to be present on PATH, which is documented.
ℹ
Credentials
The skill does not require any environment variables but documents an optional LIFI_API_KEY for higher rate limits. This is proportionate to the stated purpose; confirm you only provide a non-sensitive API key (not private keys).
✓
Persistence & Privilege
always is false and the skill does not request persistent system-wide changes or access to other skills' configs. The included validate.sh is a publisher-side CI helper, not runtime behavior.
Assessment
This skill looks coherent and read-only: it uses the uxc helper to query the LI.FI MCP endpoint and explicitly avoids signing or broadcasting transactions. Before installing, ensure you: (1) trust the endpoint https://mcp.li.quest/mcp; (2) do not provide any private keys—only an optional API key may be used for rate limits; (3) have vetted the uxc binary (it will be invoked and used to create a small command alias lifi-mcp-cli); and (4) if you run the publisher's validate.sh locally, note it requires ripgrep (rg) and runs repository-path checks. If you need stronger guarantees, ask for the maintainer/source provenance or a minimal review of the uxc binary and its link behavior.

Like a lobster shell, security has layers — review code before you run it.

latestvk973tcgksyg590fzc1603kgz2h833q0k

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments