io.github.Fashad-Ahmed/universal-db-mcp
PYPI · UNIVERSAL-DB-MCP
Security-first MCP server for PostgreSQL, SQLite, MySQL, DuckDB with SQL injection prevention.
Available components
Last scanned (19 hours ago)
Scores higher than 76% 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 setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 22 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Build provenance not yet verified. View diagnostics → Unverified
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 145 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 344 tokens (~43/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "query" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 8 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
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.
- 4 Nov 26 −1
- Provenance: fail → unverified ▼ security
- Security disclosure: pass → unverified ▼ functional
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −14
- Provenance: unverified → fail ▼ security
- Malware scan: pass → unverified ▼ security
- Security disclosure: unverified → pass ▲ functional
- 30 Oct 26 −1
- Provenance: fail → unverified ▼ security
- Stability: 0.97 → pass security
- Security disclosure: pass → unverified ▼ functional
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.97 functional
- 23 Oct 26 0
- Stability: 0.97 → pass security
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 4 Nov 2026 · Analysed pypi/universal-db-mcp@1.1.2
Provenance Inconclusive
We could not complete the check, so nothing is claimed either way. This is a gap on our side, not a finding about the package.
| Result | Inconclusive |
|---|---|
| Ecosystem | pypi |
| Reason | Check deferred |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 22 packages
| Packages resolved | 22 |
|---|---|
| Stale | 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 Explain ~50
Get query execution plan without running the query.
| Name | Type | Req | Description |
|---|---|---|---|
| database | – | – | Database key (format: "type:name") |
| params | – | – | Optional parameters for the query |
| sql | string | yes | SQL query to analyze |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
health Health ~30
Check database connection health and get server version info.
| Name | Type | Req | Description |
|---|---|---|---|
| database | – | – | Database key (format: "type:name") |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_databases List Databases ~18
List all configured databases and their connection status.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
query Query ~95
Execute a SQL query against the database. Supports parameterized queries for injection safety. In read-only mode, destructive operations (INSERT, UPDATE, DELETE, DROP, etc.) are blocked.
| Name | Type | Req | Description |
|---|---|---|---|
| database | – | – | Database key (format: "type:name"). Required when multiple databases are configured. |
| params | – | – | Optional list of parameters for parameterized queries (use instead of string formatting) |
| sql | string | yes | SQL query to execute |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
query_history Query History ~36
Get recent query execution history (most recent first).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of history entries to return (default 10) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
schema Schema ~47
Get database schema information: tables, columns, types, and constraints.
| Name | Type | Req | Description |
|---|---|---|---|
| database | – | – | Database key (format: "type:name") |
| tables | – | – | Optional list of specific table names to inspect |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
schema_diff Schema Diff ~34
Compare the current schema against the last snapshot taken with snapshot_schema.
| Name | Type | Req | Description |
|---|---|---|---|
| database | – | – | Database key (format: "type:name") |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
snapshot_schema Snapshot Schema ~34
Take a snapshot of the current database schema for later drift detection.
| Name | Type | Req | Description |
|---|---|---|---|
| database | – | – | Database key (format: "type:name") |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the io.github.Fashad-Ahmed/universal-db-mcp server?
io.github.Fashad-Ahmed/universal-db-mcp runs locally as a PyPI package, launched with uvx universal-db-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · universal-db-mcp
claude mcp add fashad-ahmed-universal-db-mcp -- uvx universal-db-mcp
What is the io.github.Fashad-Ahmed/universal-db-mcp server?
io.github.Fashad-Ahmed/universal-db-mcp is listed in the public MCP registry as io.github.Fashad-Ahmed/universal-db-mcp. Security-first MCP server for PostgreSQL, SQLite, MySQL, DuckDB with SQL injection prevention. This page covers its PyPI package (universal-db-mcp).
Is the io.github.Fashad-Ahmed/universal-db-mcp server safe to use?
io.github.Fashad-Ahmed/universal-db-mcp scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. 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 io.github.Fashad-Ahmed/universal-db-mcp server expose?
io.github.Fashad-Ahmed/universal-db-mcp exposes 8 tools: query, schema, explain, health, query_history, and 3 more. Their descriptions and schemas cost roughly 344 tokens of context every time the server is loaded.
Is the io.github.Fashad-Ahmed/universal-db-mcp server still maintained?
io.github.Fashad-Ahmed/universal-db-mcp is still listed as active in the MCP registry. We last reached this channel on 4 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 io.github.Fashad-Ahmed/universal-db-mcp server under?
io.github.Fashad-Ahmed/universal-db-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.