BigQuery Data Platform
PYPI · DATA-PLATFORM-MCP · SCANNED SEP 20
Read-only BigQuery tools for plain-language data questions, with a cost gate on every query
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 54 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 11 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2462 tokens (~223/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the BigQuery Data Platform MCP server?
BigQuery Data Platform runs locally as a PyPI package, launched with uvx data-platform-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · data-platform-mcp
claude mcp add debilla-data-platform-mcp -- uvx data-platform-mcp
{
"mcpServers": {
"debilla-data-platform-mcp": {
"command": "uvx",
"args": [
"data-platform-mcp"
]
}
}
} {
"servers": {
"debilla-data-platform-mcp": {
"command": "uvx",
"args": [
"data-platform-mcp"
]
}
}
} codex mcp add debilla-data-platform-mcp -- uvx data-platform-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"debilla-data-platform-mcp": {
"type": "local",
"command": [
"uvx",
"data-platform-mcp"
],
"enabled": true
}
}
} openclaw mcp add debilla-data-platform-mcp --command uvx --arg data-platform-mcp
mcp_servers:
debilla-data-platform-mcp:
command: "uvx"
args: ["data-platform-mcp"] {
"McpServers": {
"debilla-data-platform-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"data-platform-mcp"
]
}
}
} assistant mcp add debilla-data-platform-mcp -t stdio -c uvx -a data-platform-mcp
{
"mcpServers": {
"debilla-data-platform-mcp": {
"command": "uvx",
"args": [
"data-platform-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 0
- Malware scan: pass → unverified ▼ security
- Schema quality: 1722 → 2462 ▼ functional
- Schema quality: 1722 → 2348 ▼ functional
- Package version: 0.2.0 → 0.3.3 functional
- Package version: 0.2.0 → 0.3.1 functional
- Package version: 0.2.0 → 0.3.0 functional
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/data-platform-mcp@0.3.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 54 packages
| Packages resolved | 54 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_table_freshness ~175
Report when tables were last written, to catch stale or dead sources. Several plausible-looking tables on this platform stopped being updated without being dropped, so a query against one silently returns old data. Check before trusting a table you have not used before. Free — reads table metadata only, scanning no data. Args: dataset_id: The dataset to check, e.g. "events_raw". table_id: A single table to check. Omit to report every table in the dataset, which is the faster way to spot a dead one. environment: Which configured BigQuery environment to use. Omit to use the default. Call list_environments to see what exists.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | – |
| environment | string | – | – |
| table_id | string | – | – |
No output schema declared.
No examples provided.
find_code_assets_using_table ~220
Find which Colab notebooks and saved queries reference a table. The question to ask before changing or dropping a table: ``list_scheduled_queries`` says what writes it, this says who reads it. Unlike the other tools here this one opens every asset it considers, which costs Dataform read quota. It is bounded by ``max_assets`` and reports how much of the project it actually covered -- a result is evidence about the assets scanned, never proof that nothing else uses the table. Args: table: Table name to search for. A bare name matches any qualification; 'dataset.table' or a fully-qualified name narrows it. environment: Which configured environment to read. Omit for the default. asset_type: Restrict to 'sql', 'notebook' or 'data_canvas'. max_assets: Ceiling on how many bodies to read.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_type | string | – | – |
| environment | string | – | – |
| max_assets | integer | – | – |
| table | string | yes | – |
No output schema declared.
No examples provided.
get_code_asset ~100
Return one Colab notebook or saved query's contents, by name or id. Notebook outputs are stripped -- across 52 real notebooks they were 77% of the bytes, and none of the logic. Args: asset: Display name (as shown in BigQuery Studio) or the asset id. environment: Which configured environment to read. Omit for the default.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | – |
| environment | string | – | – |
No output schema declared.
No examples provided.
get_scheduled_query ~114
Get one scheduled query in full: its SQL, destination, and recent runs. Call this after list_scheduled_queries to see why a query is failing, or what SQL actually produces a table. Args: query: The scheduled query's name, or the id from list_scheduled_queries. runs: How many recent runs to include, newest first. environment: Which configured environment to look in.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | – |
| query | string | yes | – |
| runs | integer | – | – |
No output schema declared.
No examples provided.
get_table_schema ~195
Get a table's columns, partitioning, size and freshness. Free — scans no data. Call this before writing a query, for two reasons beyond column names: - `partitioning` says whether a WHERE clause can actually limit the scan. A date-shaped column name does NOT mean the table is partitioned; if this field is null, every query reads the whole table. - Nested columns are expanded to dotted paths and flagged `repeated`, which is what tells you a column needs UNNEST. Args: dataset_id: The dataset, e.g. "events_raw". table_id: The table or view name. environment: Which configured BigQuery environment to use. Omit to use the default. Call list_environments to see what exists.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | – |
| environment | string | – | – |
| table_id | string | yes | – |
No output schema declared.
No examples provided.
list_code_assets ~217
List Colab notebooks and saved queries in BigQuery Studio. Use this for anything the user calls a Colab notebook, Colab Enterprise notebook, "colab script", BigQuery notebook, saved query or data canvas -- BigQuery Studio stores all of them as code assets and this lists them all. Free -- this reads metadata only and never opens an asset. Bodies are what cost quota, so filter here first and open individual assets afterwards. Args: environment: Which configured environment to read. Omit for the default. asset_type: Restrict to one of 'sql', 'notebook', 'data_canvas'. Saved queries usually outnumber notebooks by a wide margin, so this is the difference between a readable answer and 600 rows. name_contains: Case-insensitive substring match on the display name. limit: Maximum assets to return.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_type | string | – | – |
| environment | string | – | – |
| limit | integer | – | – |
| name_contains | string | – | – |
No output schema declared.
No examples provided.
list_datasets ~74
List the BigQuery datasets available in the data platform project. Call this first to discover what data exists. Free — scans no data. Args: environment: Which configured BigQuery environment to use. Omit to use the default. Call list_environments to see what exists.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | – |
No output schema declared.
No examples provided.
list_environments ~59
List the configured BigQuery environments and which one is the default. Call this when the user names an environment you have not seen, or when a question could plausibly be about more than one. Free — reads only this server's configuration.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_scheduled_queries ~211
List scheduled queries: what they write, when they run, and their state. Use this to answer "what populates this table?" and "why is this table stale?" — a disabled or failing scheduled query is the usual cause, and check_table_freshness can see the staleness but not the reason. The SQL is not included here; call get_scheduled_query for one of them. Args: dataset: Only queries writing into this destination dataset. contains: Only queries whose name contains this text. include_disabled: Keep disabled queries in the result. They are the most likely explanation for a table that stopped updating, so this defaults to True. environment: Which configured environment to look in. Scheduled queries are regional, so this must be the environment whose location holds them.
| Name | Type | Req | Description |
|---|---|---|---|
| contains | string | – | – |
| dataset | string | – | – |
| environment | string | – | – |
| include_disabled | boolean | – | – |
No output schema declared.
No examples provided.
list_tables ~84
List tables and views inside a dataset. Free — scans no data. Args: dataset_id: The dataset to inspect, e.g. "events_raw". environment: Which configured BigQuery environment to use. Omit to use the default. Call list_environments to see what exists.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | – |
| environment | string | – | – |
No output schema declared.
No examples provided.
run_query ~309
Run a read-only (SELECT/WITH) SQL query against BigQuery and return rows. Cost safety: the query is ALWAYS dry-run first to estimate how much data it will scan. If that estimate is above the warning threshold, the query does NOT run — instead this returns `status: "confirmation_required"` with the estimated size and cost. Stop there, tell the user the estimated scan and cost, and ask. Only re-call with confirm_expensive=true once they have agreed: that flag records the user's decision, not yours. Queries above the hard cap never run, even with confirmation. Always fully-qualify tables as `<project>.<dataset>.<table>`, and check get_table_schema first — a WHERE clause only limits the scan on a table that is actually partitioned. Args: sql: A SELECT (or WITH ... SELECT) query. max_rows: Max rows to return, to keep responses small. 0 (the default) uses the server's configured limit. confirm_expensive: Set True only after the user has agreed to a query previously flagged as costly. Leave False for the first attempt. environment: Which configured BigQuery environment to query. Omit to use the default. Call list_environments to see what exists.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_expensive | boolean | – | – |
| environment | string | – | – |
| max_rows | integer | – | – |
| sql | string | yes | – |
No output schema declared.
No examples provided.
What is the BigQuery Data Platform MCP server?
BigQuery Data Platform is an MCP server listed in the public MCP registry as io.github.deBilla/data-platform-mcp. Read-only BigQuery tools for plain-language data questions, with a cost gate on every query. This page covers its PyPI package (data-platform-mcp).
Is the BigQuery Data Platform MCP server safe to use?
BigQuery Data Platform scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the BigQuery Data Platform MCP server expose?
BigQuery Data Platform exposes 11 tools: list_environments, list_datasets, list_tables, get_table_schema, check_table_freshness, and 6 more. Their descriptions and schemas cost roughly 1,758 tokens of context every time the server is loaded.
Is the BigQuery Data Platform MCP server still maintained?
BigQuery Data Platform is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.