# io.github.aryanspv/har-forensics-mcp (npm · har-forensics-mcp)

Audit a .har capture: third-party risk, leaked credentials, JWT checks, redaction. No network calls.

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `har-forensics-mcp`: 67/100 (this document), [markdown](https://verifymcp.io/servers/aryanspv-har-forensics-mcp/har-forensics-mcp.md), [page](https://verifymcp.io/servers/aryanspv-har-forensics-mcp/har-forensics-mcp)

## Channel facts

- Registry: `npm`
- Package: `har-forensics-mcp`
- Version: `0.2.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-08-03.

- **Supply Chain Security**: 86/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
- **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**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1304 tokens (~100/item across 13 items; 13 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add aryanspv-har-forensics-mcp -- npx -y har-forensics-mcp
```

### Codex

```bash
codex mcp add aryanspv-har-forensics-mcp -- npx -y har-forensics-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "aryanspv-har-forensics-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "har-forensics-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add aryanspv-har-forensics-mcp --command npx --arg -y --arg har-forensics-mcp
```

### Hermes

```yaml
mcp_servers:
  aryanspv-har-forensics-mcp:
    command: "npx"
    args: ["-y", "har-forensics-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "aryanspv-har-forensics-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "har-forensics-mcp"
      ]
    }
  }
}
```

## 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-08-03 (score 67, +1)

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

### 2026-08-02 (score 66, +45)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [functional regression] Schema quality: 77 → 100
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.03
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] License: unverified → pass
- [functional] First check of Schema quality: unverified
- [functional] Licence: MIT
- [functional] Package version: 0.1.0 → 0.2.0

### 2026-08-01 (score 21)

First indexed and scored.

## MCP tools (13)

### `analyze_har` (~68 tokens)

Analyze a HAR capture

Run every analysis over a .har file and return a triage overview: blast radius, finding counts, and a one-line verdict per check. Start here — then use the focused tools for detail.

Input parameters:

- `path` (string, required): Absolute or relative path to a .har file on this machine.

### `har_brief` (~81 tokens)

Full redacted briefing

The complete audit as markdown, with every secret masked and the analysis's own blind spots stated. This is the safe artifact to quote, paste into a ticket, or reason over.

Input parameters:

- `max_findings` (integer): Cap on findings included. Default 40.
- `path` (string, required): Absolute or relative path to a .har file on this machine.

### `har_findings` (~121 tokens)

Security and privacy findings

Findings raised against the capture — leaked tokens, PII in URLs, insecure cookies, missing headers, expired tokens. Sorted worst-first, details redacted. Returns 25 by default; use severity/offset for the rest.

Input parameters:

- `limit` (integer): Max rows. Default 25.
- `offset` (integer): Skip this many. For paging past the default 25.
- `path` (string, required): Absolute or relative path to a .har file on this machine.
- `severity` (string): Only findings at this severity. Omit for all.

### `har_vendors` (~65 tokens)

Third-party blast radius

Every third party the capture contacted, scored 0–100 by how much damage it could do: request volume, bytes, cookies set, and credentials or PII observed reaching it.

Input parameters:

- `path` (string, required): Absolute or relative path to a .har file on this machine.

### `har_provenance` (~78 tokens)

Who loaded whom

The request dependency graph: which domain caused which other domain to be contacted. Surfaces fourth parties — vendors introduced by your vendors rather than by you. Domains only, no URLs.

Input parameters:

- `limit` (integer): Max rows. Default 60.
- `path` (string, required): Absolute or relative path to a .har file on this machine.

### `har_csp` (~50 tokens)

Generate a Content-Security-Policy

Synthesize a starter CSP from what this capture actually loaded, diffed against the policy the origin sends today.

Input parameters:

- `path` (string, required): Absolute or relative path to a .har file on this machine.

### `har_hunt` (~238 tokens)

Query requests

