io.github.CloudCorpRecords/hookcheck
OCI · GHCR.IO/CLOUDCORPRECORDS/HOOKCHECK · 2 COMPONENTS
Persistence hook auditor: scan repos for auto-exec hooks, flag Shai-Hulud patterns.
Available components
Last scanned (1 hour ago)
Scores higher than 53% of OCI servers
Category Security
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 & Transparency45
- 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 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 226 tokens (~113/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 Management3
- Stability observed for 1 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 2 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.
- 23 Oct 26 0
- Package version: 0.1.3 → 0.1.17 functional
- 22 Oct 26 41
First indexed and scored.
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 23 Oct 2026 · Analysed oci/ghcr.io/cloudcorprecords/hookcheck@0.1.17
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 →
explain_hook ~100
Explain one hook found by scan_hooks: its command, classification, rules that fired, and what the classification means. Pass the hook id (e.g. package.json:postinstall) or its file path.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | – | File path of the hook as an alternative selector |
| hookId | string | – | Hook id from a scan report, e.g. package.json:postinstall |
| path | string | yes | Local directory to scan |
No output schema declared.
No examples provided.
scan_hooks ~126
Scan a local repo directory for auto-exec hooks: npm install scripts, Claude Code settings hooks, VS Code folderOpen tasks, husky, lefthook, pre-commit, Cursor and Codex configs, MCP autostart configs, and GitHub workflow run steps. Classifies each hook SAFE, RISKY, or UNKNOWN and returns a CLEAN, REVIEW, or COMPROMISED-PATTERN verdict with evidence per finding. Deterministic, local only, no network.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Local directory to scan, e.g. /home/user/project |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/hookcheck MCP server?
io.github.CloudCorpRecords/hookcheck runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/hookcheck:0.1.17. 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/cloudcorprecords/hookcheck
claude mcp add cloudcorprecords-hookcheck -- docker run --rm -i ghcr.io/cloudcorprecords/hookcheck:0.1.17
What is the io.github.CloudCorpRecords/hookcheck MCP server?
io.github.CloudCorpRecords/hookcheck is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/hookcheck. Persistence hook auditor: scan repos for auto-exec hooks, flag Shai-Hulud patterns. This page covers its container image (ghcr.io/cloudcorprecords/hookcheck).
Is the io.github.CloudCorpRecords/hookcheck MCP server safe to use?
io.github.CloudCorpRecords/hookcheck scores 41 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 io.github.CloudCorpRecords/hookcheck MCP server expose?
io.github.CloudCorpRecords/hookcheck exposes 2 tools: scan_hooks, explain_hook. Their descriptions and schemas cost roughly 226 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/hookcheck MCP server still maintained?
io.github.CloudCorpRecords/hookcheck is still listed as active in the MCP registry. We last reached this channel on 23 October 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.CloudCorpRecords/hookcheck MCP server under?
io.github.CloudCorpRecords/hookcheck declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.