io.github.renanlido/custom-mcp-database
PYPI · CUSTOM-MCP-DATABASE · SCANNED SEP 20
Run alias-based queries against PostgreSQL, MySQL, MongoDB and Oracle without exposing credentials.
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 → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 38 of 40 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- Dependency health was assessed across the 38 of 40 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency48
- 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 91 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 316 tokens (~79/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 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 (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.renanlido/custom-mcp-database server?
io.github.renanlido/custom-mcp-database runs locally as a PyPI package, launched with uvx custom-mcp-database. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · custom-mcp-database
claude mcp add renanlido-custom-mcp-database -- uvx custom-mcp-database
{
"mcpServers": {
"renanlido-custom-mcp-database": {
"command": "uvx",
"args": [
"custom-mcp-database"
]
}
}
} {
"servers": {
"renanlido-custom-mcp-database": {
"command": "uvx",
"args": [
"custom-mcp-database"
]
}
}
} codex mcp add renanlido-custom-mcp-database -- uvx custom-mcp-database
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"renanlido-custom-mcp-database": {
"type": "local",
"command": [
"uvx",
"custom-mcp-database"
],
"enabled": true
}
}
} openclaw mcp add renanlido-custom-mcp-database --command uvx --arg custom-mcp-database
mcp_servers:
renanlido-custom-mcp-database:
command: "uvx"
args: ["custom-mcp-database"] {
"McpServers": {
"renanlido-custom-mcp-database": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"custom-mcp-database"
]
}
}
} assistant mcp add renanlido-custom-mcp-database -t stdio -c uvx -a custom-mcp-database
{
"mcpServers": {
"renanlido-custom-mcp-database": {
"command": "uvx",
"args": [
"custom-mcp-database"
]
}
}
} 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.
- 20 Sept 26 −2
- Stability: pass → 0.83 functional
- 19 Sept 26 0
- Stability: 0.97 → pass security
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 −3
- Stability: pass → 0.80 functional
- 12 Sept 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 20 Sept 2026 · Analysed pypi/custom-mcp-database@0.6.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 38 packages
| Packages resolved | 38 |
|---|---|
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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 →
db_execute_query ~178
Run a query against a configured database. SQL (postgres/mysql/oracle): pass the SQL string in ``query`` and optional bind values in ``params`` (use the driver's placeholder style; Oracle uses ``:name``). Add your own LIMIT/WHERE to keep results small. MongoDB: pass a JSON filter object in ``query`` and the ``collection`` name. 24-char hex strings are coerced to ObjectId; empty filters are rejected; results are capped at ``limit`` documents (default 10). Returns: {"data": [...], "row_count": int} (plus "error" on a rejected empty Mongo filter)
| Name | Type | Req | Description |
|---|---|---|---|
| collection | – | – | – |
| database_alias | string | yes | – |
| limit | integer | – | – |
| oracle_schema | – | – | – |
| params | – | – | – |
| query | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
db_list_aliases ~45
List every configured database alias and its type. Returns: {"aliases": [{"alias": str, "type": "postgres|mysql|mongo|oracle"}, ...]}
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
db_list_collections ~40
List all collections for a configured MongoDB alias. Returns: {"collections": [str, ...]}
| Name | Type | Req | Description |
|---|---|---|---|
| database_alias | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
db_security_status ~53
Report the active security policy. Returns: {"readonly": bool, "allow_writes": bool, "allow_ddl": bool, "max_rows": int, "mongo_javascript_blocked": bool}
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
What is the io.github.renanlido/custom-mcp-database server?
io.github.renanlido/custom-mcp-database is listed in the public MCP registry as io.github.renanlido/custom-mcp-database. Run alias-based queries against PostgreSQL, MySQL, MongoDB and Oracle without exposing credentials. This page covers its PyPI package (custom-mcp-database).
Is the io.github.renanlido/custom-mcp-database server safe to use?
io.github.renanlido/custom-mcp-database scores 78 out of 100 on VerifyMCP. 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.renanlido/custom-mcp-database server expose?
io.github.renanlido/custom-mcp-database exposes 4 tools: db_list_aliases, db_list_collections, db_execute_query, db_security_status. Their descriptions and schemas cost roughly 316 tokens of context every time the server is loaded.
Is the io.github.renanlido/custom-mcp-database server still maintained?
io.github.renanlido/custom-mcp-database is still listed as active in the MCP registry. We last reached this channel on 20 September 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.renanlido/custom-mcp-database server under?
io.github.renanlido/custom-mcp-database declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.