crabeye-mcp-bridge vs iota-mcp

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

Metriccrabeye-mcp-bridgeMCP Server iota-mcpMCP Server

Type: crabeye-mcp-bridgeMCP Server; iota-mcpMCP Server
Category: crabeye-mcp-bridgeOther; iota-mcpOther
GitHub stars: crabeye-mcp-bridge0; iota-mcp0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: crabeye-mcp-bridgeNot yet assessed; iota-mcp74/100 · Good
Community rating: crabeye-mcp-bridgeNo reviews yet; iota-mcpNo reviews yet
Last commit: crabeye-mcp-bridgeUnknown; iota-mcp76 days ago
Licence: crabeye-mcp-bridgeNone declared; iota-mcpNOASSERTION
Official: crabeye-mcp-bridgeNo; iota-mcpNo
Source: crabeye-mcp-bridge 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.