io.github.sebastienrousseau/noyalib-mcp
OCI · GHCR.IO/SEBASTIENROUSSEAU/NOYALIB-MCP
MCP server for lossless YAML 1.2 parsing, formatting, and validation (pure Rust).
Available components
Last scanned (7 hours ago)
Scores higher than 99% 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 & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to sebastienrousseau/noyalib-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT OR Apache-2.0).Pass
- Actively maintained (last published 19 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 944 tokens (~118/item across 8 items; 6 tools + 2 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 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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.
- 4 Nov 26 +1
- Security disclosure: unverified → pass ▲ functional
- 3 Nov 26 0
- Stability: 0.97 → pass security
- Security disclosure: pass → unverified ▼ functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 21 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.
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/sebastienrousseau/noyalib-mcp@0.0.58
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | oci |
| Reason | Verified |
| Discovered via | OCI referrers API |
| Source repo | sebastienrousseau/noyalib-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/sebastienrousseau/noyalib-mcp/.github/workflows/release.yml@refs/tags/v0.0.58 |
| Rekor log index | 3279524554 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha256:f72228f5f269bf73086b635adae244a9efc6affdee0c43aede5966e724306387 |
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 →
noyalib_edit Edit a value in YAML text, losslessly (stateless) ~121
Set the value at a dotted/indexed path in the YAML text given in the request and return the whole edited text. Only the touched span changes; every comment, blank line and quote style elsewhere is preserved byte-for-byte. Nothing on disk is touched: the caller decides where the result goes.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Dotted/indexed path, e.g. `server.port` or `items[0].name`. |
| value | string | yes | Replacement value as a YAML fragment. |
| yaml | string | yes | The YAML text to edit. |
| Name | Type | Req | Description |
|---|---|---|---|
| yaml | string | yes | The whole YAML text with the one value replaced. |
No examples provided.
noyalib_get Read a YAML value (lossless) ~116
Read the YAML value at a dotted/indexed path in the given file and return the source slice exactly — no re-quoting, no canonicalisation, comments and formatting preserved. Use this to inspect a value before changing it; use `noyalib_set` to write a value back losslessly.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | Path to the YAML file on disk. |
| path | string | yes | Dotted/indexed path into the YAML, e.g. `server.host` or `items[0].name`. |
| Name | Type | Req | Description |
|---|---|---|---|
| value | string | yes | The source slice at the path, exactly as written: no re-quoting, no canonicalisation. Empty for a key with no value. |
No examples provided.
noyalib_parse Parse YAML text into JSON (stateless) ~105
Parse the YAML text given in the request and return its JSON data model (custom tags stripped, the projection the official YAML test suite expects). Multi-document streams return a JSON array with one element per document. Refuses hostile input (nesting, alias expansion, size) and duplicate keys under the strict YAML 1.2 profile, the same rules as the library. Nothing is read from or written to disk.
| Name | Type | Req | Description |
|---|---|---|---|
| yaml | string | yes | The YAML text to parse. |
| Name | Type | Req | Description |
|---|---|---|---|
| documents | array | yes | One JSON value per document of the stream, custom tags stripped. A single-document text gives one element. |
No examples provided.
noyalib_set Write a YAML value (lossless) ~173
Set the YAML value at a dotted/indexed path in the given file, rewriting only the touched span so every comment, blank line, and sibling entry is preserved byte-for-byte (written atomically). Use this for Renovate-style version bumps and config patches; use `noyalib_get` first when you need to read the current value. On a parse error the document is left unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | Path to the YAML file on disk. |
| path | string | yes | Dotted/indexed path into the YAML. |
| value | string | yes | Replacement value as a YAML fragment (e.g. `0.0.2`, `"hello"`, `[1, 2, 3]`). Must parse in the target position; the document is left unchanged on parse error. |
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | The file that was rewritten. |
| path | string | yes | The path that was set. |
| value | string | yes | The YAML fragment now at that path. |
No examples provided.
noyalib_set_multidoc Write a YAML value in one document of a multi-doc stream (lossless) ~195
Set the YAML value at a dotted/indexed path within a single document of a multi-document (`---`-separated) YAML stream, selected by zero-based document index. Only the touched span of that one document is rewritten; every other document, comment, blank line and separator is preserved byte-for-byte (written atomically). Use `noyalib_set` for a single-document file. On a parse error or out-of-range index the file is left unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| doc_index | integer | yes | Zero-based index of the document within the `---`-separated stream to modify. |
| file | string | yes | Path to the multi-document YAML file on disk. |
| path | string | yes | Dotted/indexed path into the selected document. |
| value | string | yes | Replacement value as a YAML fragment. Must parse in the target position; the file is left unchanged on parse error. |
| Name | Type | Req | Description |
|---|---|---|---|
| doc_index | integer | yes | The zero-based index of the document that changed. |
| file | string | yes | The file that was rewritten. |
| path | string | yes | The path that was set, within that document. |
| value | string | yes | The YAML fragment now at that path. |
No examples provided.
noyalib_validate Validate YAML text, optionally against a JSON Schema (stateless) ~107
Check that the YAML text parses under the library's limits, and when a JSON Schema (as JSON text) is given, that the document satisfies it. Returns `valid` with an empty list, or the parse error with its line and column, or every schema violation with its RFC 6901 path. Nothing on disk is touched.
| Name | Type | Req | Description |
|---|---|---|---|
| schema | string|null | – | A JSON Schema, as JSON text (optional). |
| yaml | string | yes | The YAML text to validate. |
| Name | Type | Req | Description |
|---|---|---|---|
| column | integer|null | – | The column of the parse error, when there is one. |
| error | string|null | – | The parse error, when the text does not parse. |
| line | integer|null | – | The line of the parse error, when there is one. |
| valid | boolean | yes | Whether the text parses and, when a schema was given, satisfies it. |
| violations | array | yes | Every schema violation; empty when the document is valid or no schema was given. |
No examples provided.
How do I install the io.github.sebastienrousseau/noyalib-mcp server?
io.github.sebastienrousseau/noyalib-mcp runs locally as a container image, launched with docker run --rm -i ghcr.io/sebastienrousseau/noyalib-mcp:0.0.58. 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/sebastienrousseau/noyalib-mcp
claude mcp add sebastienrousseau-noyalib-mcp -- docker run --rm -i ghcr.io/sebastienrousseau/noyalib-mcp:0.0.58
What is the io.github.sebastienrousseau/noyalib-mcp server?
io.github.sebastienrousseau/noyalib-mcp is listed in the public MCP registry as io.github.sebastienrousseau/noyalib-mcp. MCP server for lossless YAML 1.2 parsing, formatting, and validation (pure Rust). This page covers its container image (ghcr.io/sebastienrousseau/noyalib-mcp).
Is the io.github.sebastienrousseau/noyalib-mcp server safe to use?
io.github.sebastienrousseau/noyalib-mcp scores 68 out of 100 on VerifyMCP. Its build provenance is signed and verified. 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.sebastienrousseau/noyalib-mcp server expose?
io.github.sebastienrousseau/noyalib-mcp exposes 6 tools: noyalib_edit, noyalib_get, noyalib_parse, noyalib_set, noyalib_set_multidoc, noyalib_validate. Their descriptions and schemas cost roughly 817 tokens of context every time the server is loaded.
Is the io.github.sebastienrousseau/noyalib-mcp server still maintained?
io.github.sebastienrousseau/noyalib-mcp 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.sebastienrousseau/noyalib-mcp server under?
io.github.sebastienrousseau/noyalib-mcp declares the MIT OR Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.