# JidoSeal (pypi · jidoseal-mcp)

Local Self-Check of a Markdown folder: OKF tier and ISO-evidence gaps. Scans stay on your machine.

- Trust score: 50/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- pypi · `jidoseal-mcp`: 50/100 (this document), [markdown](https://verifymcp.io/servers/com-jidoseal-jidoseal-mcp/jidoseal-mcp.md), [page](https://verifymcp.io/servers/com-jidoseal-jidoseal-mcp/jidoseal-mcp)

## Channel facts

- Registry: `pypi`
- Package: `jidoseal-mcp`
- Version: `0.1.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-28.

- **Supply Chain Security**: 48/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it.
  - 1 of 2 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Build provenance not yet verified.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 916 tokens (~305/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 78% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

**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.

## Install

### How do I install the JidoSeal MCP server?

JidoSeal runs locally as a PyPI package, launched with uvx jidoseal-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add com-jidoseal-jidoseal-mcp -- uvx jidoseal-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-jidoseal-jidoseal-mcp": {
      "command": "uvx",
      "args": [
        "jidoseal-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-jidoseal-jidoseal-mcp": {
      "command": "uvx",
      "args": [
        "jidoseal-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-jidoseal-jidoseal-mcp -- uvx jidoseal-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-jidoseal-jidoseal-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "jidoseal-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-jidoseal-jidoseal-mcp --command uvx --arg jidoseal-mcp
```

### Hermes

```yaml
mcp_servers:
  com-jidoseal-jidoseal-mcp:
    command: "uvx"
    args: ["jidoseal-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-jidoseal-jidoseal-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "jidoseal-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-jidoseal-jidoseal-mcp -t stdio -c uvx -a jidoseal-mcp
```

### Other

```json
{
  "mcpServers": {
    "com-jidoseal-jidoseal-mcp": {
      "command": "uvx",
      "args": [
        "jidoseal-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 50, −15)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 65, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 63, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-23 (score 48)

First indexed and scored.

## MCP tools (3)

### `jidoseal_scan` (~351 tokens)

JidoSeal Self-Check (free, local)

Run JidoSeal's free Self-Check over a folder of Markdown documents on THIS machine and return its JidoSeal certification tier — Bronze, Silver or Gold — plus, for every file, which fields are missing for the next tier, and the corpus's coverage against each tier. Same rubric, and the same tier, coverage and per-file gap list as the Self-Check at jidoseal.com/app/run for the same folder. Bronze = OKF v0.2 as written (a populated `type`); Silver = Bronze + fields that evidence ISO 9001 §7.5.2 (title, description, timestamp, owner); Gold = Silver + fields that evidence ISO 30401 (status, review_policy, reviewed_at, next_review_at). ISO names no fields; these are JidoSeal's way of meeting the clauses. Each gap is marked AUTO (JidoSeal can propose the value) or NEEDS-CLIENT (only the owner can answer it), so the caller can close them for free before paying for anything. Free and unlimited. Exactly what leaves your machine: nothing — 100% local, zero content egress. Your files, their names, and their contents never leave your device. Writes the scan's own records to <root>/.jidoseal/ (manifest.json and an appended progress.ndjson) and nowhere else.

Input parameters:

- `include_machine` (boolean): Scan every Markdown file, ignoring this corpus's own machine/transient excludes from .jidoseal/config.yaml. Leave false: the certified path scans without it.
- `root` (string, required): Absolute path of the folder to scan. Every *.md file under it is scanned, recursively.

### `jidoseal_certification_offer` (~168 tokens)

What JidoSeal certification would cost for this corpus

Scan a folder locally and return the paid-certification offer for it: the tier it qualifies for, the real price for that tier and why that price applies, what the certificate includes (a dated certificate bound to a Merkle root of the corpus, a verifiable badge, a public verification page, a registry listing), and the exact list of facts a purchase would send to jidoseal.com. Charges nothing, starts nothing, and sends nothing — it is a local computation about a purchase the customer has not made. Exactly what leaves your machine: nothing — 100% local, zero content egress. Your files, their names, and their contents never leave your device.

Input parameters:

- `include_machine` (boolean)
- `root` (string, required): Absolute path of the folder.

### `jidoseal_start_checkout` (~260 tokens)

Start the JidoSeal certification purchase (returns a Stripe Checkout link)

Ask jidoseal.com to create a Stripe Checkout session for certifying this corpus, and return the checkout URL for the customer to open and pay. Call it only with the customer's explicit go-ahead: it is the purchase step. It does NOT take a payment — this server never sees a card, Stripe hosts the checkout, and nothing is charged or issued unless the customer completes it themselves. This is the one JidoSeal tool that contacts the network, and it sends only: company, name and email as typed by the customer, the tier, a 0-100 score, the corpus's Merkle root, the local scan's id, and which Bronze price applies. No file contents, no file names, no per-file hashes, no paths. The tier, score and Merkle root are taken from a fresh local scan run here — never from the caller.

Input parameters:

- `company` (string, required): The customer's company name, as it should appear on the certificate.
- `include_machine` (boolean)
- `root` (string, required): Absolute path of the folder to certify.
- `submitter_email` (string, required): Where the certificate and receipt go.
- `submitter_name` (string, required): The person submitting, as typed by them.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-jidoseal-jidoseal-mcp/jidoseal-mcp#diagnostics

## Score history

- 2026-09-28: 50
- 2026-09-27: 65
- 2026-09-26: 65
- 2026-09-25: 65
- 2026-09-24: 63
- 2026-09-23: 48

## Common questions

### What is the JidoSeal MCP server?

JidoSeal is an MCP server listed in the public MCP registry as com.jidoseal/jidoseal-mcp. Local Self-Check of a Markdown folder: OKF tier and ISO-evidence gaps. Scans stay on your machine. This page covers its PyPI package (jidoseal-mcp).

### Is the JidoSeal MCP server safe to use?

JidoSeal scores 50 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 28 September 2026. 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 JidoSeal MCP server expose?

JidoSeal exposes 3 tools: jidoseal_scan, jidoseal_certification_offer, jidoseal_start_checkout. Their descriptions and schemas cost roughly 779 tokens of context every time the server is loaded.

### Is the JidoSeal MCP server still maintained?

JidoSeal is still listed as active in the MCP registry. We last reached this channel on 28 September 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 JidoSeal MCP server under?

JidoSeal declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/jidoseal-mcp/
- Socket report: https://socket.dev/pypi/package/jidoseal-mcp
- Repository: https://github.com/Jidoseal/jidoseal-mcp
- Website: https://jidoseal.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-jidoseal-jidoseal-mcp/jidoseal-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-jidoseal-jidoseal-mcp/jidoseal-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-jidoseal-jidoseal-mcp/jidoseal-mcp