CoReason Ecosystem — Federated MCP Gateway vs HAPI MCP Server

Side by side on the facts. GitHub figures come straight from each repository; ratings come from signed-in reviewers here.

MetricCoReason Ecosystem — Federated MCP GatewayMCP Server HAPI MCP ServerMCP Server

Type: CoReason Ecosystem — Federated MCP GatewayMCP Server; HAPI MCP ServerMCP Server
Category: CoReason Ecosystem — Federated MCP GatewayAPI Tools; HAPI MCP ServerAPI Tools
GitHub stars: CoReason Ecosystem — Federated MCP Gateway0; HAPI MCP Server0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: CoReason Ecosystem — Federated MCP GatewayNot yet assessed; HAPI MCP ServerNot yet assessed
Community rating: CoReason Ecosystem — Federated MCP GatewayNo reviews yet; HAPI MCP ServerNo reviews yet
Last commit: CoReason Ecosystem — Federated MCP GatewayUnknown; HAPI MCP ServerUnknown
Licence: CoReason Ecosystem — Federated MCP GatewayNone declared; HAPI MCP ServerNone declared
Official: CoReason Ecosystem — Federated MCP GatewayNo; HAPI MCP ServerNo
Source: CoReason Ecosystem — Federated MCP Gateway Repository; HAPI MCP Server Repository

Highlighted cells win that row on an objective measure. Rows without a clear winner — category, licence, source — are left unmarked. A higher trust score means better auditability and maintenance, not safer code.