{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/data.diagnose-prod/",
    "json": "https://www.anchorterminal.com/niches/data.diagnose-prod/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/data.diagnose-prod/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/data.diagnose-prod/index.min.md"
  },
  "markdown": "Two or three companies' docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 2 | 10 | 14 | 12 | 8 |\n\n## What counts as done\n\nThe 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.\n\nMeasured, for our own tests: every query ends within the statement timeout and returns no more than the configured row cap.\n\nHow agents ask for it: why is this query slow; find the rows that broke the import; check database health; is there a missing index\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **DBHub (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.\n- **MongoDB MCP Server (MongoDB, Inc.)**: explain returns winning-plan statistics, indexCheck rejects collection scans, readOnly removes write tools, and document and byte caps bound each result.\n\n## Does the job, with a limit\n\nIt 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.\n\n- **Mirage (AgentVFS) (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.\n- **ClickHouse MCP Server (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.\n- **MCP Toolbox for Databases (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.\n- **Neon MCP Server (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.\n- **ObsessionDB (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.\n- **PlanetScale MCP Server (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.\n- **Postgres MCP Pro (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.\n- **Redis MCP (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).\n- **Snowflake-managed MCP server (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.\n- **Supabase API + MCP (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.\n\n- not this job: CoinMarketCap x402 API (CoinMarketCap): No database connection, query plan or health tool; it serves vendor data only.\n- not this job: Filesystem (MCP reference server) (Model Context Protocol, a Series of LF Projects, LLC): No database access.\n- not this job: Memory (MCP reference server) (Model Context Protocol, a Series of LF Projects, LLC): No database access.\n- not this job: Nansen x402 API (Nansen): No database connection, query plan or health tool; it serves vendor data only.\n- not this job: ReqRes MCP server (ReqRes): No plans, health checks or access to a production database; a request log covers its own project only.\n\n## What stops agents finishing\n\n- every command needs human review because no read-only boundary is trusted\n- health check reports clean when it examined nothing\n- production reachable only from inside a private network\n\n## Around it\n\nBefore: observability.read-error. After: code.ticket-to-pr, data.safe-migration.\n\n## Where this comes from\n\nWeight 12 of 100 in Databases \u0026 files: 8 of 52 accounts (DBHub production-support comments, Ask HN on DB access, Postgres MCP Pro health check, QueryBear thread)\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/data.diagnose-prod.json, or the MCP tool get_use_case with id data.diagnose-prod. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Diagnose a production data problem or slow query, read-only",
        "url": ""
      }
    ],
    "description": "Diagnose a production data problem or slow query, read-only: 2 companies fully do it, 10 with a limit, 14 carry the tag. Every listing in Databases \u0026 files with the reason and a source.",
    "facts": null,
    "h1": "Diagnose a production data problem or slow query, read-only",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/data.diagnose-prod/",
    "published": "",
    "section": "agents",
    "title": "Diagnose a production data problem or slow query, read-only | Anchor…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/data.diagnose-prod/"
  },
  "tokens": {
    "markdown": 1450,
    "slim": 330
  },
  "version": 1
}