Search the capture with the Hunt query language. Filters: body, contenttype, duration, encoding, host, is, method, mime, path, priority, protocol, referer, reqbody, respbody, scheme, size, status, time, type, url, or header.<name>. `is:` takes 1p, 3p, cached, failed, firstparty, http, https, redirect, thirdparty. Comparators (status:>=400, size:>500kb, duration:>1s), globs (host:*.doubleclick.net), regex (body:~/sk_live_[a-z0-9]+/), and negation (header.set-cookie:!secure) all work; bare words match the URL. Returns an `#` index — pass it to har_entry or har_curl.

Input parameters:

- `limit` (integer): Max rows. Default 50.
- `path` (string, required): Absolute or relative path to a .har file on this machine.
- `query` (string, required): e.g. "is:thirdparty status:>=400" or "graphql type:xhr"

### `har_entry` (~137 tokens)

Full detail for one request

Everything about a single request by index: status, timing phase breakdown, request and response headers, cookies, query, and body. Redacted. Get the index from har_hunt or har_perf.

Input parameters:

- `include_body` (boolean): Include response body with secret patterns masked, instead of dropping it. Default false. Use when debugging an API response shape.
- `index` (integer, required): Entry index, as shown in the `#` column of har_hunt.
- `max_body_chars` (integer): Body truncation. Default 2000.
- `path` (string, required): Absolute or relative path to a .har file on this machine.

### `har_curl` (~129 tokens)

Replay a request as cURL or fetch()

Generate a runnable cURL command or JavaScript fetch() call for one request, with credentials masked by default. Get the index from har_hunt.

Input parameters:

- `form` (string): Output form. Default curl.
- `index` (integer, required): Entry index, from har_hunt's `#` column.
- `path` (string, required): Absolute or relative path to a .har file on this machine.
- `scrub` (boolean): Mask credential headers and secret patterns. Default true. Setting false emits live credentials in plain text.
- `shell` (string): Quoting style for curl. Default bash.

### `har_perf` (~76 tokens)

Why the page was slow

Performance breakdown: slowest requests with their dominant timing phase, heaviest responses, per-origin connection-setup cost, uncompressed text assets, and latency spent on redirects and failures.

Input parameters:

- `limit` (integer): Max rows. Default 10.
- `path` (string, required): Absolute or relative path to a .har file on this machine.

### `har_diff` (~92 tokens)

Compare two captures

Diff a before and after capture: requests added and removed, responses that got slower or heavier, and third parties that appeared or disappeared. Use for release regressions and 'did this deploy add a tracker'.

Input parameters:

- `after` (string, required): Path to the .har to compare against the baseline.
- `before` (string, required): Path to the baseline .har.
- `limit` (integer): Max rows. Default 20.

### `find_captures` (~74 tokens)

Find .har files on this machine

List .har captures in the working directory, Downloads, Desktop, Documents, and the temp directory, newest first. Use when the user refers to a capture without giving a path.

Input parameters:

- `dir` (string): Search this directory instead of the usual places.
- `limit` (integer): Max rows. Default 20.

### `sanitize_har` (~95 tokens)

Write a redacted copy of a HAR

Mask secrets, tokens, emails, card numbers, and response bodies, then write a `.redacted.har` next to the original. Run this before attaching a capture to a ticket — enterprise DLP now blocks unsanitized HAR uploads outright.

Input parameters:

- `out` (string): Output path. Defaults to <input>.redacted.har.
- `path` (string, required): Absolute or relative path to a .har file on this machine.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/aryanspv-har-forensics-mcp/har-forensics-mcp#diagnostics

## Score history

- 2026-08-03: 67
- 2026-08-02: 66
- 2026-08-01: 21

## Links

- npm package: https://www.npmjs.com/package/har-forensics-mcp
- Socket report: https://socket.dev/npm/package/har-forensics-mcp
- Repository: https://github.com/aryanspv/har-forensics-mcp
- Changelog RSS feed: https://verifymcp.io/servers/aryanspv-har-forensics-mcp/har-forensics-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/aryanspv-har-forensics-mcp/har-forensics-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/aryanspv-har-forensics-mcp/har-forensics-mcp