io.github.rog0x/schema
NPM · @ROG0X/MCP-SCHEMA-TOOLS · SCANNED AUG 3
JSON Schema, TypeScript types, mocks for AI agents
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 →
Supply Chain Security86
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. 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 133 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @rog0x/mcp-schema-tools
claude mcp add rog0x-schema -- npx -y @rog0x/mcp-schema-tools
codex mcp add rog0x-schema -- npx -y @rog0x/mcp-schema-tools
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rog0x-schema": {
"type": "local",
"command": [
"npx",
"-y",
"@rog0x/mcp-schema-tools"
],
"enabled": true
}
}
} openclaw mcp add rog0x-schema --command npx --arg -y --arg @rog0x/mcp-schema-tools
mcp_servers:
rog0x-schema:
command: "npx"
args: ["-y", "@rog0x/mcp-schema-tools"] {
"mcpServers": {
"rog0x-schema": {
"command": "npx",
"args": [
"-y",
"@rog0x/mcp-schema-tools"
]
}
}
} 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.
- 2 Aug 26 +29
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Licence: MIT functional
- 1 Aug 26 +15
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- 31 Jul 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 46
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@rog0x/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.