Live Catalog

Hive currently exposes 369 callable tools: 351 wrapped provider tools across 10 category-scoped MCP endpoints plus 18 Hive-native stateful monitoring, memory, alert, report, and B2B subject tools. The root /mcp endpoint keeps tools/list compact at 13 discovery and execution-routing tools; exact tools are called through invoke_api_endpoint, category endpoints, or REST /api/v1/execute.

Use this page when you need the current production shape. For exact names, schemas, required parameters, and pagination cursors, use the live discovery surfaces below instead of copying a cached static table.

Discovery examples

Search by the task your agent is trying to complete, not only by a guessed endpoint name.

curl -X GET "https://mcp.hiveintelligence.xyz/api/v1/tools?search=wallet%20risk&limit=5&fields=name,title,description,inputSchema" \
  -H "Authorization: Bearer YOUR_HIVE_API_KEY"

Useful first searches:

After search, call get_api_endpoint_schema before execution. That is the main difference between Hive as an agent workflow surface and a static endpoint catalog.

Authoritative discovery surfaces

REST catalog

curl -X GET "https://mcp.hiveintelligence.xyz/api/v1/tools?limit=250" \
  -H "Authorization: Bearer YOUR_HIVE_API_KEY"

Useful query parameters:

MCP resources

Read these from the root /mcp endpoint:

• hive://tools -- full live tool inventory
• hive://categories -- category namespaces and endpoint paths
• hive://providers -- active provider integrations
• hive://toolsets -- task-oriented routing maps
• hive://task-canaries -- representative calls for coverage checks
• hive://skills -- skill pack metadata
• hive://status -- runtime status semantics

Schema lookup

Use get_api_endpoint_schema on the root /mcp endpoint before invoking any exact tool. Then call the tool through invoke_api_endpoint.

Category inventory

Hive-native stateful tools

The 18 Hive-native tools are not part of a provider category count. They add persistence and partner-scoped state on top of the provider catalog:

• Monitors: hive_create_monitor, hive_list_monitors, hive_get_monitor, hive_update_monitor, hive_archive_monitor, hive_get_monitor_runs
• Observations and alerts: hive_list_observations, hive_list_alerts, hive_update_alert_status, hive_get_latest_snapshot
• Memory and reports: hive_remember_fact, hive_list_memory_facts, hive_forget_memory_fact, hive_generate_monitor_report
• B2B subjects: hive_list_subjects, hive_get_subject, hive_archive_subject, hive_list_subject_audit_events

Root discovery tools

The root /mcp endpoint exposes these 13 tools to keep general-purpose agents focused:

• search_tools
• get_api_endpoint_schema
• invoke_api_endpoint
• get_market_and_price_endpoints
• get_on_chain_dex_and_pool_endpoints
• get_portfolio_and_wallet_endpoints
• get_token_and_contract_endpoints
• get_defi_protocol_endpoints
• get_nft_analytics_endpoints
• get_security_and_risk_endpoints
• get_network_and_infrastructure_endpoints
• get_search_and_discovery_endpoints
• get_prediction_market_endpoints

Agents should start at root unless they are intentionally constrained to one category. Focused agents can connect directly to one or more category endpoints.

Recommended workflow

1. Call search_tools with the user's natural-language task.
2. Read hive://toolsets if the task is ambiguous or multi-step.
3. Call get_api_endpoint_schema for the selected exact tool.
4. Call invoke_api_endpoint with schema-valid arguments, or call the same tool through REST /api/v1/execute.
5. Report source, freshness, runtime status, and any non-ok provider state.

Example agent routing:

Related

• Tools Overview
• Get Started
• Portfolio & Wallet
• MCP Features
• API Integration