Hive Gateway FAQs

Question 1

What is the Hive Gateway?

Accepted Answer

The Hive Gateway serves as a unified discovery surface and centralized API registry for the extensive Hive Civilization Model Context Protocol (MCP) server ecosystem, facilitating seamless integration and access for autonomous AI agents.

Question 2

How does Hive Gateway provide service discovery for MCP servers?

Accepted Answer

It offers a centralized discovery surface at `/.well-known/mcp.json`, where clients can find direct shim URLs for all 22 Hive Civilization MCP servers. This allows for efficient discovery and integration without acting as a proxy for all requests.

Question 3

What core MCP services are hosted directly by Hive Gateway?

Accepted Answer

For legacy compatibility, Hive Gateway directly hosts 5 core MCP services in-process: Evaluator (for ERC-8183), Trade (for SMB invoice settlement), DePIN (for provider marketplaces), Compute Grid (for compute auctions), and Morph (for polymorphic identity).

Question 4

Is Hive Gateway intended to be a hot-path proxy for all Hive Civilization services?

Accepted Answer

No, Hive Gateway's primary role is discovery. While it provides a central point for finding services and hosts some legacy services, direct shim URLs are recommended for Glama/Smithery probes and direct interaction with individual MCP servers, rather than using the gateway as a hot-path proxy.

Question 5

What is the Model Context Protocol (MCP) within the Hive Civilization?

Accepted Answer

The Model Context Protocol (MCP) is a foundational communication standard that defines how servers within the Hive Civilization ecosystem interact. It enables interoperability, context sharing, and structured communication, particularly crucial for the coordination of AI and autonomous agents.

Hive Gateway

Hive Gateway

主要功能

使用案例

主要功能

使用案例