Check the schema or data while writing code
Four or more companies' docs show a full fit.
What counts as done
The 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.
Measured, for our own tests: the schema lookup for one table takes no more than two calls and under 5,000 tokens. No docs we read state these figures, so they don't count against a listing here.
How 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
Does the job 7
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Mirage (AgentVFS) B 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. source |
| ClickHouse MCP Server BB 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. source |
| DBHub BB 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. source |
| MCP Toolbox for Databases A 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. source |
| MongoDB MCP Server A 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. source |
| Neon MCP Server BB 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. source |
| Supabase API + MCP BB Supabase Pte. Ltd. | list_tables under ?read_only=true&project_ref=...&functions=database,docs, which drops mutating tools; several accounts use it this way to check schemas and permissions before writing code. source |
Does the job, with a limit 5
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 |
|---|---|
| ObsessionDB F 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. source |
| PlanetScale MCP Server BB 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. source |
| Postgres MCP Pro F 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. source |
| Redis MCP C 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. source |
| Snowflake-managed MCP server C 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. 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 | A paid crypto market-data API (quotes, DEX search) with an x402 MCP endpoint; it exposes no schema of the person's database. source |
| Filesystem (MCP reference server) B Model Context Protocol, a Series of LF Projects, LLC | File tools only; no database connection. |
| Memory (MCP reference server) B Model Context Protocol, a Series of LF Projects, LLC | A knowledge-graph file store; no database schema or SQL. |
| Nansen x402 API B Nansen | A paid on-chain analytics API (wallets, Smart Money, token flows); it exposes no schema of the person's database. source |
| ReqRes MCP server D ReqRes | Works on its own hosted collections, not the repository's database. source |
What stops agents finishing
- tool list too large for the client (Cursor sends 40 tools)
- server fails to start on a fresh install after an upstream dependency change
- schema listing crashes on 100+ tables
Around it
Before: code.understand-codebase. After: code.ticket-to-pr.
Where this comes from
Weight 22 of 100 in Databases & files: 12 of 52 accounts; the most common job in the DBHub use-case thread and the Supabase MCP comments on Hacker News
The same as data: /api/v1/use-cases/data.schema-check.json, or the MCP tool get_use_case with id data.schema-check. 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.