Technical Architecture

Overview

hive-mcp2 is structured around a single wrapped tool catalog with multiple access surfaces layered on top.

Main Layers

Wrapped tool catalog

This is the live direct tool surface used by the server runtime.

• 512 live direct tools
• provider-backed handlers
• shared schema and metadata normalization

Root MCP endpoint

The root /mcp endpoint is the recommended AI-facing surface.

• compact discovery-oriented tools/list
• resource-based discovery through hive://tools, hive://categories, and hive://providers
• direct tool execution by name

Category-scoped MCP endpoints

These are narrower surfaces built from toolRegistry.ts.

• 14 scoped endpoints
• 389 categorized tools
• direct tools/list results by category

REST API

The REST layer exposes:

• GET /api/v1/tools for the full live wrapped catalog
• POST /api/v1/execute for tool execution

Provider Routing

Requests are routed to provider-specific handlers based on tool metadata.

Current live provider inventory:

• CoinGecko
• DeFiLlama
• GoPlus
• Codex
• CCXT
• GoldRush
• Finnhub
• Tenderly
• Moralis

Discovery Model

There are two important discovery patterns:

1. Root discovery for the full live surface
2. Category-scoped discovery for smaller, more targeted workflows

This distinction is the main reason the docs now separate Tools Reference from Live Catalog.

Related

• API Integration
• Tools Reference
• Data Sources