Simple MCP MySQL Server

The materials state that no secrets or environment variables are required, and no third-party API token is requested. If a real MySQL connection later requires database credentials, those would still be sensitive, but the current materials do not show separate collection or exfiltration risk.

Its stated purpose is to interact with a MySQL database and execute queries, which means queries and results are sent to and received from the connected database instance. No external SaaS or unrelated endpoint is declared, and there is no clear red flag of third-party exfiltration, but the database connection itself is still a standard form of network egress.

The system flags this tool as executes-code, meaning it runs locally as an MCP service process. Its described functionality is focused on database access, and there is no evidence of system privileges clearly beyond that scope, but launching a local process is still a standard capability that warrants caution.

The description explicitly says it can list tables, view schemas, and execute read-only SQL, which means it can access database structure and query results. Although it is presented as read-only and there is no stated local file access, database contents themselves may be sensitive, so it should be limited to a least-privilege data account.

The project has an auditable open-source repository, which is a meaningful risk-reducing factor. However, it comes from a third-party registry, has no declared license, shows 0 stars, and has unknown maintenance status, so the supply-chain signals are relatively weak and the code and dependencies should be reviewed before use.