io.github.musaddiq-dev/mysql-mcp-server

The evidence

Every deduction below names the artefact that produced it. Nothing on this page was executed: the source was read, never run, and no running server was contacted.

Code Safety

• src/mysql_mcp_server/server.py:149mcp-python-sql-string-built (medium/medium)

  A SQL statement is assembled by string building rather than passed as a parameterised query. Every driver here accepts parameters as a second argument; building the string is never necessary.

      
      try:
          cursor.execute(f"DESCRIBE `{table_name}`")
          columns = cursor.fetchall()
          logger.debug(f"Described table '{table_name}', found {len(columns)} columns")

• src/mysql_mcp_server/server.py:424mcp-python-sql-string-built (medium/medium)

  A SQL statement is assembled by string building rather than passed as a parameterised query. Every driver here accepts parameters as a second argument; building the string is never necessary.

      try:
          # Use backticks to safely escape the table name
          cursor.execute(f"SHOW CREATE TABLE `{table_name}`")
          result = cursor.fetchone()
          

• src/mysql_mcp_server/server.py:523mcp-python-sql-string-built (medium/medium)

  A SQL statement is assembled by string building rather than passed as a parameterised query. Every driver here accepts parameters as a second argument; building the string is never necessary.

          for table_name in table_names:
              table_name = validate_identifier(table_name, "table name")
              cursor.execute(f"SELECT COUNT(*) FROM `{table_name}`")
              count_result = cursor.fetchone()
              row_count = count_result[0] if count_result else 0

Auth Posture

• authentication_model

  stdio transport: the client launches the server as a subprocess, so the OS process boundary is the auth boundary — `03` §4 does not penalise absent auth here

• transport_security

  declared transport: stdio — launched as a subprocess by the client, so the security boundary is the client process, not a network port (`03` §4)

• secret_handling

  detect-secrets matched 2 credential-shaped string(s), every one from a keyword or entropy heuristic (Secret Keyword). Those flag placeholders, variable names and content hashes as readily as credentials, so they do not establish the committed credential `03` §4's 0 asserts, and this sub-check is not scored; Secret Keyword at PKG-INFO:122; Secret Keyword at README.md:100

• authorization_granularity

  8 tool registrations and no conditional access logic found — `03` §4 calls this case 'needs human review' and assigns it no score band, so it is not scored here

Maintenance

• recency

  last commit 146 day(s) before 2026-10-16

• issue_responsiveness

  this repository has no issues `03` §5's window covers. An unanswered issue scores 0 under §5, but a repository with no issues filed has not failed to answer one.

• release_cadence

  median release gap 0 days (by releases), last release 146 day(s) ago

• bus_factor

  sole maintainer, and no commit in over 90 days

• repository_signals

  `03` §5 scores this by quartile WITHIN the server's category, which needs a distribution across every scanned server and so cannot be computed while scanning one. It is a post-pass over the crawl and that pass does not exist yet.

Transparency

• license

  LICENSE present with no SPDX-License-Identifier tag; identified as 'MIT' from its text

• readme_quality

  README.md: installation instructions (+25), configuration documented (+25), exposed tools or resources enumerated (+30), states what the server does in the first 200 words (+20)

• declared_scopes

  specific scope or access documentation is present, but `03` §7's 100 and 60 bands both compare it against scopes INFERRED from static analysis, which is not built yet. Scoring 100 on an empty inference would be a vacuous truth — 'all ∅ inferred scopes are documented'.

• changelog

  no CHANGELOG in the fetched source. `03` §7's partial credit for tagged releases carrying release notes is not applied here — that needs the forge API, which this check does not call

• security_contact

  SECURITY.md present