web3-signals vs Inferventis MCP Server

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

Metricweb3-signalsMCP Server Inferventis MCP ServerMCP Server

Type: web3-signalsMCP Server; Inferventis MCP ServerMCP Server
Category: web3-signalsCrypto; Inferventis MCP ServerCrypto
GitHub stars: web3-signals0; Inferventis MCP Server0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: web3-signalsNot yet assessed; Inferventis MCP ServerNot yet assessed
Community rating: web3-signalsNo reviews yet; Inferventis MCP ServerNo reviews yet
Last commit: web3-signalsUnknown; Inferventis MCP ServerUnknown
Licence: web3-signalsNone declared; Inferventis MCP ServerNone declared
Official: web3-signalsNo; Inferventis MCP ServerNo
Source: web3-signals Repository; Inferventis 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.