Merxex Exchange

What you should consider before installing: - Metadata vs runtime mismatch: The registry metadata says no env vars and no install, but the SKILL.md expects you to run npx @merxex/mcp and to set MERXEX_AGENT_ID and MERXEX_PRIVATE_KEY. Treat that inconsistency as a red flag — ask the publisher to correct the manifest or clarify why they differ. - Private key risk: The skill asks you to generate and store a secp256k1 private key and use it as MERXEX_PRIVATE_KEY. That key appears to be the agent’s cryptographic identity and likely allows financial operations (escrow, withdrawals). Never put your primary or high-value keys into an untrusted package. Create a dedicated test agent/key with minimal funds for evaluation, and ensure you can revoke the key or that it has limited privileges. - npx install fetches remote code: The MCP integration uses 'npx @merxex/mcp' — this downloads and runs code from npm. Before running, review the @merxex/mcp package source (npm page, repository, version, and checksums). Prefer an audited tarball or an explicit install artifact rather than blind npx execution. - Large file bundle: The skill includes many website/blog/audit files and scripts (SEO and audit tooling). These may be benign documentation, but review them for hardcoded secrets or unexpected endpoints. If you don't need the docs, prefer a minimal client-only package. - Verify endpoints and publisher identity: Confirm the GraphQL endpoint (https://exchange.merxex.com/graphql) and the homepage (https://merxex.com) are controlled by the entity you expect. Check package ownership for @merxex/mcp on npm and inspect its code. If possible, reach out to support@merxex.com to confirm integration details. - Sandbox first: Test in an isolated environment (separate account, separate keys, limited funds). Monitor what network calls the skill makes and audit any artifacts it writes. Consider running the package with network egress restricted until you have reviewed its source. - What would increase confidence: the publisher publishing a clear install spec in registry metadata, a link to the exact @merxex/mcp repository and commit hash, signed release artifacts or checksums, explicit required-env listing in the registry, and a short security writeup explaining key scope and revocation. In short: the skill appears to implement what it claims, but manifest inconsistencies and use of an npx install combined with required private keys justify cautious review before granting credentials or running it in production.