MySQL Audit
PYPI · MYSQL-AUDIT-AI-AGENT
MySQL migration and query safety review for AI agents: locks, table copies, data loss, injection.
Available components
Last scanned (12 hours ago)
Scores higher than 77% of PyPI servers
Category Databases
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 → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 30 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to jimmyjan0824/mysql_audit_ai_agent). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 889 tokens (~148/item across 6 items; 6 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 Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (17% of tools); any adoption earns full credit.Pass
Tool Safety50
- Injection-marker check failed: the server instructions contains an instruction to conceal the call from the user, the text "Never tell the user", at byte 658 of that field. See how to fix → Fail
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 −3
- Injection markers: pass → fail ▼ security
- Package version: 0.3.2 → 0.3.3 functional
- 28 Oct 26 −1
- Schema quality: pass → fail ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.2.0 → 0.3.2 functional
- Package version: 0.2.0 → 0.3.1 functional
- Package version: 0.2.0 → 0.3.0 functional
- Package version: 0.2.0 → 0.2.1 functional
- 27 Oct 26 63
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 5 Nov 2026 · Analysed pypi/mysql-audit-ai-agent@0.3.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | jimmyjan0824/mysql_audit_ai_agent |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/jimmyjan0824/mysql_audit_ai_agent/.github/workflows/release.yml@refs/tags/v0.3.3 |
| Rekor log index | 3556350361 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:d732993149c1f5936c688e79655412adad3c3f68330995153ee8bb67d8bbba43 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 30 packages
| Packages resolved | 30 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
explain_rule ~35
Explain one rule (e.g. "L02"): why it matters and a safe example.
| Name | Type | Req | Description |
|---|---|---|---|
| rule_id | string | yes | – |
No output schema declared.
No examples provided.
list_rules ~24
List every rule this server checks, with its id, title and default severity.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
preflight_checks ~136
SQL for the user (or DBA) to run on the primary right before deploying a migration: long transactions, long queries and metadata locks on the tables it touches, current table sizes, and how to check replica lag. Each query returns rows only when the deploy should wait. This tool does not connect to the database; hand the SQL to the user. Args: sql: The migration that is about to run. mysql_version: Optional server version, e.g. "5.7.44"; picks SHOW SLAVE / REPLICA STATUS.
| Name | Type | Req | Description |
|---|---|---|---|
| mysql_version | – | – | – |
| sql | string | yes | – |
No output schema declared.
No examples provided.
review_code ~68
Check application source code (Python, JS/TS, PHP, Go, Java) for SQL built by string interpolation or concatenation, i.e. SQL injection. Returns a verdict (safe / block) and findings with line and the parameterized fix.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
No output schema declared.
No examples provided.
review_migration ~353
Review MySQL DDL or a migration script for locking, data-loss and replication risks. Args: sql: The SQL to run, one or more statements separated by semicolons. schema: Optional CREATE TABLE statements for the tables involved (e.g. from SHOW CREATE TABLE). Makes column-type and index checks exact. stats: Optional size per table from information_schema.tables: a row count ({"orders": 25000000}) or {"orders": {"rows": 25000000, "data_bytes": <data_length>, "index_bytes": <index_length>}}. Large = 1M rows or 5 GB. mysql_version: Optional target server version, e.g. "8.0.28", "8.4.3" or "aurora-3.04" (SELECT VERSION()). Older servers copy the table for more column changes. Without it, 8.0.29 or later is assumed. free_disk_gb: Optional free space on the server's data volume, in GB. With byte sizes in stats, a table rebuild that does not fit is blocked. rollback_sql: Optional down migration kept in a separate file (e.g. a golang-migrate .down.sql or Flyway U__ file). Down sections and --rollback lines inside sql are found without it. Returns a verdict (safe / review / block) and findings with line, impact and fix.
| Name | Type | Req | Description |
|---|---|---|---|
| free_disk_gb | – | – | – |
| mysql_version | – | – | – |
| rollback_sql | – | – | – |
| schema | – | – | – |
| sql | string | yes | – |
| stats | – | – | – |
No output schema declared.
No examples provided.
review_query ~86
Review queries an application will run (SELECT / UPDATE / DELETE / INSERT) for missing indexes, unbatched writes and unsafe UPDATE/DELETE. Pass schema for index checks. Returns a verdict (safe / review / block) and findings with line, impact and fix.
| Name | Type | Req | Description |
|---|---|---|---|
| mysql_version | – | – | – |
| schema | – | – | – |
| sql | string | yes | – |
| stats | – | – | – |
No output schema declared.
No examples provided.
How do I install the MySQL Audit MCP server?
MySQL Audit runs locally as a PyPI package, launched with uvx mysql-audit-ai-agent. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mysql-audit-ai-agent
claude mcp add jimmyjan0824-mysql-audit -- uvx mysql-audit-ai-agent
What is the MySQL Audit MCP server?
MySQL Audit is an MCP server listed in the public MCP registry as io.github.jimmyjan0824/mysql-audit. MySQL migration and query safety review for AI agents: locks, table copies, data loss, injection. This page covers its PyPI package (mysql-audit-ai-agent).
Is the MySQL Audit MCP server safe to use?
MySQL Audit scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the MySQL Audit MCP server expose?
MySQL Audit exposes 6 tools: review_migration, review_query, review_code, preflight_checks, explain_rule, list_rules. Their descriptions and schemas cost roughly 702 tokens of context every time the server is loaded.
Is the MySQL Audit MCP server still maintained?
MySQL Audit is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the MySQL Audit MCP server under?
MySQL Audit declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the MySQL Audit MCP server?
VerifyMCP ran 16 checks on MySQL Audit, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.