codeDB Lens
OCI · GHCR.IO/CODEDB-IO/CODEDB-LENS
Read-only health checks and data questions for SQL Server and PostgreSQL, with your saved profiles.
Available components
Last scanned (4 hours ago)
Scores higher than 64% of OCI 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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency35
- 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
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 7 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1452 tokens (~103/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 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
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.
Checks we ran (12)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
- Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
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.
- 6 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 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 0
- Stability: 0.03 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 0.9.0 → 0.9.1 functional
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 40
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 6 Nov 2026 · Analysed oci/ghcr.io/codedb-io/codedb-lens@0.9.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
check ~99
Run the codeDB Lens health check on a profile (read-only, 10-60 s): A-F grade with its coverage, findings with severity, confidence, evidence preview and next action, and rules without data. Saves the report in the profile's history, like the app does.
| Name | Type | Req | Description |
|---|---|---|---|
| profile | string | yes | profile name from list_profiles |
| redact | boolean | – | mask host, database, object, login and file names and drop query text |
| Name | Type | Req | Description |
|---|---|---|---|
| coverage | number | yes | – |
| findings | null|array | yes | – |
| grade | string | yes | – |
| no_data | null|array | yes | – |
| note | string | yes | – |
| passed | integer | yes | – |
| report | string | yes | – |
| score | number | yes | – |
| server | object | yes | – |
No examples provided.
compare ~93
Compare two runs of the same instance: new, resolved and persisting findings and the grade change. Default: the two latest runs. Needs the user's free key (codedb-lens register).
| Name | Type | Req | Description |
|---|---|---|---|
| a | string | – | older run path from history; default: the second latest |
| b | string | – | newer run path from history; default: the latest |
| profile | string | yes | profile name from list_profiles |
| Name | Type | Req | Description |
|---|---|---|---|
| after | object | yes | – |
| before | object | yes | – |
| changed | null|array | yes | – |
| new | null|array | yes | – |
| persisting | null|array | yes | – |
| report | string | yes | – |
| resolved | null|array | yes | – |
| warnings | null|array | – | – |
No examples provided.
describe_table ~100
Columns (type, nullable, default), primary key, foreign keys with the referenced table, indexes and estimated rows of one table or view. Use it before writing a query, so column names are right.
| Name | Type | Req | Description |
|---|---|---|---|
| database | string | – | database name from list_databases; default: the profile's |
| profile | string | yes | profile name from list_profiles |
| table | string | yes | table or view: schema.name, or name in the default schema |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | null|array | yes | – |
| estimated_rows | null|integer | – | – |
| foreign_keys | null|array | yes | – |
| indexes | null|array | yes | – |
| name | string | yes | – |
| primary_key | null|array | yes | – |
| schema | string | yes | – |
| type | string | yes | – |
No examples provided.
explain_rule ~71
Explain one rule: what it measures, why it matters, the next action, how to verify the fix, the permission it needs, its SQL and its documentation link.
| Name | Type | Req | Description |
|---|---|---|---|
| rule_id | string | yes | rule ID, e.g. MSSQL-BACKUP-001 or PG-AUTOVAC-001 |
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | – |
| caveat | string | – | – |
| doc_url | string | yes | – |
| engine | string | yes | – |
| id | string | yes | – |
| impact | string | yes | – |
| kind | string | – | – |
| next_action | string | yes | – |
| permission | string | yes | – |
| severity | string | yes | – |
| sql | string | – | – |
| title | string | yes | – |
| verify | string | yes | – |
No examples provided.
get_finding ~95
Full detail of one rule in a saved run: status, impact, next action, how to verify the fix, and all evidence rows. Default run: the latest.
| Name | Type | Req | Description |
|---|---|---|---|
| profile | string | yes | profile name from list_profiles |
| rule_id | string | yes | rule ID from check, e.g. MSSQL-BACKUP-001 |
| run | string | – | run path from history; default: the latest run |
| Name | Type | Req | Description |
|---|---|---|---|
| caveat | string | – | – |
| columns | null|array | – | – |
| confidence | string | yes | – |
| doc_url | string | yes | – |
| id | string | yes | – |
| impact | string | yes | – |
| next_action | string | yes | – |
| reason | string | – | – |
| rows | null|array | – | – |
| run | string | yes | – |
| run_at | string | yes | – |
| severity | string | yes | – |
| status | string | yes | – |
| title | string | yes | – |
| total_rows | integer | yes | – |
| truncated | boolean | – | – |
| verify | string | yes | – |
No examples provided.
history ~75
Saved check runs of a profile, newest first: date, grade, coverage and number of findings. Each run's path can be passed to get_finding or compare.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | how many runs, newest first (default 10, at most 50) |
| profile | string | yes | profile name from list_profiles |
| Name | Type | Req | Description |
|---|---|---|---|
| runs | null|array | yes | – |
No examples provided.
list_databases ~46
Databases this profile's login can open: name, state, recovery model or encoding, collation and size in bytes.
| Name | Type | Req | Description |
|---|---|---|---|
| profile | string | yes | profile name from list_profiles |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | null|array | yes | – |
| note | string | – | – |
| rows | null|array | yes | – |
| truncated | boolean | yes | – |
No examples provided.
list_profiles ~35
List the saved connection profiles you may use: name, engine, host, initial database and language. Never returns passwords or connection strings.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | – |
| profiles | null|array | yes | – |
No examples provided.
list_recordings ~71
Recordings (activity sampled every 15 s for 1 or 24 h) kept with a profile's reports, newest first. Recordings made elsewhere can still be read with recording_report and their folder.
| Name | Type | Req | Description |
|---|---|---|---|
| profile | string | – | profile name; empty lists the recordings of every profile you may use |
| Name | Type | Req | Description |
|---|---|---|---|
| recordings | null|array | yes | – |
No examples provided.
list_rules ~57
List the Lens rule catalog (health checks): ID, engine, category, severity and title. Kind "series" rules judge recordings, the others run in a check.
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | – | mssql or pg; empty lists both |
| Name | Type | Req | Description |
|---|---|---|---|
| rules | null|array | yes | – |
No examples provided.
list_tables ~113
Tables and views visible to the profile's login in a database: schema, name, type, estimated rows, size and whether the login can read them. Start here, then describe_table, then query.
| Name | Type | Req | Description |
|---|---|---|---|
| database | string | – | database name from list_databases; default: the profile's |
| filter | string | – | name pattern: plain text matches anywhere in the name, or a LIKE pattern with % |
| profile | string | yes | profile name from list_profiles |
| schema | string | – | only this schema |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | null|array | yes | – |
| note | string | – | – |
| rows | null|array | yes | – |
| truncated | boolean | yes | – |
No examples provided.
query ~192
Run one read-only SELECT (or WITH ... SELECT) on a profile and get columns and rows. Aggregate in SQL (GROUP BY, TOP/LIMIT) instead of fetching raw rows: results stop at the profile's row limit (500 unless the user changed it), cells at 2 KB, and truncated: true means the answer is partial. Writes, EXEC, multiple statements and functions with side effects are refused; quote a column named like an SQL keyword. SQL Server reads uncommitted data, like the health check.
| Name | Type | Req | Description |
|---|---|---|---|
| database | string | – | database name from list_databases; default: the profile's |
| max_rows | integer | – | row limit; default and ceiling: the profile's |
| profile | string | yes | profile name from list_profiles |
| sql | string | yes | one SELECT or WITH ... SELECT statement |
| timeout_s | integer | – | seconds; default and ceiling: the profile's |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | null|array | yes | – |
| elapsed_ms | integer | yes | – |
| note | string | – | – |
| rows | null|array | yes | – |
| truncated | boolean | yes | – |
| warning | string | – | – |
No examples provided.
record_command ~107
The command the user runs in a terminal (or on the server) to record a profile for up to 1 h, or 24 h with the free key. You cannot start a recording: give the user this command.
| Name | Type | Req | Description |
|---|---|---|---|
| duration | string | – | how long to record, e.g. 30m, 1h or 24h (default 1h; more than 1h needs the free key) |
| profile | string | yes | profile name from list_profiles |
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | – |
| note | string | yes | – |
| report_command | string | yes | – |
| server_command | string | yes | – |
No examples provided.
recording_report ~129
Analyse a recording, optionally for a period (e.g. an incident): time coverage, gaps without data, findings as episodes (blocking, waits, long queries, workers or connections), peak of each chart and the top queries. Also writes the HTML report into the recording folder.
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | yes | recording folder, from list_recordings or given by the user |
| from | string | – | start of the period, RFC 3339 (default: start of the recording) |
| to | string | – | end of the period, RFC 3339 (default: end of the recording) |
| Name | Type | Req | Description |
|---|---|---|---|
| charts | null|array | yes | – |
| coverage | number | yes | – |
| findings | null|array | yes | – |
| from | string | yes | – |
| gaps | null|array | yes | – |
| report | string | yes | – |
| server | object | yes | – |
| started | string | yes | – |
| stop_reason | string | – | – |
| stopped | string | – | – |
| to | string | yes | – |
| top_queries | object | yes | – |
No examples provided.
How do I install the codeDB Lens MCP server?
codeDB Lens runs locally as a container image, launched with docker run --rm -i -e CODEDB_LENS_PASSWORD ghcr.io/codedb-io/codedb-lens:0.9.1 mcp, plus the required --engine and --server, which you supply. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/codedb-io/codedb-lens
claude mcp add codedb-io-codedb-lens -- docker run --rm -i -e CODEDB_LENS_PASSWORD ghcr.io/codedb-io/codedb-lens:0.9.1 mcp
This image reads CODEDB_LENS_PASSWORD. Set it in your client's env block for this server; docker run -e passes it through to the container. Incomplete: the registry marks --engine and --server as required and gives no value we can show, so they are not in this command. Add them before you run it.
What is the codeDB Lens MCP server?
codeDB Lens is an MCP server listed in the public MCP registry as io.github.codedb-io/codedb-lens. Read-only health checks and data questions for SQL Server and PostgreSQL, with your saved profiles. This page covers its container image (ghcr.io/codedb-io/codedb-lens).
Is the codeDB Lens MCP server safe to use?
codeDB Lens scores 45 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 codeDB Lens MCP server expose?
codeDB Lens exposes 14 tools: check, compare, describe_table, explain_rule, get_finding, and 9 more. Their descriptions and schemas cost roughly 1,283 tokens of context every time the server is loaded.
Is the codeDB Lens MCP server still maintained?
codeDB Lens is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the codeDB Lens MCP server?
VerifyMCP ran 12 checks on codeDB Lens, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about codeDB Lens: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.