Mmcp.market

Head to head

DBHub vs Dataset to Postgres, Supabase & MySQL (Database Push)

Same numbers we show everywhere else, lined up. Ratings come from users, the grade comes from our scanner, adoption comes from public registries.

DBHubio.github.bytebase/dbhub
A
No reviews yet

Token-efficient database MCP server for PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, SQLite

Full listing
Dataset to Postgres, Supabase & MySQL (Database Push)io.github.Nero-Engine/dataset-to-database
C
No reviews yet

Push rows from a dataset, file or Google Sheet into a Postgres, Supabase, Neon or MySQL table.

Full listing

The short version

Neither has been reviewed yet, so the comparison rests on the scan and the public usage numbers. The safety scan favours DBHub (85/100 against 67). Dataset to Postgres, Supabase & MySQL (Database Push) is hosted and callable through the gateway; DBHub runs on your own machine. DBHub has noticeably more public adoption.

 DBHubDataset to Postgres, Supabase & MySQL (Database Push)
User ratingNo reviews yetNo reviews yet
Safety gradeA85/100C67/100
AdoptionWidely usedNew
GitHub stars3.5k
Downloads / week21k
Runs whereYour machine (local)Hosted (remote)
Gateway-readyNoYes
Tools
Write actions
Price per callFreeFree
LicenceMIT
Last release2026-09-19
CategoryDatabasesDatabases

Other comparisons