How do I install the Mexc Futures REST skill?

Run npx skillmds@latest add mncrftfrcnm/mexc-futures-rest-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Mexc Futures REST safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Mexc Futures REST?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Mexc Futures REST free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Mexc Futures REST?

mncrftfrcnm (@mncrftfrcnm) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Mexc Futures REST by mncrftfrcnm — Agent Skill

Name: Mexc Futures REST
Author: mncrftfrcnm

File contents

MEXC Futures REST

Workflow

Resolve bundled helper paths from the skill root. In Claude Code, use ${CLAUDE_SKILL_DIR}/scripts/...; do not assume the skill is installed under ~/.claude/skills or any fixed repository path.

Use ${CLAUDE_SKILL_DIR}/scripts/mexc_futures_request.py for request construction and signing. Never ask the user to paste API keys into chat, command arguments, source files, logs, or screenshots.

Use the quick commands below first for common tasks. Do not open references or run broad text searches until a quick command or lookup slice is insufficient.
Use MEXC_API_KEY and MEXC_API_SECRET env vars only; the helper enforces credential loading, signed-param placement, redacted dry-runs, method/path/base-url validation, and live-write confirmation.
Use GET /api/v1/contract/detail to confirm contract metadata, precision, leverage limits, and availability before trading.
MEXC is live-only: use tiny sizes and --execute --confirm-live only when clearly requested.
Prefer python "${CLAUDE_SKILL_DIR}/scripts/lookup.py" <topic> over opening full references; for balance/account questions, start with python "${CLAUDE_SKILL_DIR}/scripts/lookup.py" balance.

Quick Commands

python "${CLAUDE_SKILL_DIR}/scripts/mexc_futures_request.py" GET /api/v1/contract/ping
python "${CLAUDE_SKILL_DIR}/scripts/mexc_futures_request.py" GET /api/v1/private/account/assets --signed
python "${CLAUDE_SKILL_DIR}/scripts/mexc_futures_request.py" GET /api/v1/private/account/assets --signed --execute

Rules

Use GET /api/v1/private/account/assets --signed --execute for the current Futures balance snapshot.
Use python "${CLAUDE_SKILL_DIR}/scripts/lookup.py" balance to retrieve compact balance/account commands without loading references.
Futures order placement requires KYC and account-side permission; prefer externalOid.
Back off on rate limits and honor retry guidance when returned.

Verification

After helper edits, run python "${CLAUDE_SKILL_DIR}/scripts/mexc_futures_request.py" --self-test.

---name: mexc-futures-rest-2description: MEXC Futures REST workflows for public contract data, signed account requests, positions, orders, and secure OPEN-API signing without exposing API keys.---# MEXC Futures REST## WorkflowResolve bundled helper paths from the skill root. In Claude Code, use `${CLAUDE_SKILL_DIR}/scripts/...`; do not assume the skill is installed under `~/.claude/skills` or any fixed repository path.Use `${CLAUDE_SKILL_DIR}/scripts/mexc_futures_request.py` for request construction and signing. Never ask the user to paste API keys into chat, command arguments, source files, logs, or screenshots.1. Use the quick commands below first for common tasks. Do not open references or run broad text searches until a quick command or lookup slice is insufficient.2. Use `MEXC_API_KEY` and `MEXC_API_SECRET` env vars only; the helper enforces credential loading, signed-param placement, redacted dry-runs, method/path/base-url validation, and live-write confirmation.3. Use `GET /api/v1/contract/detail` to confirm contract metadata, precision, leverage limits, and availability before trading.4. MEXC is live-only: use tiny sizes and `--execute --confirm-live` only when clearly requested.5. Prefer `python "${CLAUDE_SKILL_DIR}/scripts/lookup.py" <topic>` over opening full references; for balance/account questions, start with `python "${CLAUDE_SKILL_DIR}/scripts/lookup.py" balance`.## Quick Commands```bashpython "${CLAUDE_SKILL_DIR}/scripts/mexc_futures_request.py" GET /api/v1/contract/pingpython "${CLAUDE_SKILL_DIR}/scripts/mexc_futures_request.py" GET /api/v1/private/account/assets --signedpython "${CLAUDE_SKILL_DIR}/scripts/mexc_futures_request.py" GET /api/v1/private/account/assets --signed --execute```## Rules- Use `GET /api/v1/private/account/assets --signed --execute` for the current Futures balance snapshot.- Use `python "${CLAUDE_SKILL_DIR}/scripts/lookup.py" balance` to retrieve compact balance/account commands without loading references.- Futures order placement requires KYC and account-side permission; prefer `externalOid`.- Back off on rate limits and honor retry guidance when returned.## VerificationAfter helper edits, run `python "${CLAUDE_SKILL_DIR}/scripts/mexc_futures_request.py" --self-test`.

Frequently asked questions

Mexc Futures REST