Mysql MCP Server by designcomputer

Findings (10)

• highHigh. Something risky that needs a close look before you install.
  dependencies issue

  Details are available to the maintainer after claiming this listing.
• highHigh. Something risky that needs a close look before you install.
  dependencies issue

  Details are available to the maintainer after claiming this listing.
• highHigh. Something risky that needs a close look before you install.
  dependencies issue

  Details are available to the maintainer after claiming this listing.
• mediumMedium. Worth checking, often a vulnerable dependency or a setup problem.
  black@26.5.1: 1 known vulnerability

  GHSA-cg8m-r9f2-5wm2

  requirements-dev.txt
• mediumMedium. Worth checking, often a vulnerable dependency or a setup problem.
  python-multipart@0.0.9: 8 known vulnerabilities

  PYSEC-2026-1851, PYSEC-2026-1852, PYSEC-2026-3036, PYSEC-2026-3037, PYSEC-2026-3038 +3 more

  requirements.txt
• mediumMedium. Worth checking, often a vulnerable dependency or a setup problem.
  cryptography@48.0.0: 4 known vulnerabilities

  PYSEC-2026-3552, PYSEC-2026-3553, PYSEC-2026-3554, GHSA-537c-gmf6-5ccf

  uv.lock
• mediumMedium. Worth checking, often a vulnerable dependency or a setup problem.
  mcp@1.27.2: 5 known vulnerabilities

  PYSEC-2026-3483, GHSA-5h93-6whr-6q8j, GHSA-84m7-p3x7-pcfv, GHSA-rwrf-2pqf-9j8j, GHSA-w4fh-qvv9-3v23

  uv.lock
• mediumMedium. Worth checking, often a vulnerable dependency or a setup problem.
  starlette@1.2.1: 2 known vulnerabilities

  PYSEC-2026-248, PYSEC-2026-249

  uv.lock
• lowLow. Minor, or common in normal tools. Shown for information.
  pydantic-settings@2.14.1: 1 known vulnerability

  GHSA-4xgf-cpjx-pc3j

  uv.lock
• lowLow. Minor, or common in normal tools. Shown for information.
  No manifest declaring network access and environment variables (agent.json)

Network activity

Tools exposed (3)

• execute_sql

  Execute a SQL statement against the MySQL server. Use for SELECT, DML (INSERT/UPDATE/DELETE), SHOW, DESCRIBE, and ad-hoc queries. Supports cross-database queries using database.table notation. Single statements only — use fully qualified names instead of USE statements.

• get_schema_info

  Get column metadata for a table or all tables in the configured database: column names, data types, nullability, default values, and comments. Call this before querying an unfamiliar table. Omit table_name to see all tables at once. Accepts bare table names (uses MYSQL_DATABASE) or database.table fo

• get_table_sample

  Fetch a small sample of rows from a table to understand its data format and content. Use alongside get_schema_info before writing complex queries. Accepts bare table names (uses MYSQL_DATABASE) or database.table for cross-database lookups.