Unswell
OCI · GHCR.IO/STOKARO/UNSWELL-MCP:0.1.0-ALPHA.4
Offline self-checking to reduce AI-style wording in source code and documentation.
Available components
Last scanned (10 hours ago)
Scores higher than 93% of OCI 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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this image's dependency list comes from an SBOM its publisher attached, which nothing verifies, so we will not report it as a clean result.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.Unverified
Provenance & Transparency48
- 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 52 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 168 tokens (~84/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 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 current MCP spec version (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.
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 0
- Stability: pass → 0.97 functional
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +7
- Source repository: unverified → pass ▲ security
- Stability: 0.87 → pass security
- 16 Oct 26 −5
- Provenance: pass → unverified ▼ security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 −3
- Stability: pass → 0.80 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 5 Nov 2026 · Analysed oci/ghcr.io/stokaro/unswell-mcp:0.1.0-alpha.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
unswell_check ~46
Check supplied prose or source bytes with the fixed Unswell policy.
| Name | Type | Req | Description |
|---|---|---|---|
| sources | null|array | yes | Between 1 and 256 documents; policy byte and analysis limits also apply. |
| Name | Type | Req | Description |
|---|---|---|---|
| outcome | string | yes | pass, policy_failure, or error. Only pass is a complete successful check. |
| result | object | yes | Engine findings, source coordinates, gate decision, exclusions, and manifest. |
No examples provided.
unswell_describe ~44
Inspect supported formats, checked contexts, rules, and the effective policy.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | – | Optional project-relative filename for policy overrides. Does not open the file. |
| Name | Type | Req | Description |
|---|---|---|---|
| baseline_loaded | boolean | yes | – |
| commit | string | yes | – |
| features | null|array | – | – |
| formats | null|array | yes | – |
| gate_mode | string | yes | – |
| policy | object | yes | – |
| prepared_features | null|array | – | – |
| prepared_kinds | null|array | – | – |
| rules | null|array | yes | – |
| version | string | yes | – |
No examples provided.
How do I install the Unswell MCP server?
Unswell runs locally as a container image, launched with docker run --rm -i ghcr.io/stokaro/unswell-mcp:0.1.0-alpha.4. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/stokaro/unswell-mcp:0.1.0-alpha.4
claude mcp add stokaro-unswell -- docker run --rm -i ghcr.io/stokaro/unswell-mcp:0.1.0-alpha.4
What is the Unswell MCP server?
Unswell is an MCP server listed in the public MCP registry as io.github.stokaro/unswell. Offline self-checking to reduce AI-style wording in source code and documentation. This page covers its container image (ghcr.io/stokaro/unswell-mcp:0.1.0-alpha.4).
Is the Unswell MCP server safe to use?
Unswell scores 55 out of 100 on VerifyMCP. 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 Unswell MCP server expose?
Unswell exposes 2 tools: unswell_check, unswell_describe. Their descriptions and schemas cost roughly 90 tokens of context every time the server is loaded.
Is the Unswell MCP server still maintained?
Unswell 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 Unswell MCP server under?
Unswell declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.