# Hares — MCP security scanner (npm · @alihashim313/hares)

Multi-layer security scanner for MCP servers and agent skills (injection, exfiltration)

- Trust score: 76/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- npm · `@alihashim313/hares`: 76/100 (this document), [markdown](https://verifymcp.io/servers/alialrikabi313-hares/alihashim313-hares.md), [page](https://verifymcp.io/servers/alialrikabi313-hares/alihashim313-hares)

## Channel facts

- Registry: `npm`
- Package: `@alihashim313/hares`
- Version: `0.1.0`
- 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-09-25.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 16 of 67 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 45 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1037 tokens (~259/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Hares — MCP security scanner server?

Hares — MCP security scanner runs locally as an npm package, launched with npx -y @alihashim313/hares. 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 alialrikabi313-hares -- npx -y @alihashim313/hares
```

### Cursor

```json
{
  "mcpServers": {
    "alialrikabi313-hares": {
      "command": "npx",
      "args": [
        "-y",
        "@alihashim313/hares"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "alialrikabi313-hares": {
      "command": "npx",
      "args": [
        "-y",
        "@alihashim313/hares"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add alialrikabi313-hares -- npx -y @alihashim313/hares
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add alialrikabi313-hares --command npx --arg -y --arg @alihashim313/hares
```

### Hermes

```yaml
mcp_servers:
  alialrikabi313-hares:
    command: "npx"
    args: ["-y", "@alihashim313/hares"]
```

### Netclaw

```json
{
  "McpServers": {
    "alialrikabi313-hares": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@alihashim313/hares"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add alialrikabi313-hares -t stdio -c npx -a -y @alihashim313/hares
```

### Other

```json
{
  "mcpServers": {
    "alialrikabi313-hares": {
      "command": "npx",
      "args": [
        "-y",
        "@alihashim313/hares"
      ]
    }
  }
}
```

## 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-09-25 (score 76, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 75, −3)

- [functional] Stability: pass → 0.77

### 2026-09-22 (score 78, 0)

- [security] Stability: 0.97 → pass

### 2026-09-21 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 75, −3)

- [functional] Stability: pass → 0.80

### 2026-09-15 (score 78, 0)

- [security] Stability: 0.97 → pass

## MCP tools (4)

### `scan_server` (~360 tokens)

Scan an MCP server for security issues

Run a full security scan of an MCP server or agent skill and return a compact risk summary.

Covers four layers: package structure and metadata, static code analysis with taint tracking, prompt-injection and tool-description poisoning, and — only when `sandbox` is true — behavioral observation inside Docker.

The scanned code is NEVER executed unless `sandbox: true` is passed. Remote targets (`npm:`, `gh:`) are downloaded and read, never installed.

The result is deliberately compact: pass `verbose: true` for every finding with its explanation and fix. Always read `coverage` — a clean result over files that failed to parse is not evidence of safety.

Input parameters:

- `disabled_rules` (array): Rule ids to suppress, e.g. ['HARES-L2-EXEC-001']. Suppressed rules are removed from the result, not downgraded.
- `lang` (string): Language for all human-readable text in the result.
- `max_findings` (integer): Maximum findings to return. The full count is always reported separately.
- `path` (string, required): What to scan: a local directory path, `npm:<package>` (optionally `npm:pkg@version`), or `gh:<owner>/<repo>` (optionally `gh:owner/repo@ref`). Remote targets are downloaded and analyzed statically; n…
- `sandbox` (boolean): Run layer 4, which EXECUTES the scanned server inside a Docker container to observe its behavior. Off by default. Only enable with the user's explicit consent, and only when Docker is available.
- `verbose` (boolean): Return every finding with its full explanation and remediation. Off by default because the compact form is far cheaper in context.

### `quick_check` (~243 tokens)

Fast risk triage of an MCP server

Fast triage of an MCP server: runs layer 1 (structure and metadata) and layer 3 (prompt injection and tool-description poisoning) only, skipping the expensive static-analysis and taint-tracking layer.

Use this to decide whether a full `scan_server` is warranted. A clean quick_check does NOT mean the target is safe — code-level vulnerabilities live in the layer this tier skips, and `layers_skipped` says so in every result.

Input parameters:

- `disabled_rules` (array): Rule ids to suppress, e.g. ['HARES-L2-EXEC-001']. Suppressed rules are removed from the result, not downgraded.
- `lang` (string): Language for all human-readable text in the result.
- `max_findings` (integer): Maximum findings to return. The full count is always reported separately.
- `path` (string, required): What to scan: a local directory path, `npm:<package>` (optionally `npm:pkg@version`), or `gh:<owner>/<repo>` (optionally `gh:owner/repo@ref`). Remote targets are downloaded and analyzed statically; n…

### `diff_versions` (~314 tokens)

Compare two versions of an MCP server for rug-pull changes

Compare two versions of an MCP server and report rug-pull indicators — the classic supply-chain trick where a benign version is installed and trusted, then a later version silently rewrites tool descriptions, schemas or capabilities to carry hidden instructions.

Pass two targets (`old` and `new`) as local paths, `npm:pkg@version`, or `gh:owner/repo@ref`. Both are downloaded and analyzed statically; neither is ever installed or executed.

A change alone is not an attack — legitimate upgrades change descriptions constantly. Only a change *toward* an injection pattern or a privilege escalation is confirmed; a bare wording change stays needs_review. Read `verdict`: `rug_pull` means review before upgrading.

Input parameters:

- `lang` (string): Language for all human-readable text in the result.
- `max_findings` (integer): Maximum findings to return. The full count is always reported separately.
- `new` (string, required): The newer version to compare: a local path, `npm:<package>@<version>`, or `gh:<owner>/<repo>@<ref>`. Downloaded and analyzed statically; never installed or executed.
- `old` (string, required): The older (baseline) version to compare: a local path, `npm:<package>@<version>`, or `gh:<owner>/<repo>@<ref>`. Downloaded and analyzed statically; never installed or executed.
- `verbose` (boolean): Return each difference with its full explanation and remediation. Off by default to save context.

### `explain_finding` (~120 tokens)

Explain a Hares rule in depth

Look up the full catalog entry for a rule id returned by a scan: what it detects, why it is dangerous, how to fix it, its CWE ids, severity, and which layer produced it.

Use this to explain a scan result to the user in depth instead of paraphrasing a one-line title.

Input parameters:

- `lang` (string): Language for all human-readable text in the result.
- `rule_id` (string, required): A rule id exactly as it appears in a scan result, e.g. 'HARES-L2-EXEC-001'.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/alialrikabi313-hares/alihashim313-hares#diagnostics

## Score history

- 2026-09-25: 76
- 2026-09-24: 75
- 2026-09-23: 75
- 2026-09-22: 78
- 2026-09-21: 78
- 2026-09-20: 77
- 2026-09-19: 77
- 2026-09-18: 76
- 2026-09-17: 76
- 2026-09-16: 75
- 2026-09-15: 78
- 2026-09-14: 78
- 2026-09-13: 77
- 2026-09-12: 77
- 2026-09-11: 76
- 2026-09-10: 77
- 2026-09-09: 84
- 2026-09-08: 84
- 2026-09-07: 83
- 2026-09-06: 83
- 2026-09-05: 82
- 2026-09-04: 82
- 2026-09-03: 81
- 2026-09-02: 81
- 2026-09-01: 80
- 2026-08-31: 80
- 2026-08-30: 79
- 2026-08-29: 79
- 2026-08-28: 78
- 2026-08-27: 78

## Common questions

### What is the Hares — MCP security scanner server?

Hares — MCP security scanner is listed in the public MCP registry as io.github.alialrikabi313/hares. Multi-layer security scanner for MCP servers and agent skills (injection, exfiltration). This page covers its npm package (@alihashim313/hares).

### Is the Hares — MCP security scanner server safe to use?

Hares — MCP security scanner scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 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 Hares — MCP security scanner server expose?

Hares — MCP security scanner exposes 4 tools: scan_server, quick_check, diff_versions, explain_finding. Their descriptions and schemas cost roughly 1,037 tokens of context every time the server is loaded.

### Is the Hares — MCP security scanner server still maintained?

Hares — MCP security scanner is still listed as active in the MCP registry. We last reached this channel on 25 September 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 Hares — MCP security scanner server under?

Hares — MCP security scanner 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/@alihashim313/hares
- Socket report: https://socket.dev/npm/package/@alihashim313/hares
- Changelog RSS feed: https://verifymcp.io/servers/alialrikabi313-hares/alihashim313-hares.xml
- Changelog JSON feed: https://verifymcp.io/servers/alialrikabi313-hares/alihashim313-hares.json
- HTML version of this page: https://verifymcp.io/servers/alialrikabi313-hares/alihashim313-hares