Home/mysql_mcp_server/Trust report

Trust and health report

mysql_mcp_server - trust report

Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.

GraphCanon updated today · GitHub synced 4w

Maintenance

Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.

Steady60% signal

last push 36d ago · last release 2mo · 5 releases (90d)

Provenance

Repository identity and fork provenance (github_public_v1).

  • GitHub repo id: 898128804
  • Not a fork
  • Personal account
  • Computed 4w

Security intelligence

Source-by-source security scan results from public intelligence providers. Missing, partial, or failed queries are shown explicitly and are not treated as clean.

OSV dependency advisories

Published findings
Last query
today
Scanner
osv@v1
Stored findings
24
View source evidence

deps.dev advisories

Not queried
Scanner
deps.dev@v1
View source evidence

OpenSSF Scorecard

Not queried
Scanner
openssf-scorecard@v1

Weekly public scans omit some checks at scale.

View source evidence

Dependency advisories (deduplicated)

GHSA-3qhf-m339-9g5v
mcp@1.2.0 · osv@v1
requirements.txt
GHSA-9h52-p55h-vw2f
mcp@1.2.0 · osv@v1
requirements.txt
GHSA-j975-95f5-7wqh
mcp@1.2.0 · osv@v1
requirements.txt
GHSA-jpw9-pfvf-9f58
mcp@1.2.0 · osv@v1
requirements.txt
GHSA-vj7q-gjh5-988w
mcp@1.2.0 · osv@v1
requirements.txt
PYSEC-2026-1616
mcp@1.2.0 · osv@v1
requirements.txt
PYSEC-2026-1617
mcp@1.2.0 · osv@v1
requirements.txt
PYSEC-2026-1618
mcp@1.2.0 · osv@v1
requirements.txt
PYSEC-2026-3482
mcp@1.2.0 · osv@v1
requirements.txt
PYSEC-2026-3483
mcp@1.2.0 · osv@v1
requirements.txt
GHSA-2c2j-9gv5-cj73
starlette@0.35.0 · osv@v1
requirements.txt
GHSA-82w8-qh3p-5jfq
starlette@0.35.0 · osv@v1
requirements.txt
GHSA-86qp-5c8j-p5mr
starlette@0.35.0 · osv@v1
requirements.txt
GHSA-f96h-pmfr-66vw
starlette@0.35.0 · osv@v1
requirements.txt
GHSA-jp82-jpqv-5vv3
starlette@0.35.0 · osv@v1
requirements.txt
GHSA-wqp7-x3pw-xc5r
starlette@0.35.0 · osv@v1
requirements.txt
GHSA-x746-7m8f-x49c
starlette@0.35.0 · osv@v1
requirements.txt
PYSEC-2026-161
starlette@0.35.0 · osv@v1
requirements.txt
PYSEC-2026-1941
starlette@0.35.0 · osv@v1
requirements.txt
PYSEC-2026-1943
starlette@0.35.0 · osv@v1
requirements.txt
PYSEC-2026-2280
starlette@0.35.0 · osv@v1
requirements.txt
PYSEC-2026-2281
starlette@0.35.0 · osv@v1
requirements.txt
PYSEC-2026-248
starlette@0.35.0 · osv@v1
requirements.txt
PYSEC-2026-249
starlette@0.35.0 · osv@v1
requirements.txt

Method and caveats: these are sourced, dated heuristics from public GitHub data and external security intelligence providers. A status like "no published findings from this source" is not a guarantee of safety. Read the full trust methodology · JSON report at /api/graphcanon/tools/designcomputer-mysql-mcp-server/trust.

Common questions

Is mysql_mcp_server maintained?
GraphCanon rates mysql_mcp_server "Steady" (60% maintenance signal from public GitHub metadata, computed 4w). Last push was 36 days ago. 5 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained.
Is mysql_mcp_server safe to use?
Last scanned today (deps profile). Status: 24 low - 24 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report. GraphCanon does not certify mysql_mcp_server as safe - review maintenance, provenance, and scan findings on this page before adopting.
Is mysql_mcp_server a fork?
No. mysql_mcp_server is not flagged as a fork in GitHub metadata at the time of the last refresh.
Does mysql_mcp_server have known security vulnerabilities?
Last scanned today (deps profile). Status: 24 low - 24 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report.
How often is the mysql_mcp_server trust report updated?
Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed 4w (methodology github_public_v1).
What does GraphCanon never claim about mysql_mcp_server?
We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for mysql_mcp_server. Signals are sourced heuristics with explicit limits - see trust methodology.
How does GraphCanon assess trust for mysql_mcp_server?
Signals are sourced from public GitHub metadata and optional dependency/MCP manifest scans, each tagged with methodology version and computed date. GraphCanon does not publish a composite safety grade. Read trust methodology for full scope and limits.

Was this helpful?

Anonymous feedback helps us improve pages and translations.