Rouge

What is Rouge?

Rouge brings together post-quantum cryptography and mcp-native architecture. Built from genesis using NIST-approved post-quantum algorithms—specifically ML-DSA-65 (FIPS 204) for digital signatures and ML-KEM-768 for encryption security. Provides 61 total modular tools across 14 categories (including Wallet, Tokens, DeFi, NFTs, Staking, Smart Contracts, Social, Messaging, Identity, Bridge, and Governance).

Its documented workflow includes: Can be executed directly via npx without a global install (npx @rougechain/mcp-server) or installed globally (npm install -g @rougechain/mcp-server). AI Agent Configuration (Read-Only vs. *Read-only setup:* Integrating the server configuration into an environment like Claude Desktop pointing to the API endpoint (https://api.rougechain.io). The platform documentation describes wallet access this way: Wallet keys and seed phrases are managed locally.

Rouge features

How to use Rouge

1. 1

   MCP Server Installation

   Can be executed directly via npx without a global install (npx @rougechain/mcp-server) or installed globally (npm install -g @rougechain/mcp-server).

2. 2

   AI Agent Configuration (Read-Only vs.

   AI Agent Configuration (Read-Only vs.

3. 3

   *Read-only setup:* Integrating the server

   *Read-only setup:* Integrating the server configuration into an environment like Claude Desktop pointing to the API endpoint (https://api.rougechain.io).

4. 4

   *Write/Signing setup:* Adding a ROUGECHAIN_MNEMONIC

   *Write/Signing setup:* Adding a ROUGECHAIN_MNEMONIC (a 24-word seed phrase) to the environment variables to unlock transaction-signing capabilities.

5. 5

   Write Operations

   29 transaction-signing tools become active when a valid seed phrase environment variable is supplied, allowing the execution of on-chain instructions.

Who is Rouge for?

Rouge is suited to users looking for post-quantum cryptography and mcp-native architecture on RougeChain (Mainnet / Testnet). Its documented workflow includes wallet funding and balance management.

Before you use it

• Exposing your 24-word seed phrase (ROUGECHAIN_MNEMONIC) in unsecure configuration environments can compromise funds; ensure proper local environment hygiene since it authorizes local transaction signing.
• Common troubleshooting steps involve ensuring local ports (e.g., port 5100) are clear of conflicting processes (Address already in use) and verifying that node height properly tracks network status (GET /api/health).
• Cross-chain bridge actions require waiting for relayer polling cycles (up to roughly 2 minutes) and confirming underlying testnet transactions before status updates reflect on-chain.