# io.github.CloudCorpRecords/hookcheck (npm · @reneturcios/hookcheck)

Persistence hook auditor: scan repos for auto-exec hooks, flag Shai-Hulud patterns.

- Trust score: 56/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- npm · `@reneturcios/hookcheck`: 56/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-hookcheck/reneturcios-hookcheck.md), [page](https://verifymcp.io/servers/cloudcorprecords-hookcheck/reneturcios-hookcheck)
- oci · `ghcr.io/cloudcorprecords/hookcheck`: 41/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-hookcheck/ghcr-io-cloudcorprecords-hookcheck.md), [page](https://verifymcp.io/servers/cloudcorprecords-hookcheck/ghcr-io-cloudcorprecords-hookcheck)

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/hookcheck`
- Version: `0.1.17`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Supply Chain Security**: 48/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 226 tokens (~113/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.CloudCorpRecords/hookcheck MCP server?

io.github.CloudCorpRecords/hookcheck runs locally as an npm package, launched with npx -y @reneturcios/hookcheck. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-hookcheck -- npx -y @reneturcios/hookcheck
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-hookcheck": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/hookcheck"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-hookcheck": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/hookcheck"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-hookcheck -- npx -y @reneturcios/hookcheck
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-hookcheck": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@reneturcios/hookcheck"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloudcorprecords-hookcheck --command npx --arg -y --arg @reneturcios/hookcheck
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-hookcheck:
    command: "npx"
    args: ["-y", "@reneturcios/hookcheck"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-hookcheck": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@reneturcios/hookcheck"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloudcorprecords-hookcheck -t stdio -c npx -a -y @reneturcios/hookcheck
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-hookcheck": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/hookcheck"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-23 (score 56, −4)

- [security regression] Malware scan: pass → unverified
- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.85
- [functional] Package version: 0.1.16 → 0.1.17

### 2026-10-22 (score 60)

First indexed and scored.

## MCP tools (2)

### `scan_hooks` (~126 tokens)

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.

Input parameters:

- `path` (string, required): Local directory to scan, e.g. /home/user/project

### `explain_hook` (~100 tokens)

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.

Input parameters:

- `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, required): Local directory to scan

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-hookcheck/reneturcios-hookcheck#diagnostics

## Score history

- 2026-10-23: 56
- 2026-10-22: 60

## Common questions

### 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 npm package (@reneturcios/hookcheck).

### Is the io.github.CloudCorpRecords/hookcheck MCP server safe to use?

io.github.CloudCorpRecords/hookcheck scores 56 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. It declares no install or post-install scripts. 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.

## Links

- npm package: https://www.npmjs.com/package/@reneturcios/hookcheck
- Socket report: https://socket.dev/npm/package/@reneturcios/hookcheck
- Repository: https://github.com/CloudCorpRecords/hookcheck
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-hookcheck/reneturcios-hookcheck.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-hookcheck/reneturcios-hookcheck.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-hookcheck/reneturcios-hookcheck