mcp-data-pipeline-connector vs enforcement-database

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

Metricmcp-data-pipeline-connectorMCP Server enforcement-databaseMCP Server

Type: mcp-data-pipeline-connectorMCP Server; enforcement-databaseMCP Server
Category: mcp-data-pipeline-connectorDatabases; enforcement-databaseDatabases
GitHub stars: mcp-data-pipeline-connector0; enforcement-database0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: mcp-data-pipeline-connectorNot yet assessed; enforcement-databaseNot yet assessed
Community rating: mcp-data-pipeline-connectorNo reviews yet; enforcement-databaseNo reviews yet
Last commit: mcp-data-pipeline-connectorUnknown; enforcement-databaseUnknown
Licence: mcp-data-pipeline-connectorNone declared; enforcement-databaseNone declared
Official: mcp-data-pipeline-connectorNo; enforcement-databaseNo
Source: mcp-data-pipeline-connector Repository; enforcement-database 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.