C
codedb-io/codedb-lens
See what your database isn't showing you.
★ 8·updated 2026-11-06
View on GitHub ↗Direct link · no redirect page
We have neither an install command nor a public remote endpoint from this repository, so we do not print a config. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 8 ★ · codedb-io/codedb-lens · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 8 ★ · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
codedb-io/codedb-lens;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
See what your database isn't showing you.
Excerpted from the repository README (abridged)
Free, read-only health check for SQL Server and PostgreSQL .
Website · English · Português (Brasil)
Real run against a test SQL Server (host renamed). Open a demo report .
> v0.8: check (with an executive summary and --redact for sharing), compare, and record + report to watch an instance for up to 24 hours (how). 26 rules plus 8 for recordings. FAQ and more on the website.
codeDB Lens connects to your instance with a read-only login, runs a catalog of evidence-based
rules and writes a self-contained HTML + JSON report with an A–F grade and a coverage seal
(the share of rules that could actually run). Nothing about your database leaves your machine.
## Install
| Where | How |
| Windows | Installer (per user, no admin) or portable .zip |
| Windows (Scoop) | scoop bucket add codedb https://github.com/codedb-io/codedb-lens then scoop install codedb/codedb-lens |
| Linux | .deb / .rpm from the latest release, or the tarball for x64 / arm64 |
| Docker | docker run --rm -e PG_DSN -v "$PWD:/out" ghcr.io/codedb-io/codedb-lens check --engine pg --dsn-env PG_DSN --out /out |
The Windows binaries are open source but not code-signed yet, so SmartScreen may show a warning.
Why, and how to verify the download.
## Why another tool?
Evidence, not opinions. Every finding shows the collected values, the query that produced them and when.
Honest confidence. Each finding is Confirmed, Hint or No data. A rule that lacks permission
never shows up as a false "OK"; it lowers the coverage instead.
Read-only, always. No DDL, no DML, no agent, no installation on the server.
Rules are data. Each rule is a YAML file plus a SQL query. Contributions don't touch the engine.
English and Portuguese (Brazil), in the app, the CLI and the report.
## What it checks
| SQL Server | PostgreSQL |
| Missing or old backups | Version out of support |
| No recent clean DBCC CHECKDB | pg_stat_statements not available |
| Failing SQL Agent jobs | A single query dominating execution time |
| Disk or transaction log running out of space | Long and idle-in-transaction sessions |
| Dominant waits, translated | Sessions blocked by locks |
| Sessions blocked right now | Transaction ID wraparound risk |
| A single query dominating CPU | Dead rows and autovacuum falling behind |
| Instance settings left at defaults | Replication slots retaining WAL, replica lag |
| TempDB file layout | Connections near the limit, no pooler |
| Version out of support | Unused, duplicate and invalid indexes |
| High-impact missing indexes | Estimated table bloat |
| Unused and duplicate indexes | Largest tables |
Each rule has a documentation page with what it checks, why it matters, what to do and its limits.
## Quick start
On Windows, open codeDB Lens from the Start menu. Pick the engine, enter the server and run the diagnosis.
Connection profiles are saved; passwords go to the Windows Credential Manager.
Command line (Windows and Linux):
bash
codedb-lens check --engine mssql --server prod01 --auth windows
codedb-lens check --engine pg --dsn-env PG_DSN
Passwords are never accepted as command-line arguments. Use integrated auth, an environment variable or a saved profile.
## Use with AI (MCP)
Website · English · Português (Brasil)
Real run against a test SQL Server (host renamed). Open a demo report .
> v0.8: check (with an executive summary and --redact for sharing), compare, and record + report to watch an instance for up to 24 hours (how). 26 rules plus 8 for recordings. FAQ and more on the website.
codeDB Lens connects to your instance with a read-only login, runs a catalog of evidence-based
rules and writes a self-contained HTML + JSON report with an A–F grade and a coverage seal
(the share of rules that could actually run). Nothing about your database leaves your machine.
## Install
| Where | How |
| Windows | Installer (per user, no admin) or portable .zip |
| Windows (Scoop) | scoop bucket add codedb https://github.com/codedb-io/codedb-lens then scoop install codedb/codedb-lens |
| Linux | .deb / .rpm from the latest release, or the tarball for x64 / arm64 |
| Docker | docker run --rm -e PG_DSN -v "$PWD:/out" ghcr.io/codedb-io/codedb-lens check --engine pg --dsn-env PG_DSN --out /out |
The Windows binaries are open source but not code-signed yet, so SmartScreen may show a warning.
Why, and how to verify the download.
## Why another tool?
Evidence, not opinions. Every finding shows the collected values, the query that produced them and when.
Honest confidence. Each finding is Confirmed, Hint or No data. A rule that lacks permission
never shows up as a false "OK"; it lowers the coverage instead.
Read-only, always. No DDL, no DML, no agent, no installation on the server.
Rules are data. Each rule is a YAML file plus a SQL query. Contributions don't touch the engine.
English and Portuguese (Brazil), in the app, the CLI and the report.
## What it checks
| SQL Server | PostgreSQL |
| Missing or old backups | Version out of support |
| No recent clean DBCC CHECKDB | pg_stat_statements not available |
| Failing SQL Agent jobs | A single query dominating execution time |
| Disk or transaction log running out of space | Long and idle-in-transaction sessions |
| Dominant waits, translated | Sessions blocked by locks |
| Sessions blocked right now | Transaction ID wraparound risk |
| A single query dominating CPU | Dead rows and autovacuum falling behind |
| Instance settings left at defaults | Replication slots retaining WAL, replica lag |
| TempDB file layout | Connections near the limit, no pooler |
| Version out of support | Unused, duplicate and invalid indexes |
| High-impact missing indexes | Estimated table bloat |
| Unused and duplicate indexes | Largest tables |
Each rule has a documentation page with what it checks, why it matters, what to do and its limits.
## Quick start
On Windows, open codeDB Lens from the Start menu. Pick the engine, enter the server and run the diagnosis.
Connection profiles are saved; passwords go to the Windows Credential Manager.
Command line (Windows and Linux):
bash
codedb-lens check --engine mssql --server prod01 --auth windows
codedb-lens check --engine pg --dsn-env PG_DSN
Passwords are never accepted as command-line arguments. Use integrated auth, an environment variable or a saved profile.
## Use with AI (MCP)
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/codedb-io-codedb-lens/)
- Source
- awesome · https://github.com/codedb-io/codedb-lens
- Browse by field
- MCP servers
- Traction
- 8 ★
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.