Mmcp.market

Coinopai MCP server

by clawdbotworker·io.github.clawdbotworker/coinopai-mcp·v1.2.4·1 stars
No reviews yet

Kronos crypto signals + trade decisions + 819 automation prompts. x402 micropayments, USDC/Base.

B77/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B77/100

full report

Adoption
Growing

1 stars465 downloads/wk

Reviews

Write one

Nobody has reviewed Coinopai yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Coinopai tools (9)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • audit_trade_decision

    The accountability step — verify any decision against real prices. Pass the decision_id from get_crypto_decision and a window (1h/4h/24h). Returns: did the direction hold? What was the PnL%? Verdict: GOOD_DECISION, BAD_DIRECTION, or NOISE. Every decision should be audited. Costs $0.07 USDC.

  • check_trade_preflight

    Step 1 of the trade loop — checks if conditions allow a trade. Returns allowed:true/false, market state, cooldown, signal strength, warnings. If allowed, proceed to get_crypto_decision. Costs $0.05 USDC.

  • get_agent_automation

    Get the full agent automation prompt and workflow steps by slug. Costs $0.01 USDC.

  • get_crypto_decision

    Get a probabilistic trade decision from Kronos — then verify it. Returns CONSIDER_LONG/SHORT/NO_ACTION with confidence, regime, and a decision_id. Call audit_trade_decision with that ID after 1h to see if the decision was right. Full loop: preflight ($0.05) → decision ($0.15) → audit ($0.07) = $0.27 per verified cycle. Costs $0.15 USDC.

  • get_crypto_risk

    Current crypto market risk state (NORMAL/ELEVATED/HIGH), regime detection, equity tracking, signal streaks. Costs $0.02 USDC.

  • get_crypto_signal_history

    Historical 15-minute crypto signals from Kronos — up to 168 hours of BTC/ETH/SOL/XRP/ADA data. Costs $0.05 USDC.

  • get_crypto_signals

    Latest hourly directional signals for BTC, ETH, SOL, XRP, ADA from the Kronos model. Positive = bullish, negative = bearish. Costs $0.05 USDC.

  • list_automation_categories

    List all 35 automation categories with counts. Costs $0.005 USDC.

  • search_agent_automations

    Search 819 agent automation prompts by keyword. Returns matching automations with title, description, complexity and services. Costs $0.01 USDC.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan3 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 2 days ago15/15
  • Maintainer identitynamespace and repository owner differ4/10
Overall 77/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

Install Coinopai in Claude Code, Cursor or VS Code

Runs npx -y coinopai-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add coinopai-mcp -- npx -y coinopai-mcp
Add to Cursor

What the publisher says

From the Coinopai repository's README, as published. We do not edit it. Read it on GitHub

coinopai-mcp

Auditable market context with calibrated forecast ranges and outcome verification.

Source: https://github.com/forgemeshlabs/coinopai-mcp

An MCP server that lets AI agents buy Kronos market context with x402 micropayments on Base. Kronos is not a buy/sell oracle: it gives agents calibrated ranges, risk context, decision journals, and audit records they can verify.

This repo is the MCP client layer; paid intelligence is served from hosted CoinOpAI x402 endpoints.

Weak calls and wrong calls are shown too. That's the point.

Why Kronos Is Different

Most market APIs stop after returning a direction. Kronos leads with calibrated ranges and risk context, then assigns a decision_id so every decision can be audited against future market behavior.

The moat is the audit loop:

preflight -> decision -> audit

Trust the process less. Verify the record more.

Architecture

┌──────────────────────────────────┐
│   Claude Code / AI Agent         │
└──────────────┬───────────────────┘
               │  MCP (stdio)
               ▼
┌──────────────────────────────────┐
│        coinopai-mcp              │
│    npx coinopai-mcp              │
└──────────────┬───────────────────┘
               │  HTTP + 402 payment header
               ▼
┌──────────────────────────────────┐
│      x402.coinopai.com           │
│   Kronos intelligence API        │
└──────────────┬───────────────────┘
               │
               ▼
┌──────────────────────────────────┐
│   Coinbase x402 Facilitator      │
│   USDC settled on Base mainnet   │
└──────────────────────────────────┘

The agent calls a tool → the MCP server receives an HTTP 402 → automatically signs a USDC micropayment → retries with the payment header → data returned. Configure once, pay automatically from the configured low-balance wallet.

Current package: coinopai-mcp@1.2.10.

Settlement note: the MCP pins @x402/core and @x402/evm to 2.11.0 and signs EIP-3009 authorizations with a chain-aware timestamp. This avoids the Base RPC/facilitator clock-skew failure mode where a payment can be rejected as "authorization is not yet valid" or "valid before expired". Successful object responses include x402 settlement metadata under _payment, including the on-chain transaction hash when available.

The Auditable Loop ($0.27/cycle)

check_trade_preflight  ──→  get_crypto_decision  ──→  [wait 1h]  ──→  audit_trade_decision
       $0.05                      $0.15                                      $0.07

   Market state?             Directional context              Outcome record
   Cooldown context?         Confidence context               Direction held?
   Regime context?           + decision_id                    Verdict
   Data freshness?           + audit hint                     + pnl_pct

Every decision is self-verifying. The decision_id links the setup to the outcome. The audit fetches real market prices and produces a verdict. Nothing is hidden.

Current Status

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Coinopai: common questions

Is Coinopai MCP server safe?
Mostly: it is graded B (77/100). Read the Coinopai safety report
How do I install Coinopai?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Coinopai need an API key?
Yes. The registry entry asks for WALLET_PRIVATE_KEY.
Is Coinopai maintained?
The last commit was 2 days ago (2026-09-25). The latest release is v1.2.4.
What can I use instead of Coinopai?
Servers from other publishers that do the same job: AlgoVault — Crypto Quant Trade Calls MCP server, Stelar Signals MCP server and Blockrun MCP server. Compare all Coinopai alternatives.

Alternatives to Coinopai

Same job from other publishers: the closest match first, then the best rated.

All Coinopai alternatives →
  • AlgoVault — Crypto Quant Trade Calls
    The Brain Layer for AI Trading Agents — quant calls + cross-venue arb across perp venues via MCP.
    A
  • Stelar Signals
    Crypto market signals and portfolio telemetry. 6 tools pay-per-call in USDC, no API key.
    A
  • Blockrun
    Web search, deep research, prediction markets & crypto data for AI agents. Pay per call via x402.
    B
  • Agent402.Tools: pay-per-call web tools
    Agentic Finance: 500+ agent tools, multi-chain USDC over x402 or MPP, free via PoW or card credits
    A
  • Trading Signals
    Live AI crypto trading signals for agents. No API key needed to try — 3 signals + hit rate.
    B

More from clawdbotworker →