SchemaSure — structured extraction
NPM · @NOAMJOSE/SCHEMASURE · SCANNED AUG 7
Extract schema-valid JSON from text/HTML or document images. Pay per call via x402 V2.
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. 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 6 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability52
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 426 tokens (~213/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 57% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 · @noamjose/schemasure
claude mcp add noamjose-schemasure -- npx -y @noamjose/schemasure
codex mcp add noamjose-schemasure -- npx -y @noamjose/schemasure
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"noamjose-schemasure": {
"type": "local",
"command": [
"npx",
"-y",
"@noamjose/schemasure"
],
"enabled": true
}
}
} openclaw mcp add noamjose-schemasure --command npx --arg -y --arg @noamjose/schemasure
mcp_servers:
noamjose-schemasure:
command: "npx"
args: ["-y", "@noamjose/schemasure"] {
"mcpServers": {
"noamjose-schemasure": {
"command": "npx",
"args": [
"-y",
"@noamjose/schemasure"
]
}
}
} 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 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +22
- Malware scan: unverified → pass ▲ security
- Schema quality: unverified → fair ▲ functional
- 1 Aug 26 +20
- Tool coverage: 75% → 57% ▼ functional
- Schema quality: good → unverified ▼ functional
- Schema quality: 283 → 213 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.17 ▲ functional
- 31 Jul 26 −50
- Malware scan: pass → unverified ▼ security
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 +28
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 75 functional
- 26 Jul 26 41
First indexed and scored.
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 7 Aug 2026 · Analysed npm/@noamjose/[email protected]
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
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.
extract_image_to_schema ~143
Extract readable fields from a PNG, JPEG, or WebP invoice, receipt, form, screenshot, label, or photographed document into guaranteed schema-valid JSON. This hosted service is V2-only and always paid from the first call; there is no free or V1 image endpoint. A locally configured SCHEMASURE_PRIVATE_KEY signs x402 V2 USDC payments on Base mainnet and never leaves this process. Add per-field schema descriptions for best accuracy.
| Name | Type | Req | Description |
|---|---|---|---|
| image | object | yes | – |
| options | object | – | – |
| schema | object | yes | JSON Schema (draft 2020-12) that the returned `data` is guaranteed to satisfy. |
No output schema declared.
No examples provided.
extract_to_schema ~283
Turn messy text/HTML into guaranteed schema-valid JSON. Output is guaranteed to validate against your JSON Schema (Ajv, draft 2020-12) or you get a typed error and are not charged (charge-only-on-success). Evaluation mode: calls the legacy V1 endpoint with a small free allowance (no wallet configured). Set SCHEMASURE_PRIVATE_KEY to enable paid production calls via x402 V2. Benchmarked 100% schema-valid with ~0.99 field F1 and zero hallucinations across a 10-doc-type corpus (11 items, incl. an adversarial prompt-injection tier), p50 latency ~1.5s. Evidence: /.well-known/benchmarks.json. Use whenever you need unstructured text/HTML turned into JSON matching a specific shape — invoices, receipts, resumes, product/HTML pages, logs, or anything you can describe as a schema. Tip: add a per-field description to your schema for best accuracy.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | Raw unstructured content to extract from (plain text or HTML). |
| inputType | string | – | How to interpret `input`: plain text, HTML, or auto-detect (default). |
| options | object | – | – |
| schema | object | yes | JSON Schema (draft 2020-12) that the returned `data` is guaranteed to satisfy. |
No output schema declared.
No examples provided.