io.github.marcelo-ochoa/mysql
NPM · @MARCELO-OCHOA/SERVER-MYSQL · SCANNED AUG 3
An MCP server for MySQL databases.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (104 of 108), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (104 of 108), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 144 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability54
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (poor).Fail
- Context-footprint check failed: tool/resource definitions use about 1257 tokens (~251/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @marcelo-ochoa/server-mysql
claude mcp add marcelo-ochoa-mysql -- npx -y @marcelo-ochoa/server-mysql
codex mcp add marcelo-ochoa-mysql -- npx -y @marcelo-ochoa/server-mysql
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"marcelo-ochoa-mysql": {
"type": "local",
"command": [
"npx",
"-y",
"@marcelo-ochoa/server-mysql"
],
"enabled": true
}
}
} openclaw mcp add marcelo-ochoa-mysql --command npx --arg -y --arg @marcelo-ochoa/server-mysql
mcp_servers:
marcelo-ochoa-mysql:
command: "npx"
args: ["-y", "@marcelo-ochoa/server-mysql"] {
"mcpServers": {
"marcelo-ochoa-mysql": {
"command": "npx",
"args": [
"-y",
"@marcelo-ochoa/server-mysql"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +32
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Schema quality: unverified → poor ▲ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Licence: MIT functional
- 31 Jul 26 −21
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +26
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- 28 Jul 26 −26
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 27 Jul 26 50
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed npm/@marcelo-ochoa/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 104 packages
104 packages in the resolved dependency tree · 103 deprecated · 32 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
mysql-awr ~126
Generate a MySQL performance report similar to Oracle AWR. Includes database statistics, InnoDB metrics, top queries (requires performance_schema), table/index statistics, connection info, and optimization recommendations.
| Name | Type | Req | Description |
|---|---|---|---|
| mcp_client | string | — | Specify the name and version of the MCP client implementation being used (e.g. Copilot, Claude, Cline...) |
| model | string | — | The name (and version) of the language model being used by the MCP client to process requests (e.g. gpt-4.1, claude-sonnet-4, llama4...) |
No output schema declared.
No examples provided.
mysql-connect ~305
Provides an interface to connect to a specified MySQL database. If a database connection is already active, the tool will close the existing connection before establishing a new one. This tool accepts three required parameters: connectionString: The MySQL connection string without embedded credentials (e.g., mysql://host:port/dbname or host:port/dbname) user: The MySQL username password: The MySQL password The credentials are stored in environment variables MYSQL_USER and MYSQL_PASSWORD for the session. The `model` argument should only be used to specify the name and version of the LLM (Large Language Model) you are using, with no additional information. The `mcp_client` argument should specify only the name of the MCP (Model Context Protocol) client you are using, with no additional information.
| Name | Type | Req | Description |
|---|---|---|---|
| connectionString | string | yes | The MySQL connection string (e.g. mysql://host:port/dbname or host:port/dbname) |
| mcp_client | string | — | Specify the name and version of the MCP client implementation being used (e.g. Copilot, Claude, Cline...) |
| model | string | — | The name (and version) of the language model being used by the MCP client to process requests (e.g. gpt-4.1, claude-sonnet-4, llama4...) |
| password | string | yes | The MySQL password |
| user | string | yes | The MySQL user (e.g. root) |
No output schema declared.
No examples provided.
mysql-explain ~242
Generate and display the execution plan for a given SQL query using MySQL's EXPLAIN command. This tool helps you understand how MySQL will execute your query, including information about table scans, joins, indexes used, and estimated costs. Args: sql: The SQL query to explain. The `model` argument should specify only the name and version of the LLM (Large Language Model) you are using, with no additional information. The `mcp_client` argument should specify only the name of the MCP (Model Context Protocol) client you are using, with no additional information. Returns: Detailed execution plan showing how MySQL will process the query, including costs, row estimates, and access methods.
| Name | Type | Req | Description |
|---|---|---|---|
| mcp_client | string | yes | Specify the name and version of the MCP client implementation being used (e.g. Copilot, Claude, Cline...) |
| model | string | yes | The name (and version) of the language model being used by the MCP client to process requests (e.g. gpt-4.1, claude-sonnet-4, llama4...) |
| sql | string | yes | The SQL query to explain |
No output schema declared.
No examples provided.
mysql-query ~346
This tool executes SQL queries in a READ ONLY session connected to a MySQL database. If no active connection exists, it uses MCP server registration argument and environment variables MYSQL_USER and MYSQL_PASSWORD. You should: Execute the provided SQL query. Return the results in Toon format. Args: sql: The SQL query to execute. The `model` argument should specify only the name and version of the LLM (Large Language Model) you are using, with no additional information. The `mcp_client` argument should specify only the name of the MCP (Model Context Protocol) client you are using, with no additional information. Returns: Json-formatted query results. For every SQL query you generate, please include a comment at the beginning of the SELECT statement (or other main SQL command) that identifies the LLM model name and version you are using. Format the comment as: /* LLM in use is [model_name_and_version] */ and place it immediately after the main SQL keyword. For example: SELECT /* LLM in use is claude-sonnet-4 */ column1, column2 FROM table_name; Please apply this format consistently to all SQL queries you generate, using your actual model name and version in the comment
| Name | Type | Req | Description |
|---|---|---|---|
| mcp_client | string | yes | Specify the name and version of the MCP client implementation being used (e.g. Copilot, Claude, Cline...) |
| model | string | yes | The name (and version) of the language model being used by the MCP client to process requests (e.g. gpt-4.1, claude-sonnet-4, llama4...) |
| sql | string | yes | The SQL query to execute |
No output schema declared.
No examples provided.
mysql-stats ~238
Get comprehensive statistics for a specific MySQL table. This tool retrieves detailed information including row counts, table size, index information, column statistics, and other metadata that can help optimize queries and understand data distribution. Args: name: The name of the table to get statistics for. The `model` argument should specify only the name and version of the LLM (Large Language Model) you are using, with no additional information. The `mcp_client` argument should specify only the name of the MCP (Model Context Protocol) client you are using, with no additional information. Returns: Json-formatted table statistics including row counts, size information, indexes, and column details.
| Name | Type | Req | Description |
|---|---|---|---|
| mcp_client | string | — | Specify the name and version of the MCP client implementation being used (e.g. Copilot, Claude, Cline...) |
| model | string | — | The name (and version) of the language model being used by the MCP client to process requests (e.g. gpt-4.1, claude-sonnet-4, llama4...) |
| name | string | yes | The name of the table to get statistics for |
No output schema declared.
No examples provided.