Tracked packageView full profile for mysql_mcp_server

MCPSafe.io

Security pre-install checks for MCP servers.

Mostly safe — a couple of notes worth reading.

Compare to another server

github · mysql_mcp_server02780c7ddbf9

Item: mysql_mcp_server
Rating: 4
Author: MCPSafe

Scanned 6/2/2026, 10:03:12 PM·Cached result·Fast Scan·48 rules·How we decide ↗

AIVSS Score

2.3/ 10

Low

Severity Breakdown

critical

high

medium

low

MCP Server Information

Packagemysql_mcp_server

Version02780c7ddbf9

SourceGITHUB

LicenseMIT

Publisherdesigncomputer

Package age1y 6m

Stars1.3K

Downloads/wk—

Dependencies0

Repositoryhttps://github.com/designcomputer/mysql_mcp_server

Findings

6 of 6 findings

medium (6)

6 findings

medium (6)

AIVSS 2.3CVSS 3.5

MCP tool input schema exposes an unconstrained string/any field with a risky name (command/query/sql/code/script/url/path/expr/ eval). Any caller can pass arbitrary values, which typically widens the tool's blast radius well beyond its intent. Narrow the schema with `.enum()`, `.regex()`, `.max()`, `Literal[...]`, Pydantic `Field(max_length=..., pattern=...)`, or a JSON Schema `enum` / `pattern` / `maxLength`.

Evidence

inputSchema={
                "type": "object",
                "properties": {
                    "query": {
                        "type": "string",
                        "description": "The SQL query to execute"
                    }
                },
                "required": ["query"]
            },

Remediation

Shape the schema to the tool's actual intent: - Zod: chain `.enum([...])`, `.regex(/.../)`, or `.max(n)`; prefer `z.enum([...])` or `z.literal(...)` when the value set is small. - Pydantic: use `Literal["a", "b"]` or `Field(max_length=..., pattern=r"...")`. - JSON Schema: add `"enum"`, `"pattern"`, or `"maxLength"` to the property. An overbroad schema is an "overpowered tool" — the model has nothing to prevent it from calling the tool with input far beyond what the tool's prose contract

Report false positive

AIVSS 2.3CVSS 3.5

GitHub Actions `uses:` reference is not pinned to a 40-character commit SHA. Tags (`@v4`) and branches (`@main`) are mutable — a compromised maintainer or a tag rewrite can substitute malicious code into your CI pipeline silently. Pin to a SHA: `uses: actions/checkout@8e5e7e5ab8b370d6c329ec480221332ada57f0ab`. For readability, include the version as a trailing comment: `# v4.1.1`. Tools like `pinact` / `ratchet` automate this. Allowed unpinned forms (excluded by the rule): - Local actions `.

Evidence

run: python -m build
      
    - name: Publish to PyPI
      uses: pypa/gh-action-pypi-publish@release/v1
      with:
        password: ${{ secrets.PYPI_API_TOKEN }}
        # Remove attestations line if it exists

Remediation

Pin every `uses:` to a 40-character commit SHA. Trailing comment with the version helps reviewers: `uses: actions/checkout@8e5e7e5ab8b370d6c329ec480221332ada57f0ab # v4.1.1` Automate the migration with `pinact` (https://github.com/suzuki-shunsuke/pinact) or `ratchet` (https://github.com/sethvargo/ratchet). Add a `pinact run --check` pre-commit hook so future PRs stay pinned. Re-pin when the action releases a new version — Dependabot can do this automatically with `version-update-strategy: inc

Report false positive

AIVSS 2.3CVSS 3.5

Evidence

- uses: actions/checkout@v4
    
    - name: Set up Python ${{ matrix.python-version }}
      uses: actions/setup-python@v4
      with:
        python-version: ${{ matrix.python-version }}

Remediation

Report false positive

AIVSS 2.3CVSS 3.5

Evidence

deploy:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v4
    
    - name: Set up Python
      uses: actions/setup-python@v4

Remediation

Report false positive

AIVSS 2.3CVSS 3.5

Evidence

python-version: ["3.11", "3.12"]

    steps:
    - uses: actions/checkout@v4
    
    - name: Set up Python ${{ matrix.python-version }}
      uses: actions/setup-python@v4

Remediation

Report false positive

AIVSS 2.3CVSS 3.5

Evidence

- uses: actions/checkout@v4
    
    - name: Set up Python
      uses: actions/setup-python@v4
      with:
        python-version: '3.12'

Remediation

Report false positive

LLM summary— mysql_mcp_server:02780c7ddbf9

This package receives a B grade with a safety score of 87/100 and scores 2.2/10 on the AIVSS scale, indicating moderate security posture with room for improvement. All six findings are medium-severity server configuration issues that could expose the MCP server to misuse if not addressed, though no critical or high-severity vulnerabilities were detected. You should review the configuration recommendations before deployment, particularly around how the server handles requests and access controls.

