Website Security Audit
NPM · @EAZETECH/WEBSITE-SECURITY-AUDIT-MCP
Passive security audit of a public website: HTTPS, headers, cookies, TLS, DNS, email, security.txt
Available components
Last scanned (17 hours ago)
Scores higher than 44% of npm 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 Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 2 of 23 dependencies flagged as unhealthy. View diagnostics → Partial
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 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +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.
- 17 Nov 26 +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.
- 16 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.1.0 → 0.1.1 functional
- 15 Nov 26 55
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 21 Nov 2026 · Analysed npm/@eazetech/website-security-audit-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 23 packages
| Packages resolved | 23 |
|---|---|
| Stale | 2 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
audit_website_security Audit website security ~202
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| cached | boolean | yes | True when this result was reused from a scan of the same address in the last minute |
| counts | object | yes | – |
| domain | string | yes | – |
| durationMs | integer | yes | – |
| findings | array | yes | Sorted from critical to pass |
| grade | string | yes | – |
| notes | array | yes | Checks that did not finish, were skipped or saw partial data |
| redirects | array | yes | – |
| scannedAt | string | yes | ISO 8601 time of the scan |
| score | integer | yes | – |
| target | string | yes | Final address after redirects, without query string |
No examples provided.
check_security_headers Check security headers ~151
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| cookieCount | integer | yes | Number of Set-Cookie headers on the final response |
| counts | object | yes | – |
| domain | string | yes | – |
| durationMs | integer | yes | – |
| findings | array | yes | – |
| headers | object | yes | Values from the final response, cleaned and shortened. A header that is not set is left out. |
| notes | array | yes | Checks that did not finish, were skipped or saw partial data |
| redirects | array | yes | – |
| scannedAt | string | yes | – |
| target | string | yes | Final address after redirects, without query string |
No examples provided.
check_security_txt Check security.txt ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to check, such as example.com. A full URL is also accepted; only its host name is used. |
| Name | Type | Req | Description |
|---|---|---|---|
| checked | array | yes | – |
| contentType | string | – | – |
| domain | string | yes | – |
| durationMs | integer | yes | – |
| 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 | yes | – |
| found | boolean | yes | – |
| notes | array | yes | Checks that did not finish, were skipped or saw partial data |
| scannedAt | string | yes | – |
| signed | boolean | yes | True when the file carries an OpenPGP cleartext signature |
| url | string | – | Where the file was found; left out when none was found |
No examples provided.
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.
npm · @eazetech/website-security-audit-mcp
claude mcp add co-eazetech-website-security-audit -- npx -y @eazetech/website-security-audit-mcp
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.