Diagnose a production data problem or slow query, read-only
Two or three companies' docs show a full fit.
What counts as done
The agent returns the rows, plan or health finding that explains the problem, each finding naming what was examined, with no write, DDL or long-held lock on production.
Measured, for our own tests: every query ends within the statement timeout and returns no more than the configured row cap. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: why is this query slow
, find the rows that broke the import
, check database health
, is there a missing index
Does the job 2
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| DBHub BB Bytebase | Opt-in explain_sql never executes and rejects ANALYZE; query_timeout maps to statement_timeout; SSH tunnels per source; per-tool readonly and max_rows. An account runs production support across nine sources this way. source |
| MongoDB MCP Server A MongoDB, Inc. | explain returns winning-plan statistics, indexCheck rejects collection scans, readOnly removes write tools, and document and byte caps bound each result. source |
Does the job, with a limit 10
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| Mirage (AgentVFS) B Strukto.AI | A read-only mount with row and byte caps and a 30-second timeout can find bad rows, but there is no plan, explain or health check. source |
| ClickHouse MCP Server BB ClickHouse, Inc. | Read-only by default with a query timeout and EXPLAIN ESTIMATE or DESCRIBE, which do not run the body (scalar subqueries excepted), but there is no row cap, so the measured row-cap bar cannot hold. source |
| MCP Toolbox for Databases A Google LLC | Read-only session locks plus Postgres tools for active queries, long-running transactions and a database overview, but no EXPLAIN-without-execution tool was found for Postgres and execute_sql returns uncapped rows. source |
| Neon MCP Server BB Neon, LLC (subsidiary of Databricks, Inc.) | inspect_database runs 15 read-only checks, plus explain_sql_statement and list_slow_queries, but Neon's docs say never to connect MCP agents to production databases. source |
| ObsessionDB F Kellerkind UG (haftungsbeschränkt) | Monitoring tools list query patterns, executions, error signatures and table sizes; but with no read-only mode or scope documented for run_sql, the no-write guarantee rests on the agent. source |
| PlanetScale MCP Server BB PlanetScale, Inc. | Insights, query error patterns and executions, branch metrics and Postgres logs, with reads on a replica under a read-only role and a 50-second limit; no row cap. source |
| Postgres MCP Pro F Crystal Corp. | explain_query with hypothetical indexes, get_top_queries, analyze_query_indexes and analyze_db_health fit the job, but #211 shows health reporting no bloated indexes when none was examined, and #178 a restricted-mode file-read bypass, both open. source |
| Redis MCP C Redis Ltd. | A server-management tool returns database info and an ACL user can be read-only, but no slow-log, explain or row cap is documented, and runtime switching of logical databases is missing (#90). source |
| Snowflake-managed MCP server C Snowflake Inc. | SQL runs under the user's role, so a read role keeps writes out, but no explain, health or row-cap tool is offered; annotations are hints Snowflake does not enforce. source |
| Supabase API + MCP BB Supabase Pte. Ltd. | get_advisors and debugging logs with read-only mode, but no EXPLAIN-only tool or row cap, and accounts keep it off production. source |
Doesn't do this job 5
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| CoinMarketCap x402 API BB CoinMarketCap | No database connection, query plan or health tool; it serves vendor data only. source |
| Filesystem (MCP reference server) B Model Context Protocol, a Series of LF Projects, LLC | No database access. |
| Memory (MCP reference server) B Model Context Protocol, a Series of LF Projects, LLC | No database access. |
| Nansen x402 API B Nansen | No database connection, query plan or health tool; it serves vendor data only. source |
| ReqRes MCP server D ReqRes | No plans, health checks or access to a production database; a request log covers its own project only. source |
What stops agents finishing
- every command needs human review because no read-only boundary is trusted
- health check reports clean when it examined nothing
- production reachable only from inside a private network
Around it
Before: observability.read-error. After: code.ticket-to-pr, data.safe-migration.
Where this comes from
Weight 12 of 100 in Databases & files: 8 of 52 accounts (DBHub production-support comments, Ask HN on DB access, Postgres MCP Pro health check, QueryBear thread)
The same as data: /api/v1/use-cases/data.diagnose-prod.json, or the MCP tool get_use_case with id data.diagnose-prod. Other jobs in this category: /api/v1/niches?category=data.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.