ContextOS — Powered Exoskeleton for AI Coding
OCI · GHCR.IO/YUBINBIN32-OPS/CONTEXTOS
Context exoskeleton for AI development: reduce token usage and context occupancy.
Available components
Last scanned (20 hours ago)
Scores higher than 61% 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 artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency35
- 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
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 8 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability54
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 404 tokens (~404/item across 1 items; 1 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 Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +35
- Injection markers: unverified → pass ▲ security
- Schema quality: 594 → 404 ▲ functional
- Tool coverage: 21% → 100% ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.53 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 13 Oct 26 0
- Package version: 2.7.1 → 3.0.3 functional
- 9 Oct 26 0
- Package version: 3.0.2 → 3.0.3 functional
- 7 Oct 26 −26
- Tool safety: pass → unverified ▼ security
- Stability: 0.17 → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 2.7.1 → 3.0.2 functional
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- Package version: 2.7.0 → 2.7.1 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 16 Oct 2026 · Analysed oci/ghcr.io/yubinbin32-ops/contextos@3.0.3
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 →
contextos ~165
With a known goal, ask({onboard:{goal:"ModuleIndex"}}) returns local overview, trusted graph/owners and verified source; ambiguity is partial, no model fallback. Without a goal use ask({overview:true}). ask({request|inspect}) gets exact source evidence. micro delegates bounded API work; agent delegates implementation to a configured CLI. command runs once; command({action:"get",id}) retrieves. change applies edits/verify. ops({capability,action,args}) exposes state and advanced operations. Put parameters in args; projectRoot absolute.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | micro | ask | command | agent | change |
| args | object | – | Action parameters; advanced operations use capability/action/args. |
| projectRoot | string | yes | Absolute repository root. |
No output schema declared.
No examples provided.
How do I install the ContextOS — Powered Exoskeleton for AI Coding MCP server?
ContextOS — Powered Exoskeleton for AI Coding runs locally as a container image, launched with docker run --rm -i -e CONTEXTOS_PROJECT_ROOT ghcr.io/yubinbin32-ops/contextos:3.0.3. 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/yubinbin32-ops/contextos
claude mcp add yubinbin32-ops-contextos -- docker run --rm -i -e CONTEXTOS_PROJECT_ROOT ghcr.io/yubinbin32-ops/contextos:3.0.3
This image reads CONTEXTOS_PROJECT_ROOT. Set it in your client's env block for this server; docker run -e passes it through to the container.
What is the ContextOS — Powered Exoskeleton for AI Coding MCP server?
ContextOS — Powered Exoskeleton for AI Coding is an MCP server listed in the public MCP registry as io.github.yubinbin32-ops/contextos. Context exoskeleton for AI development: reduce token usage and context occupancy. This page covers its container image (ghcr.io/yubinbin32-ops/contextos).
Is the ContextOS — Powered Exoskeleton for AI Coding MCP server safe to use?
ContextOS — Powered Exoskeleton for AI Coding scores 43 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 ContextOS — Powered Exoskeleton for AI Coding MCP server expose?
ContextOS — Powered Exoskeleton for AI Coding exposes 1 tool: contextos. Their descriptions and schemas cost roughly 165 tokens of context every time the server is loaded.
Is the ContextOS — Powered Exoskeleton for AI Coding MCP server still maintained?
ContextOS — Powered Exoskeleton for AI Coding is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.