Gachi Data API — Japan Station & Accessibility Data vs iota-mcp

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

MetricGachi Data API — Japan Station & Accessibility DataMCP Server iota-mcpMCP Server

Type: Gachi Data API — Japan Station & Accessibility DataMCP Server; iota-mcpMCP Server
Category: Gachi Data API — Japan Station & Accessibility DataOther; iota-mcpOther
GitHub stars: Gachi Data API — Japan Station & Accessibility Data0; iota-mcp0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: Gachi Data API — Japan Station & Accessibility DataNot yet assessed; iota-mcp74/100 · Good
Community rating: Gachi Data API — Japan Station & Accessibility DataNo reviews yet; iota-mcpNo reviews yet
Last commit: Gachi Data API — Japan Station & Accessibility DataUnknown; iota-mcp76 days ago
Licence: Gachi Data API — Japan Station & Accessibility DataNone declared; iota-mcpNOASSERTION
Official: Gachi Data API — Japan Station & Accessibility DataNo; iota-mcpNo
Source: Gachi Data API — Japan Station & Accessibility Data Repository; iota-mcp 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.