# model2data studio (pypi · model2data-studio)

Realistic fake data from a schema designed in model2data studio: preview rows, write seeds.

- Trust score: 61/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `model2data-studio`: 61/100 (this document), [markdown](https://verifymcp.io/servers/jb-analytica-model2data-studio/model2data-studio.md), [page](https://verifymcp.io/servers/jb-analytica-model2data-studio/model2data-studio)

## Channel facts

- Registry: `pypi`
- Package: `model2data-studio`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 49/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 3 of 16 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 41 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 496 tokens (~99/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add jb-analytica-model2data-studio -- uvx model2data-studio
```

### Cursor

```json
{
  "mcpServers": {
    "jb-analytica-model2data-studio": {
      "command": "uvx",
      "args": [
        "model2data-studio"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "jb-analytica-model2data-studio": {
      "command": "uvx",
      "args": [
        "model2data-studio"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add jb-analytica-model2data-studio -- uvx model2data-studio
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jb-analytica-model2data-studio": {
      "type": "local",
      "command": [
        "uvx",
        "model2data-studio"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add jb-analytica-model2data-studio --command uvx --arg model2data-studio
```

### Hermes

```yaml
mcp_servers:
  jb-analytica-model2data-studio:
    command: "uvx"
    args: ["model2data-studio"]
```

### Netclaw

```json
{
  "McpServers": {
    "jb-analytica-model2data-studio": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "model2data-studio"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add jb-analytica-model2data-studio -t stdio -c uvx -a model2data-studio
```

### Other

```json
{
  "mcpServers": {
    "jb-analytica-model2data-studio": {
      "command": "uvx",
      "args": [
        "model2data-studio"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 61, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-01 (score 76, 0)

- [security] Stability: 0.97 → pass

### 2026-10-31 (score 76, +15)

- [security improvement] Malware scan: unverified → pass
- [functional] Stability: pass → 0.97

### 2026-10-29 (score 61, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-25 (score 76, 0)

- [security] Stability: 0.97 → pass

### 2026-10-24 (score 76, +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.

### 2026-10-21 (score 75, +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.

### 2026-10-19 (score 74, +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.

## MCP tools (5)

### `account` (~51 tokens)

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.

Output parameters:

- `result` (string)

### `list_projects` (~33 tokens)

The account's saved projects: the id to pass to the other tools,
the name, and when it was last saved.

Output parameters:

- `result` (string)

### `describe_project` (~87 tokens)

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.

Input parameters:

- `project_id` (string, required)

Output parameters:

- `result` (string)

### `preview_data` (~145 tokens)

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.

Input parameters:

- `as_of`
- `locale`
- `project_id` (string, required)
- `rows`
- `seed`

Output parameters:

- `result` (string)

### `write_data` (~121 tokens)

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.

Input parameters:

- `as_of`
- `export_format` (string)
- `force` (boolean)
- `locale`
- `out_dir` (string, required)
- `project_id` (string, required)
- `rows`
- `seed`

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/jb-analytica-model2data-studio/model2data-studio#diagnostics

## Score history

- 2026-11-05: 61
- 2026-11-04: 61
- 2026-11-03: 61
- 2026-11-02: 76
- 2026-11-01: 76
- 2026-10-31: 76
- 2026-10-30: 61
- 2026-10-29: 61
- 2026-10-28: 76
- 2026-10-27: 76
- 2026-10-26: 76
- 2026-10-25: 76
- 2026-10-24: 76
- 2026-10-23: 75
- 2026-10-22: 75
- 2026-10-21: 75
- 2026-10-20: 74
- 2026-10-19: 74
- 2026-10-18: 73
- 2026-10-17: 73
- 2026-10-16: 72
- 2026-10-15: 57
- 2026-10-14: 56
- 2026-10-13: 56
- 2026-10-12: 55
- 2026-10-08: 53
- 2026-10-04: 52
- 2026-10-03: 51
- 2026-10-02: 47
- 2026-10-01: 47

## Common questions

### 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.

## Links

- PyPI project: https://pypi.org/project/model2data-studio/
- Socket report: https://socket.dev/pypi/package/model2data-studio
- Website: https://www.jbanalytica.com/model2data/
- Changelog RSS feed: https://verifymcp.io/servers/jb-analytica-model2data-studio/model2data-studio.xml
- Changelog JSON feed: https://verifymcp.io/servers/jb-analytica-model2data-studio/model2data-studio.json
- HTML version of this page: https://verifymcp.io/servers/jb-analytica-model2data-studio/model2data-studio