mcp-address-history vs aTars MCP

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

Metricmcp-address-historyMCP Server aTars MCPMCP Server

Type: mcp-address-historyMCP Server; aTars MCPMCP Server
Category: mcp-address-historyCrypto; aTars MCPCrypto
GitHub stars: mcp-address-history0; aTars MCP0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: mcp-address-historyNot yet assessed; aTars MCPNot yet assessed
Community rating: mcp-address-historyNo reviews yet; aTars MCPNo reviews yet
Last commit: mcp-address-historyUnknown; aTars MCPUnknown
Licence: mcp-address-historyNone declared; aTars MCPNone declared
Official: mcp-address-historyNo; aTars MCPNo
Source: mcp-address-history Repository; aTars MCPNot available

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.