io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 7, 2026
Local OKF tier check for Markdown folders: scan tiers, trust verdicts and git change reports.
Local, read-only MCP server that grades Markdown folders against OKF v0.2 frontmatter tiers and reports trust verdicts and git-driven trust changes.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Follow the launch instructions in the repository.
sealtier checks a folder of Markdown files against the Open Knowledge Format (OKF) v0.2 frontmatter tiers — Bronze, Silver, Gold — entirely on your own machine. It tells you which tier a knowledge base reaches, exactly which frontmatter fields each file is missing for the next tier, whether a document can still be trusted, and what a git edit did to that trust. It reads only: a scan writes nothing anywhere, and no tool in this package makes a network call.
It is a clean-room rebuild of the jidoseal-mcp server's three local
tools. The original's two remaining tools are not rebuilt: one creates
a paid Stripe Checkout session (a payment funnel), and the other's
decisive output is a price that is published only on the vendor's
website, so it cannot be reproduced from the public record.
A field counts only if it has real content — title: with nothing
after it earns nothing.
A corpus's tier is the tier of its weakest file. Coverage is the
share of files reaching each tier. Each missing field is marked AUTO
(a value the tool can propose) or NEEDS-CLIENT (only the owner can
answer). The 0–100 score is round(mean of the three coverage values) — a reconstruction, disclosed as such: the original publishes
a worked value (44 for coverage 66.7 / 33.3 / 33.3) but no formula,
and this formula reproduces it. The Merkle root is the hex sha256 of
the concatenated per-file sha256 hex digests, files ordered by name —
also a disclosed reconstruction.
A note on egress: the original vendor claims its scan engine sends
nothing over the network. That is the vendor's own claim about its
proprietary engine, not independently audited. This rebuild is
simpler to reason about: it imports no HTTP client and opens no
socket, and jidoseal_changes starts exactly one program — the local
git, with transports disabled (protocol.allow=never,
GIT_NO_LAZY_FETCH=1).
One recorded deviation: the original also writes
.jidoseal/manifest.json and .jidoseal/progress.ndjson under the
scanned folder. This rebuild is read-only and writes nothing.
Or run the container image:
The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.
Each command takes its arguments as one JSON object and prints the JSON result.
Exit codes: 0 on success, 1 when a tool cannot complete (the
error names the problem — a missing folder, a failed git status),
2 for usage errors.
One bin serves both faces. The mcp subcommand starts a stdio MCP
server:
MCP client configuration:
Frontmatter parsing is a small hand-rolled YAML subset (flat
key: value pairs, quoted strings, inline lists/maps, one level of
indented block maps and lists). A frontmatter block outside that
subset is reported per file as frontmatter_ok: false; such a file
reaches no tier and no field counts until it is fixed by hand.
MIT — see LICENSE.
Source: README.md at commit 24bdc55
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.
pathrequiredCheck 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.
pathrequiredReport 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.
refpathrequired90% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
npx @reneturcios/sealtier jidoseal_scan '{"path":"/path/to/notes"}'docker run -i ghcr.io/cloudcorprecords/sealtier# Tier a folder of Markdown filessealtier jidoseal_scan '{"path":"~/notes"}'
# Trust verdict for one file, or every *.md in a foldersealtier jidoseal_trust '{"path":"~/notes/policies/leave.md"}'
# What changed since HEAD, and what it did to trustsealtier jidoseal_changes '{"path":"~/notes"}'sealtier jidoseal_changes '{"path":"~/notes","ref":"v1.2"}'
sealtier --versionnpx -y @reneturcios/sealtier mcp{ "mcpServers": { "sealtier": { "command": "npx", "args": ["-y", "@reneturcios/sealtier", "mcp"] } }}npm installnpm run build # tsc -> dist/npm test # node test runner over test/*.test.ts, no network, fake git executornpm run dev # run the CLI from source via tsx