Method
How the checker works, and what it will not do
It reads a manifest. It reports what the manifest declares against 15 rules. It does not run the server, inspect the package or watch the agent.
What it reads
Four formats: an MCP config JSON (mcpServers or servers), a skills manifest JSON (skills), a SKILL.md with YAML front matter and an instruction body, or the inventory CSV from /kit/. Each entry becomes a record with the fields the rules need: source, publisher, version, transport, filesystem scope, network scope, sandbox, identity, logging, retention, allowed tools, auto-approval and instructions.
The four verdicts
| Verdict | When it is given | What to do |
|---|---|---|
| Not ready to approve | At least one Critical finding | Fix the critical items before anything else |
| Fix before approving | No Critical, at least one High | Fix the highs or record a named, dated acceptance |
| Review before approving | Only Medium and Low findings | Read the finding and decide; the rule is a question, not a verdict |
| No blocking findings | No rule fired | Approve on the manifest, and say what the reading covers |
The same four phrases appear in the banner, the API, the CSV and the approval note. The score is a reading: 100 minus 25 per Critical, 12 per High, 5 per Medium and 2 per Low, never below zero. It is secondary to the verdict and is never shown without the counts.
What a finding carries
The rule id, the severity, the entry it affects, the evidence from the file, why it matters, the fix and the official requirement behind it. A finding without the evidence is not shown; the checker does not assert a problem it cannot point to.
What it never does
- It never runs, installs or contacts anything named in the manifest.
- It never claims a server is safe. A clean report means no rule fired, not that the tool is safe.
- It never scans package source code for vulnerabilities; that is an SCA scanner's job.
- It never enforces a policy, blocks a server or monitors an agent; that is an agent gateway's job.
- It never gives legal advice on the Cyber Resilience Act or any other regime.
- It never sends the pasted text anywhere until the reviewer chooses to save a report.
How to check a line
Every rule cites its source and the official requirement it expresses. The rules page carries all four markets. Where a scheme does not state a requirement, the page says so rather than filling the gap.
What "the official rule behind it" means
It means a requirement we read in the published text and state in our own words, with the clause so a reader can open the official text and compare. It is not a quotation of the instrument, and it is not a certification that the reader meets it.