crypto -market-data

This MCP server provides a comprehensive set of tools for blockchain market data and cryptocurrency price analytics. Through HTTP, you can query real-time prices, historical price series, market capitalization, trading volumes, and a variety of market indicators such as price changes, market dominance, cross-chain price aggregates, fiat conversions, sentiment, and technical analysis indicators. Use the available tools to fetch current prices with get_price, retrieve historical data via get_historical_prices, and analyze markets with get_market_cap, get_volume_analytics, and get_price_changes. The server is intended for integration with MCP clients like Claude or the MCP SDK; you can configure your client to connect to the provided URL and transport at https://mcp.hiveintelligence.xyz/hive_market_data/mcp and issue tool invocations in the established MCP request format.

Prerequisites:\n- Docker installed on the host (recommended) or another compatible container runtime.\n- Network access to the MCP endpoint https://mcp.hiveintelligence.xyz/hive_market_data/mcp when using remote access.\n\nInstallation steps (Docker):\n1) Ensure Docker is running on your machine.\n2) Pull and run the MCP market data image (adjust image name if needed):\n docker run -d --name hive-market-data -p 8080:80 hiveintelligence/hive-market-data-mcp\n3) Verify the container is healthy and listening on the configured port (e.g., 8080).\n4) If needed, set environment variables such as MCP_URL and MCP_TRANSPORT to point clients at the remote MCP endpoint.\n5) Connect your MCP client to https://mcp.hiveintelligence.xyz/hive_market_data/mcp using transport http.\n\nNote: If you deploy locally, you may substitute docker run arguments to expose a different port or to supply authentication or telemetry configurations per your environment.

Tips and considerations:\n- The MCP endpoint uses HTTP transport; ensure network security, especially if exposing to the public Internet. Consider reverse proxying and TLS termination if needed.\n- The server supports a broad set of tools (get_price, get_historical_prices, get_market_cap, get_volume_analytics, get_price_changes) for diverse analytics workflows.\n- Some data calls may be rate-limited or subject to latency depending on data source integrations. Implement retry logic and backoff in your client.\n- If you encounter CORS or client authentication issues, verify that the MCP URL and transport configuration in your client match the server settings.\n- Environment variables such as MCP_URL and MCP_TRANSPORT can help standardize client configurations across environments.\n- For production deployments, consider adding monitoring, logging, and security hardening around the container (e.g., limiting access, updating images, and auditing API usage).