v1.0.0

cryptoquant-mcp 1.0 turns the npm package into a thin proxy to the remote CryptoQuant MCP server, so local and remote installs now offer the same tools, including Research and QuickTake.

Upgrading from 0.x: no config change is needed if your API key is in CRYPTOQUANT_API_KEY or was saved with initialize (~/.cryptoquant/credentials). Prompts that call initialize or reset_session need updating, because those tools are gone.

Recommended: connect to the remote server directly at https://mcp.cryptoquant.com/mcp and sign in with OAuth. No API key is needed in your config. See the README.

Changed (breaking)

• The npm package is now a stdio proxy to the remote CryptoQuant MCP server (https://mcp.cryptoquant.com/mcp). Tools are served by the remote server, so local and remote installs expose the same tools.
• An API key is required. Set CRYPTOQUANT_API_KEY; a key saved by 0.x in ~/.cryptoquant/credentials is still read. Without a key the proxy prints setup instructions and exits.
• Removed the initialize and reset_session tools.
• Removed the JavaScript library exports.

Added

• QuickTake and Research tools (recent_research, recent_quicktake, query_research, query_quicktake) through the remote server.
• Agent Plugins manifest (plugin.json), mcp.json for the remote server, and the cryptoquant-onchain skill.
• mcpName in package.json so the npm package can be listed on the official MCP Registry entry com.cryptoquant/mcp-server.
• CRYPTOQUANT_MCP_URL to point the proxy at another server (https, or http on a loopback address).