model2data studio
PYPI · MODEL2DATA-STUDIO
Realistic fake data from a schema designed in model2data studio: preview rows, write seeds.
Available components
Last scanned (47 minutes ago)
Scores higher than 58% of PyPI servers
Category Testing and QA
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 Security49
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 3 of 16 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 41 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 496 tokens (~99/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.97 functional
- 29 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 25 Oct 26 0
- Stability: 0.97 → pass security
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 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 5 Nov 2026 · Analysed pypi/model2data-studio@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 16 packages
| Packages resolved | 16 |
|---|---|
| Stale | 3 |
| 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 →
account ~51
What this API key can do, and the limits its plan is under. Worth reading before asking for a lot of rows: the caps are per plan, and a refusal is a 402 rather than a smaller answer.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
describe_project ~87
One project's tables, columns, references and enums, as text. The column notes are included: a note holding JSON is a generation hint (`{"min": 5.99, "max": 999.99}`, `{"null_rate": 0.4}`), so it is what decides the values a column comes out with.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_projects ~33
The account's saved projects: the id to pass to the other tools, the name, and when it was last saved.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
preview_data ~145
Generate this project's data and return the rows themselves. Capped at fifty rows a table so the answer stays readable; every table says how many rows it really has. Use `write_data` for the whole set. `rows` overrides the project's row count, `seed` pins the values, `as_of` (YYYY-MM-DD) pins the day dates are placed around, and `locale` overrides the project's. Leave them out and the project's own settings are used, which are the ones the studio previewed.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | – |
| locale | – | – | – |
| project_id | string | yes | – |
| rows | – | – | – |
| seed | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
write_data ~121
Generate this project's data and write the files into `out_dir`. `export_format` is "csv" for seed files or "dbt" for a dbt project. Nothing is written if any target file already exists, unless `force` is true -- half-written fixtures are worse than none.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | – |
| export_format | string | – | – |
| force | boolean | – | – |
| locale | – | – | – |
| out_dir | string | yes | – |
| project_id | string | yes | – |
| rows | – | – | – |
| seed | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the model2data studio MCP server?
model2data studio runs locally as a PyPI package, launched with uvx model2data-studio. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · model2data-studio
claude mcp add jb-analytica-model2data-studio -- uvx model2data-studio
What is the model2data studio MCP server?
model2data studio is an MCP server listed in the public MCP registry as io.github.JB-Analytica/model2data-studio. Realistic fake data from a schema designed in model2data studio: preview rows, write seeds. This page covers its PyPI package (model2data-studio).
Is the model2data studio MCP server safe to use?
model2data studio scores 61 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 model2data studio MCP server expose?
model2data studio exposes 5 tools: account, list_projects, describe_project, preview_data, write_data. Their descriptions and schemas cost roughly 437 tokens of context every time the server is loaded.
Is the model2data studio MCP server still maintained?
model2data studio is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the model2data studio MCP server under?
model2data studio declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.