# Website Security Audit (npm · @eazetech/website-security-audit-mcp)

Passive security audit of a public website: HTTPS, headers, cookies, TLS, DNS, email, security.txt

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@eazetech/website-security-audit-mcp`: 72/100 (this document), [markdown](https://verifymcp.io/servers/co-eazetech-website-security-audit/eazetech-website-security-audit-mcp.md), [page](https://verifymcp.io/servers/co-eazetech-website-security-audit/eazetech-website-security-audit-mcp)

## Channel facts

- Registry: `npm`
- Package: `@eazetech/website-security-audit-mcp`
- Version: `0.1.1`
- 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-11-21.

- **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.
  - 2 of 23 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 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 544 tokens (~181/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 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 Website Security Audit MCP server?

Website Security Audit runs locally as an npm package, launched with npx -y @eazetech/website-security-audit-mcp. 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 co-eazetech-website-security-audit -- npx -y @eazetech/website-security-audit-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "co-eazetech-website-security-audit": {
      "command": "npx",
      "args": [
        "-y",
        "@eazetech/website-security-audit-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "co-eazetech-website-security-audit": {
      "command": "npx",
      "args": [
        "-y",
        "@eazetech/website-security-audit-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add co-eazetech-website-security-audit -- npx -y @eazetech/website-security-audit-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-eazetech-website-security-audit": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@eazetech/website-security-audit-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-eazetech-website-security-audit --command npx --arg -y --arg @eazetech/website-security-audit-mcp
```

### Hermes

```yaml
mcp_servers:
  co-eazetech-website-security-audit:
    command: "npx"
    args: ["-y", "@eazetech/website-security-audit-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "co-eazetech-website-security-audit": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@eazetech/website-security-audit-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-eazetech-website-security-audit -t stdio -c npx -a -y @eazetech/website-security-audit-mcp
```

### Other

```json
{
  "mcpServers": {
    "co-eazetech-website-security-audit": {
      "command": "npx",
      "args": [
        "-y",
        "@eazetech/website-security-audit-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-11-20 (score 72, +1)

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

### 2026-11-17 (score 71, +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-11-16 (score 70, +15)

- [security improvement] Malware scan: unverified → pass
- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 0.1.0 → 0.1.1

### 2026-11-15 (score 55)

First indexed and scored.

## MCP tools (3)

### `audit_website_security` (~202 tokens)

Audit website security

Runs a passive security audit of a public website and returns a score out of 100, a grade from A+ to F, and findings with a fix for each. Checks HTTPS and redirects, security headers, cookie flags, TLS versions and the certificate, SPF, DMARC, MTA-STS, CAA and name servers, dangling CNAME records, third-party scripts, known-vulnerable JavaScript libraries, mixed content, forms, version disclosure and security.txt. Requests only what the site serves to any visitor. Takes 5 to 40 seconds. Refuses IP addresses, ports other than 80 and 443, and any host that resolves to a private, loopback, link-local, carrier-grade NAT or cloud metadata address.

Input parameters:

- `url` (string, required): Website address to check, such as example.com or https://example.com/. Only http and https on ports 80 and 443. Any query string is removed before the request.

Output parameters:

- `cached` (boolean): True when this result was reused from a scan of the same address in the last minute
- `counts` (object)
- `domain` (string)
- `durationMs` (integer)
- `findings` (array): Sorted from critical to pass
- `grade` (string)
- `notes` (array): Checks that did not finish, were skipped or saw partial data
- `redirects` (array)
- `scannedAt` (string): ISO 8601 time of the scan
- `score` (integer)
- `target` (string): Final address after redirects, without query string

### `check_security_headers` (~151 tokens)

Check security headers

Fetches a public web page, following up to 5 redirects, and reports its HTTPS redirect chain, security response headers and cookie flags, with a fix for each problem. Faster than audit_website_security and gives no grade: it does not check TLS, the certificate, DNS, email records or page content. Refuses IP addresses, ports other than 80 and 443, and any host that resolves to a private, loopback, link-local, carrier-grade NAT or cloud metadata address.

Input parameters:

- `url` (string, required): Website address to check, such as example.com or https://example.com/. Only http and https on ports 80 and 443. Any query string is removed before the request.

Output parameters:

- `cookieCount` (integer): Number of Set-Cookie headers on the final response
- `counts` (object)
- `domain` (string)
- `durationMs` (integer)
- `findings` (array)
- `headers` (object): Values from the final response, cleaned and shortened. A header that is not set is left out.
- `notes` (array): Checks that did not finish, were skipped or saw partial data
- `redirects` (array)
- `scannedAt` (string)
- `target` (string): Final address after redirects, without query string

### `check_security_txt` (~136 tokens)

Check security.txt

Looks for a security.txt file (RFC 9116) at https://<domain>/.well-known/security.txt and then /security.txt, and reports whether one is published, its Contact, Expires, Policy and other fields, and whether it has expired. Redirects are reported but not followed. Refuses IP addresses, ports other than 80 and 443, and any host that resolves to a private, loopback, link-local, carrier-grade NAT or cloud metadata address.

Input parameters:

- `domain` (string, required): Domain to check, such as example.com. A full URL is also accepted; only its host name is used.

Output parameters:

- `checked` (array)
- `contentType` (string)
- `domain` (string)
- `durationMs` (integer)
- `expired` (boolean): Left out when there is no readable Expires date
- `fields` (object): RFC 9116 fields, cleaned and shortened; left out when no file was found
- `findings` (array)
- `found` (boolean)
- `notes` (array): Checks that did not finish, were skipped or saw partial data
- `scannedAt` (string)
- `signed` (boolean): True when the file carries an OpenPGP cleartext signature
- `url` (string): Where the file was found; left out when none was found

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/co-eazetech-website-security-audit/eazetech-website-security-audit-mcp#diagnostics

## Score history

- 2026-11-21: 72
- 2026-11-20: 72
- 2026-11-19: 71
- 2026-11-18: 71
- 2026-11-17: 71
- 2026-11-16: 70
- 2026-11-15: 55

## Common questions

### What is the Website Security Audit MCP server?

Website Security Audit is an MCP server listed in the public MCP registry as co.eazetech/website-security-audit. Passive security audit of a public website: HTTPS, headers, cookies, TLS, DNS, email, security.txt. This page covers its npm package (@eazetech/website-security-audit-mcp).

### Is the Website Security Audit MCP server safe to use?

Website Security Audit scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 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 Website Security Audit MCP server expose?

Website Security Audit exposes 3 tools: audit_website_security, check_security_headers, check_security_txt. Their descriptions and schemas cost roughly 489 tokens of context every time the server is loaded.

### Is the Website Security Audit MCP server still maintained?

Website Security Audit is still listed as active in the MCP registry. We last reached this channel on 21 November 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 Website Security Audit MCP server under?

Website Security Audit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Website Security Audit MCP server?

VerifyMCP ran 16 checks on Website Security Audit, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@eazetech/website-security-audit-mcp
- Socket report: https://socket.dev/npm/package/@eazetech/website-security-audit-mcp
- Repository: https://github.com/eazetech-co/website-security-audit-mcp
- Website: https://eazetech.co/tools/website-security-audit
- Changelog RSS feed: https://verifymcp.io/servers/co-eazetech-website-security-audit/eazetech-website-security-audit-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-eazetech-website-security-audit/eazetech-website-security-audit-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/co-eazetech-website-security-audit/eazetech-website-security-audit-mcp.json
- HTML version of this page: https://verifymcp.io/servers/co-eazetech-website-security-audit/eazetech-website-security-audit-mcp