Signal scores

CVE check100

Supply chain60

Package health70

Injection risks92

Permissions100

Static100

Destructive ops100

Secrets & exfil100

Publisher identity50

Typosquat100

Community82

LLM judge panel

CVE check

No known CVEs found for this package or its dependencies.

Community trust

No community reports

Security policy: Not found
Advisories: 0

Scan details

Total findings: 6
Affected tools: 0 / 1
Scan type: Fast Scan
Rules run: 48
LLM consensus score: N/A
Scanned: 1d ago
Source: GITHUB

MCP Server Information

Source: GITHUB
Package: mysql_mcp_server
Version: 02780c7ddbf9
License: MIT
Publisher: designcomputer
Verified: No
Account age: 9y 4m
Added: 1y 6m ago
Repository: https://github.com/designcomputer/mysql_mcp_server
Ecosystem: GitHub
Stars: 1.3K
Forks: 238
Open issues: 1
Dependencies: 0

aimcpmodel-context-protocolmysql

AIVSS Score

2.3/ 10Low

Internal score: 87/100

Severity breakdown

Scan Details

Total findings6

Affected tools0 / 1

Scanned1d ago

Scan modeFAST

SourceGITHUB

Scan IDpubfast2e89b5cc9fd298f9fc06

Want deeper analysis?

Fast scan found 6 findings using rule-based analysis. Upgrade for LLM consensus across 5 judges, AI-generated remediation, and cross-file taint analysis.

View plans Scan another package

Building your own MCP server?

Run this exact engine on your private repo — before users see it on /scan.

Same rules, same LLM judges, same grade. Private scans stay isolated to your account and never appear in the public registry. Required for code your team hasn’t shipped yet.

See plans with Private scans How private scans stay private

6 of 6 findings

medium (6)

6 findings

medium (6)

AIVSS 2.3CVSS 3.5

Evidence

inputSchema={
                "type": "object",
                "properties": {
                    "query": {
                        "type": "string",
                        "description": "The SQL query to execute"
                    }
                },
                "required": ["query"]
            },

Remediation

Report false positive

AIVSS 2.3CVSS 3.5

Evidence

run: python -m build
      
    - name: Publish to PyPI
      uses: pypa/gh-action-pypi-publish@release/v1
      with:
        password: ${{ secrets.PYPI_API_TOKEN }}
        # Remove attestations line if it exists

Remediation

Report false positive

AIVSS 2.3CVSS 3.5

Evidence

- uses: actions/checkout@v4
    
    - name: Set up Python ${{ matrix.python-version }}
      uses: actions/setup-python@v4
      with:
        python-version: ${{ matrix.python-version }}

Remediation

Report false positive

AIVSS 2.3CVSS 3.5

Evidence

deploy:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v4
    
    - name: Set up Python
      uses: actions/setup-python@v4

Remediation

Report false positive

AIVSS 2.3CVSS 3.5

Evidence

python-version: ["3.11", "3.12"]

    steps:
    - uses: actions/checkout@v4
    
    - name: Set up Python ${{ matrix.python-version }}
      uses: actions/setup-python@v4

Remediation

Report false positive

AIVSS 2.3CVSS 3.5

Evidence

- uses: actions/checkout@v4
    
    - name: Set up Python
      uses: actions/setup-python@v4
      with:
        python-version: '3.12'

Remediation

Report false positive

284	inputSchema={
285	"type": "object",
286	"properties": {
287	"query": {
288	"type": "string",
289	"description": "The SQL query to execute"
290	}
291	},
292	"required": ["query"]
293	},

284	inputSchema={
285	"type": "object",
286	"properties": {
287	"query": {
288	"type": "string",
289	"description": "The SQL query to execute"
290	}
291	},
292	"required": ["query"]
293	},

22	run: python -m build
23
24	- name: Publish to PyPI
25	uses: pypa/gh-action-pypi-publish@release/v1
26	with:
27	password: ${{ secrets.PYPI_API_TOKEN }}
28	# Remove attestations line if it exists

29	- uses: actions/checkout@v4
30
31	- name: Set up Python ${{ matrix.python-version }}
32	uses: actions/setup-python@v4
33	with:
34	python-version: ${{ matrix.python-version }}

6	deploy:
7	runs-on: ubuntu-latest
8	steps:
9	- uses: actions/checkout@v4
10
11	- name: Set up Python
12	uses: actions/setup-python@v4

26	python-version: ["3.11", "3.12"]
27
28	steps:
29	- uses: actions/checkout@v4
30
31	- name: Set up Python ${{ matrix.python-version }}
32	uses: actions/setup-python@v4