{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/data.schema-check/",
    "json": "https://www.anchorterminal.com/niches/data.schema-check/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/data.schema-check/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/data.schema-check/index.min.md"
  },
  "markdown": "Four or more 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| 7 | 5 | 15 | 22 | 12 |\n\n## What counts as done\n\nThe agent names the tables and columns it needs from the live schema, runs at most a few bounded SELECT or find calls, and writes code that matches them, with no write statement reaching the database.\n\nMeasured, for our own tests: the schema lookup for one table takes no more than two calls and under 5,000 tokens.\n\nHow agents ask for it: what columns does the orders table have; check the schema before you write the migration; does this user have the right role in the database; verify this query returns what the feature expects\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **Mirage (AgentVFS) (Strukto.AI)**: PostgresVFS mounts read-only with a schemas allowlist; each table has schema.json (types, keys, indexes) and semantic.json, and head or tail on rows.jsonl asks SQL for only those rows, under row and byte caps.\n- **ClickHouse MCP Server (ClickHouse, Inc.)**: list_tables takes like filters, page_size and page tokens, and include_detailed_columns=false trims output; read-only is enforced server-side with readonly=1 by default. The 100+ table crash in #25 led to the pagination now documented.\n- **DBHub (Bytebase)**: search_objects finds tables by pattern at names, summary or full detail with a limit; read-only is enforced by a keyword allow-list plus the engine's read-only transaction. Two accounts use it for schema checks before writing code.\n- **MCP Toolbox for Databases (Google LLC)**: postgres-list-tables takes table_names and a simple or detailed output_format, so one table is one call; read-only sources lock the session at engine level and prune write tools from tools/list.\n- **MongoDB MCP Server (MongoDB, Inc.)**: list-collections and collection-schema describe collections; --readOnly leaves only read, connect and metadata tools registered; find and aggregate stop at 100 documents by default; --disabledTools atlas trims the list.\n- **Neon MCP Server (Neon, LLC (subsidiary of Databricks, Inc.))**: get_database_tables and describe_table_schema under ?category=schema; ?readonly=true disables writes; run_sql returns 100 rows by default and says when it cut a result; roleName makes grants decide what is read.\n- **Supabase API + MCP (Supabase Pte. Ltd.)**: list_tables under ?read_only=true\u0026project_ref=...\u0026functions=database,docs, which drops mutating tools; several accounts use it this way to check schemas and permissions before writing code.\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- **ObsessionDB (Kellerkind UG (haftungsbeschränkt))**: No schema tool; the agent reads system tables or DESCRIBE through run_sql. The workbench:query scope runs any SQL and no read-only mode is documented, so nothing stops a write reaching the database.\n- **PlanetScale MCP Server (PlanetScale, Inc.)**: execute_read_query runs under a read-only database role with short-lived credentials and a 50-second cancel, but returns every row with no cap, and the schema tools sit in the closed, generated part of the server that could not be read.\n- **Postgres MCP Pro (Crystal Corp.)**: list_schemas, list_objects and get_object_details find one table's columns, and restricted mode runs read-only transactions, but #237 (open) reports 0.1.1 to 0.3.0 failing to install after an upstream change, and unrestricted is every README example's default.\n- **Redis MCP (Redis Ltd.)**: Keys, hashes, JSON and index info can be inspected, but the server has no read-only switch: write and delete tools stay listed, and the README's answer is a read-only Redis ACL user.\n- **Snowflake-managed MCP server (Snowflake Inc.)**: A SYSTEM_EXECUTE_SQL tool can read information_schema under the caller's role, but there is no schema tool, and an administrator must first create the MCP server object and an OAuth security integration.\n\n- not this job: CoinMarketCap x402 API (CoinMarketCap): A paid crypto market-data API (quotes, DEX search) with an x402 MCP endpoint; it exposes no schema of the person's database.\n- not this job: Filesystem (MCP reference server) (Model Context Protocol, a Series of LF Projects, LLC): File tools only; no database connection.\n- not this job: Memory (MCP reference server) (Model Context Protocol, a Series of LF Projects, LLC): A knowledge-graph file store; no database schema or SQL.\n- not this job: Nansen x402 API (Nansen): A paid on-chain analytics API (wallets, Smart Money, token flows); it exposes no schema of the person's database.\n- not this job: ReqRes MCP server (ReqRes): Works on its own hosted collections, not the repository's database.\n\n## What stops agents finishing\n\n- tool list too large for the client (Cursor sends 40 tools)\n- server fails to start on a fresh install after an upstream dependency change\n- schema listing crashes on 100+ tables\n\n## Around it\n\nBefore: code.understand-codebase. After: code.ticket-to-pr.\n\n## Where this comes from\n\nWeight 22 of 100 in Databases \u0026 files: 12 of 52 accounts; the most common job in the DBHub use-case thread and the Supabase MCP comments on Hacker News\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/data.schema-check.json, or the MCP tool get_use_case with id data.schema-check. 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": "Check the schema or data while writing code",
        "url": ""
      }
    ],
    "description": "Check the schema or data while writing code: 7 companies fully do it, 5 with a limit, 15 carry the tag. Every listing in Databases \u0026 files with the reason and a source.",
    "facts": null,
    "h1": "Check the schema or data while writing code",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/data.schema-check/",
    "published": "",
    "section": "agents",
    "title": "Check the schema or data while writing code | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/data.schema-check/"
  },
  "tokens": {
    "markdown": 1550,
    "slim": 330
  },
  "version": 1
}
