Cryptocapi

What cryptocapi does

The cryptocapi MCP server connects an MCP client to CryptoCapi's market-analysis API. It exposes four tools: get_insight, batch_signals, get_signal, and scan_market. get_insight supports Radar analysis and can also select the Quant Plus engine; the other tools provide multi-asset signals, pair-level quantitative signals, or market rankings.

Responses from the analysis engines include an audit_trail with a protocol_hash. The package passes these values through without reserializing them, allowing the hash from an MCP response to be compared with the result of the same request made directly to the REST API. This supports reproducibility checks, but the hash does not prove that an analysis is correct or identify its origin through a cryptographic signature.

How it works

The cryptocapi MCP server starts locally through npx -y @cryptocapi/mcp and communicates with the MCP client over standard input and output. Tool requests are sent to the CryptoCapi API using the configured API key and base URL. The package returns the API response to the agent, preserving the verification fields supplied by the service.

The tools use different input formats. get_signal expects a trading pair such as BTCUSDT, while batch_signals expects coin identifiers such as bitcoin. Requests for a single asset use a 20-second timeout budget by default; operations that scan multiple assets use 45 seconds.

Setup and configuration

Add the following MCP server entry to a compatible client's configuration:

{
  "mcpServers": {
    "cryptocapi": {
      "command": "npx",
      "args": ["-y", "@cryptocapi/mcp"]
    }
  }
}

No environment variable is required for the public demonstration mode. The package falls back to demo_btc_eth_public, which supports limited Bitcoin and Ethereum requests. Set CRYPTOCAPI_API_KEY to use another key. CRYPTOCAPI_API_BASE changes the API endpoint and defaults to https://api.cryptocapi.com/v1; CRYPTOCAPI_TIMEOUT_MS sets the request budget when a custom value is needed.

A free 14-day trial from CryptoCapi opens all four engines without the demo asset restriction. API access is separated by pass: Radar Alpha, Quant Plus, Quant Pro, and Market Scan are independent entitlements.

Tools and capabilities

• get_insight: returns an asset analysis through Radar. The alpha view includes the verification seal; pulse and alpha have different access requirements.
• get_insight with engine="quant_plus": returns deterministic Quant Plus analysis with a reproducibility seal and input_vector.
• batch_signals: returns Quant Plus signals for multiple assets in one request.
• get_signal: returns a Quant Pro signal for a trading pair.
• scan_market: ranks the market according to a Market Scan strategy.

The demo key allows get_insight and Quant Plus requests only for Bitcoin and Ethereum. Quant Pro and Market Scan remain unavailable with that key, regardless of the requested asset or pair.

Limitations and notes

The cryptocapi MCP server does not expose the former third-party data tools for market summaries, CoinGecko prices, or FRED macro series. Those endpoints remain in the REST API but are not presented as MCP tools because the product focuses on derived intelligence from its own engines.

Each engine requires its own pass, and access to one engine does not unlock another. The protocol hash checks reproducibility and data integrity, not analytical accuracy. The npm package also documents CI-based provenance and recommends npm audit signatures for checking package signatures.