io.github.vpatser1/mcp-schema-designer
NPM · MCP-SCHEMA-DESIGNER · SCANNED SEP 24
Design database schemas from natural language, validate SQL, generate migrations and types
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 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 50 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 430 tokens (~86/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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.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 5 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 io.github.vpatser1/mcp-schema-designer server?
io.github.vpatser1/mcp-schema-designer runs locally as an npm package, launched with npx -y mcp-schema-designer. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-schema-designer
claude mcp add vpatser1-mcp-schema-designer -- npx -y mcp-schema-designer
{
"mcpServers": {
"vpatser1-mcp-schema-designer": {
"command": "npx",
"args": [
"-y",
"mcp-schema-designer"
]
}
}
} {
"servers": {
"vpatser1-mcp-schema-designer": {
"command": "npx",
"args": [
"-y",
"mcp-schema-designer"
]
}
}
} codex mcp add vpatser1-mcp-schema-designer -- npx -y mcp-schema-designer
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vpatser1-mcp-schema-designer": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-schema-designer"
],
"enabled": true
}
}
} openclaw mcp add vpatser1-mcp-schema-designer --command npx --arg -y --arg mcp-schema-designer
mcp_servers:
vpatser1-mcp-schema-designer:
command: "npx"
args: ["-y", "mcp-schema-designer"] {
"McpServers": {
"vpatser1-mcp-schema-designer": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mcp-schema-designer"
]
}
}
} assistant mcp add vpatser1-mcp-schema-designer -t stdio -c npx -a -y mcp-schema-designer
{
"mcpServers": {
"vpatser1-mcp-schema-designer": {
"command": "npx",
"args": [
"-y",
"mcp-schema-designer"
]
}
}
} 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.
- 24 Sept 26 0
- Stability: 0.97 → pass security
- 23 Sept 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 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 Sept 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.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 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 24 Sept 2026 · Analysed npm/mcp-schema-designer@1.1.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| 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 →
design_schema ~101
Design a database schema from a natural language description. Generates CREATE TABLE SQL (PostgreSQL), index recommendations, and a text-based ERD. Optionally accepts explicit table definitions to validate and enhance.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | Natural language description of the data model (e.g. 'an e-commerce platform with products, orders, and user reviews') |
| tables | array | – | Optional: provide explicit table definitions to validate and enhance instead of generating from description |
No output schema declared.
No examples provided.
generate_types ~89
Generate typed code from SQL CREATE TABLE statements. Supports three output formats: TypeScript interfaces, Zod validation schemas, or JSON Schema definitions.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | yes | Output format: 'typescript' for interfaces, 'zod' for Zod schemas, 'json-schema' for JSON Schema |
| sql | string | yes | SQL CREATE TABLE statements (PostgreSQL dialect) to generate types from |
No output schema declared.
No examples provided.
migrate_schema ~83
Generate migration SQL by diffing a "from" schema against a "to" schema. Produces ALTER TABLE statements in safe dependency order, rollback SQL, and warnings for destructive changes (column drops, type changes).
| Name | Type | Req | Description |
|---|---|---|---|
| from_sql | string | yes | Current database schema as SQL CREATE TABLE statements |
| to_sql | string | yes | Target database schema as SQL CREATE TABLE statements |
No output schema declared.
No examples provided.
optimize_queries ~76
Analyze a SQL query against a schema and suggest performance improvements. Identifies missing indexes, recommends query rewrites, and provides EXPLAIN plan interpretation hints.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The SQL query to optimize |
| schema | string | yes | Schema context as SQL CREATE TABLE statements, so the tool can identify missing indexes and table structure |
No output schema declared.
No examples provided.
validate_schema ~81
Validate SQL CREATE TABLE statements for best practices. Checks for missing primary keys, unnamed constraints, missing FK indexes, data type issues (e.g. TIMESTAMP vs TIMESTAMPTZ), naming conventions (snake_case, plural tables), and N+1 query risks.
| Name | Type | Req | Description |
|---|---|---|---|
| sql | string | yes | SQL CREATE TABLE statements (PostgreSQL dialect) to validate |
No output schema declared.
No examples provided.
What is the io.github.vpatser1/mcp-schema-designer server?
io.github.vpatser1/mcp-schema-designer is listed in the public MCP registry as io.github.vpatser1/mcp-schema-designer. Design database schemas from natural language, validate SQL, generate migrations and types. This page covers its npm package (mcp-schema-designer).
Is the io.github.vpatser1/mcp-schema-designer server safe to use?
io.github.vpatser1/mcp-schema-designer scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. 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 io.github.vpatser1/mcp-schema-designer server expose?
io.github.vpatser1/mcp-schema-designer exposes 5 tools: design_schema, validate_schema, migrate_schema, generate_types, optimize_queries. Their descriptions and schemas cost roughly 430 tokens of context every time the server is loaded.
Is the io.github.vpatser1/mcp-schema-designer server still maintained?
io.github.vpatser1/mcp-schema-designer is still listed as active in the MCP registry. We last reached this channel on 24 September 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 io.github.vpatser1/mcp-schema-designer server under?
io.github.vpatser1/mcp-schema-designer declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.