Coinopai MCP

What forgemeshlabs/coinopai-mcp MCP server does

The forgemeshlabs/coinopai-mcp MCP server gives agents access to hosted Kronos crypto intelligence through MCP. Its tools provide market context, risk state, signal history, conformally calibrated forecast ranges, anomaly assessments, and decision records. The supported assets for the main crypto context tools are BTC, ETH, SOL, XRP, and ADA.

A central workflow links three calls: preflight, decision, and audit. Preflight reports whether a market is allowed and includes cooldown, regime, signal, and freshness context. The decision tool creates a probabilistic journal with a decision_id. After the selected evaluation window matures, the audit tool compares the decision with real prices and returns a verdict and PnL percentage.

The project is designed for market intelligence and record verification. The README states that directional results are supporting context, not standalone trade instructions, and that no directional edge has been demonstrated in backtesting.

How it works

The MCP process runs locally over stdio and sends requests to hosted x402 endpoints. When a paid request returns HTTP 402, the client automatically signs a USDC micropayment and retries with the payment header. Payments settle on Base mainnet through the Coinbase x402 facilitator. Successful object responses can include settlement information under _payment, including an on-chain transaction hash when available.

Each tool has a listed per-call price. The documented preflight, decision, and audit sequence costs $0.27 in total: $0.05, $0.15, and $0.07 respectively. Other tools range from $0.005 to $0.07 per call. A funded wallet is therefore required for normal use.

Setup and configuration

Install the package with the documented command:

npx -y coinopai-mcp

Configure the MCP client to run that command and provide WALLET_PRIVATE_KEY in its environment. The key should belong to a dedicated, low-balance EVM wallet on Base. The README recommends installing Coinbase Wallet or another EVM wallet, switching to Base, and supplying USDC for agent payments. It states that the key remains local and that each request uses a signed micropayment rather than a blanket approval.

The package requires Node.js 18 or newer. Claude Code and Claude Desktop configuration examples are provided. When testing from the source checkout, the README advises launching the published package from another directory or a temporary project to avoid npm resolving the local package context.

Tools and capabilities

The forgemeshlabs/coinopai-mcp MCP server exposes these capabilities:

• Check market eligibility, cooldown, regime, and model context before a trade-related decision.
• Create decision journals with confidence, directional context, and a reusable decision_id.
• Audit decisions against later prices and receive direction, PnL, and verdict fields.
• Retrieve current signals, up to 168 hours of signal history, risk state, and cooldown context.
• Request an 80% calibrated price range with approximately 0.80 empirical coverage.
• Review unusual signal conditions using labels, drivers, and component scores.
• Search 819 agent automation prompts and retrieve workflows from 35 categories.

Limitations and notes

The service is not presented as a buy/sell oracle. Directional values can be weak, mixed, or wrong, and audit results expose both successful and unsuccessful decisions. A fresh audit may remain PENDING until its evaluation window matures. The repository is the MCP client layer; the paid intelligence is hosted separately. No API key or subscription is required, but calls consume USDC from the configured Base wallet. The published license is MIT.