Log inSubmit server
Coinopai MCP logo

Coinopai MCP

by forgemeshlabs

Pays for crypto market intelligence on Base and records decisions for later price-based audits.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Coinopai MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "forgemeshlabs-coinopai-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "coinopai-mcp"
      ],
      "env": {
        "WALLET_PRIVATE_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 11 tools correctly (1mo ago).

Overview

The forgemeshlabs/coinopai-mcp MCP server exposes paid crypto intelligence tools through a local stdio process. It uses a configured Base wallet to sign USDC x402 micropayments, then retrieves hosted Kronos data over HTTP. Tools cover preflight checks, signals, calibrated forecasts, risk, decision journals, anomaly review, and outcome audits for BTC, ETH, SOL, XRP, and ADA. Reach for it when an agent needs auditable market context rather than an automated trading oracle.

Use cases

  • Gate crypto analysis with market risk and cooldown checks
  • Record model decisions with identifiers for later review
  • Audit directional decisions against subsequent market prices
  • Retrieve calibrated forecast ranges for supported crypto assets
  • Search agent automation prompts and workflow steps

Key features

  • x402 USDC micropayments on Base
  • Decision journals with decision IDs
  • Price-based outcome audits
  • Calibrated crypto forecast ranges
  • Signal history and anomaly review
  • Agent automation search

Tools11

What Coinopai MCP lets your agent do. Expand a tool for its parameters.

Verified live~1.2k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

18/18 checks healthy over the last 77d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7d ago via OSV.dev · coinopai-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads1.1kPackage downloads in the last 30 days.
Last commit18d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed11Callable tools this server registers over MCP.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How Coinopai MCP works

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.

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:

Terminal
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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Coinopai MCP

Run `npx -y coinopai-mcp` through an MCP client's stdio configuration. Set `WALLET_PRIVATE_KEY` in the server environment.

Yes. The README provides a Claude Desktop configuration using `npx -y coinopai-mcp` and the `WALLET_PRIVATE_KEY` environment variable.

No API key or subscription is required. It does require a funded EVM wallet on Base because tool calls are paid in USDC through x402.

Call `get_crypto_decision` to receive a `decision_id`, then call `audit_trade_decision` after the evaluation window. The audit compares the decision with real prices and returns a verdict and PnL percentage.

Related MCP servers

All in Aggregators All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewCoinopai MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/forgemeshlabs-coinopai-mcp?style=directory)](https://allmcps.com/mcp/forgemeshlabs-coinopai-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/forgemeshlabs-coinopai-mcp"><img src="https://allmcps.com/api/badge/forgemeshlabs-coinopai-mcp?style=directory" alt="Coinopai MCP on AllMCPs" /></a>