DBHub

It requires highly sensitive credentials including DSN, database usernames/passwords, and SSH keys/passphrases, which can enable direct database access or access via SSH tunneling; if configuration, logs, or runtime environments are not well protected, unauthorized database access could result.

The materials do not declare any fixed third-party remote endpoint, and the system field lists host as none; however, by design it will connect to user-configured database hosts and possibly SSH hosts, which is normal network access consistent with its stated purpose, with no evidence of exfiltration to unrelated unknown services.

The system flags it as executing code; as an MCP server, it typically needs to start a local process and handle database connection/query requests. This is inherent to this class of tool, and the available materials do not show requests for additional high-risk system privileges beyond the database proxy use case.

Its intended purpose is to access data in PostgreSQL, MySQL, SQL Server, SQLite, and MariaDB, so it can reach business data stored in those databases; SSH and SQLite use cases may also indirectly involve local files or remote host resources. The materials do not indicate obvious overbroad authorization, but effective access depends on the privileges granted to the supplied database account and tunnel.

The source is an official registry entry with a public open-source repository and updates within the last year, providing auditability and some maintenance activity; while the very low star count and undeclared license reduce maturity confidence, the available facts do not show clear supply-chain red flags.