io.github.rog0x/schema
NPM · @ROG0X/MCP-SCHEMA-TOOLS
JSON Schema, TypeScript types, mocks for AI agents
Available components
Last scanned (6 hours ago)
Scores higher than 84% of npm servers
Category Developer Tools
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
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 228 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 487 tokens (~97/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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 5 Nov 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.
- 4 Nov 26 −1
- Stability: pass → 0.93 functional
- 29 Oct 26 0
- Stability: 0.97 → pass security
- 28 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.
- 27 Oct 26 −1
- Stability: pass → 0.93 functional
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
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 6 Nov 2026 · Analysed npm/@rog0x/mcp-schema-tools@1.0.1
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 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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 →
diff_schemas ~83
Compare two JSON Schemas and identify all differences: added/removed/changed fields, type changes, constraint changes (min/max, patterns, enums). Classifies each change as breaking or non-breaking for backwards compatibility analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| new_schema | object | yes | The updated (new) JSON Schema |
| old_schema | object | yes | The original (old) JSON Schema |
No output schema declared.
No examples provided.
generate_json_schema ~113
Generate a JSON Schema from one or more sample JSON values. Infers types, required fields, formats (email, date, URI, UUID), and detects enum patterns from multiple examples.
| Name | Type | Req | Description |
|---|---|---|---|
| detect_enums | boolean | – | Whether to detect enum values from string fields across samples (default: true, requires >= 3 samples) |
| samples | array | yes | Array of sample JSON values to infer the schema from. More samples produce a more accurate schema. |
| title | string | – | Optional title for the generated schema |
No output schema declared.
No examples provided.
generate_typescript ~104
Generate TypeScript interfaces and types from JSON data or a JSON Schema. Handles nested objects, arrays, optional fields, enums, union types, and Record types.
| Name | Type | Req | Description |
|---|---|---|---|
| json | – | – | Sample JSON data to convert to TypeScript types. Provide either this or 'schema'. |
| root_name | string | – | Name for the root interface/type (default: 'Root') |
| schema | object | – | A JSON Schema to convert to TypeScript types. Provide either this or 'json'. |
No output schema declared.
No examples provided.
mock_from_schema ~119
Generate realistic mock data from a JSON Schema. Uses smart field-name detection to produce contextual values: email fields get valid emails, name fields get realistic names, dates get ISO strings, etc. Supports all JSON Schema types and constraints.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Number of mock objects to generate (default: 1). If > 1, returns an array. |
| schema | object | yes | The JSON Schema to generate mock data from |
| seed | number | – | Random seed for reproducible output. Same seed + same schema = same data. |
No output schema declared.
No examples provided.
validate_schema ~68
Validate data against a JSON Schema. Returns detailed error messages with JSON path, expected type, actual value, and the violated keyword (type, required, format, pattern, minimum, etc.).
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | The data to validate |
| schema | object | yes | The JSON Schema to validate against |
No output schema declared.
No examples provided.
How do I install the io.github.rog0x/schema MCP server?
io.github.rog0x/schema runs locally as an npm package, launched with npx -y @rog0x/mcp-schema-tools. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @rog0x/mcp-schema-tools
claude mcp add rog0x-schema -- npx -y @rog0x/mcp-schema-tools
What is the io.github.rog0x/schema MCP server?
io.github.rog0x/schema is an MCP server listed in the public MCP registry as io.github.rog0x/schema. JSON Schema, TypeScript types, mocks for AI agents. This page covers its npm package (@rog0x/mcp-schema-tools).
Is the io.github.rog0x/schema MCP server safe to use?
io.github.rog0x/schema scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 November 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.rog0x/schema MCP server expose?
io.github.rog0x/schema exposes 5 tools: generate_json_schema, generate_typescript, validate_schema, mock_from_schema, diff_schemas. Their descriptions and schemas cost roughly 487 tokens of context every time the server is loaded.
Is the io.github.rog0x/schema MCP server still maintained?
io.github.rog0x/schema is still listed as active in the MCP registry. We last reached this channel on 6 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 io.github.rog0x/schema MCP server under?
io.github.rog0x/schema declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.rog0x/schema MCP server?
VerifyMCP ran 15 checks on io.github.rog0x/schema, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.rog0x/schema: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.