Vaultfire Trust Protocol vs Inferventis MCP Server

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

MetricVaultfire Trust ProtocolMCP Server Inferventis MCP ServerMCP Server

Type: Vaultfire Trust ProtocolMCP Server; Inferventis MCP ServerMCP Server
Category: Vaultfire Trust ProtocolCrypto; Inferventis MCP ServerCrypto
GitHub stars: Vaultfire Trust Protocol0; Inferventis MCP Server0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: Vaultfire Trust ProtocolNot yet assessed; Inferventis MCP ServerNot yet assessed
Community rating: Vaultfire Trust ProtocolNo reviews yet; Inferventis MCP ServerNo reviews yet
Last commit: Vaultfire Trust ProtocolUnknown; Inferventis MCP ServerUnknown
Licence: Vaultfire Trust ProtocolNone declared; Inferventis MCP ServerNone declared
Official: Vaultfire Trust ProtocolNo; Inferventis MCP ServerNo
Source: Vaultfire Trust Protocol 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.