Hive Intelligence

Created By
hive-intel9 months ago
The Ultimate Cryptocurrency MCP for AI Assistants - Unified access to crypto, DeFi, and Web3 analytics | MCP Endpoint
Overview

what is Hive Intelligence?

Hive Intelligence is a Model Context Protocol (MCP) server that provides comprehensive cryptocurrency and Web3 analytics through intelligent tool orchestration, enabling AI assistants to access a wide range of data.

how to use Hive Intelligence?

To use Hive Intelligence, install the server dependencies, build the server, and start it. Configure your MCP client or Claude Desktop with the provided settings to access the analytics.

key features of Hive Intelligence?

  • Unified access to over 200+ specialized tools for crypto and Web3 analytics.
  • Dynamic and category-specific access to market data, on-chain analytics, and portfolio tracking.
  • Support for various analytics categories including DeFi, NFT, and security analysis.

use cases of Hive Intelligence?

  1. Analyzing cryptocurrency market trends and price movements.
  2. Tracking and managing crypto portfolios and wallets.
  3. Conducting security and risk assessments for blockchain projects.

FAQ from Hive Intelligence?

  • What types of analytics does Hive Intelligence provide?

Hive Intelligence offers market data, on-chain analytics, portfolio tracking, and more across various categories.

  • Is Hive Intelligence suitable for developers?

Yes! Hive Intelligence is designed for developers looking to integrate cryptocurrency analytics into their applications.

  • How can I contribute to Hive Intelligence?

You can contribute by visiting our GitHub repository and submitting pull requests or issues.

Server Config

{
  "mcpServers": {
    "hive-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-hive"
      ]
    }
  }
}
Project Info
Created At
9 months ago
Updated At
9 months ago
Author Name
hive-intel
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago