AgentData - Executable Liquidity / Exit-Cost vs Stripe_connect

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

MetricAgentData - Executable Liquidity / Exit-CostMCP Server Stripe_connectMCP Server

Type: AgentData - Executable Liquidity / Exit-CostMCP Server; Stripe_connectMCP Server
Category: AgentData - Executable Liquidity / Exit-CostPayments; Stripe_connectPayments
GitHub stars: AgentData - Executable Liquidity / Exit-Cost0; Stripe_connect0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: AgentData - Executable Liquidity / Exit-CostNot yet assessed; Stripe_connectNot yet assessed
Community rating: AgentData - Executable Liquidity / Exit-CostNo reviews yet; Stripe_connectNo reviews yet
Last commit: AgentData - Executable Liquidity / Exit-CostUnknown; Stripe_connectUnknown
Licence: AgentData - Executable Liquidity / Exit-CostNone declared; Stripe_connectNone declared
Official: AgentData - Executable Liquidity / Exit-CostNo; Stripe_connectNo
Source: AgentData - Executable Liquidity / Exit-Cost Repository; Stripe_connect 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.