io.github.CloudCorpRecords/sealtier
NPM · @RENETURCIOS/SEALTIER · 2 COMPONENTS
Local OKF tier check for Markdown folders: scan tiers, trust verdicts and git change reports.
Available components
Last scanned (4 hours ago)
Scores higher than 39% 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 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 286 tokens (~95/item across 3 items; 3 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
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.
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.
- 4 Nov 26 70
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 5 Nov 2026 · Analysed npm/@reneturcios/sealtier@0.1.0
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 →
jidoseal_changes ~95
Report every Markdown file that differs from a git commit (default HEAD, so uncommitted edits and new files): what changed in its frontmatter and body, and what that did to its trust. Reads only; runs the local git with transports disabled.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Path to the folder (a git working tree) to inspect |
| ref | string | – | Git commit to compare against (default HEAD) |
No output schema declared.
No examples provided.
jidoseal_scan ~95
Scan a folder of Markdown files and report its OKF v0.2 frontmatter tier: corpus tier (its weakest file), per-file tier, present fields, and the exact fields missing for each unreached tier, plus coverage per tier, a 0-100 score and a Merkle root of the corpus. Local and read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Path to the folder of Markdown files to scan |
No output schema declared.
No examples provided.
jidoseal_trust ~96
Check one Markdown file, or every Markdown file in a folder, before relying on it: verdict stale, unverified or ok with reasons, from its OKF v0.2 trust and lifecycle fields, plus its trust tier, OKF conformance and which text of v0.2 its timestamps follow. Reads only.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Path to one Markdown file, or to a folder of Markdown files |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/sealtier MCP server?
io.github.CloudCorpRecords/sealtier runs locally as an npm package, launched with npx -y @reneturcios/sealtier. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/sealtier
claude mcp add cloudcorprecords-sealtier -- npx -y @reneturcios/sealtier
What is the io.github.CloudCorpRecords/sealtier MCP server?
io.github.CloudCorpRecords/sealtier is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/sealtier. Local OKF tier check for Markdown folders: scan tiers, trust verdicts and git change reports. This page covers its npm package (@reneturcios/sealtier).
Is the io.github.CloudCorpRecords/sealtier MCP server safe to use?
io.github.CloudCorpRecords/sealtier scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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.CloudCorpRecords/sealtier MCP server expose?
io.github.CloudCorpRecords/sealtier exposes 3 tools: jidoseal_scan, jidoseal_trust, jidoseal_changes. Their descriptions and schemas cost roughly 286 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/sealtier MCP server still maintained?
io.github.CloudCorpRecords/sealtier 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 io.github.CloudCorpRecords/sealtier MCP server under?
io.github.CloudCorpRecords/sealtier declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.