# com.squirrelscan/squirrelscan

Website QA for your coding agent: audit SEO, performance, security, accessibility over MCP.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.0.2
- **Author:** com.squirrelscan
- **License:** Unknown
- **Endpoints:** streamable-http https://mcp.squirrelscan.com/mcp
- **Source:** https://github.com/squirrelscan/squirrelscan
- **Endpoint health:** reachable (last checked 2026-08-26T22:19:29.783Z, 1 sample) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 13 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-08-15T15:33:08.878Z
- **Version scanned:** HEAD
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

40 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `analyze`
- `audit`
- `login`
- `logout`
- `status`
- `whoami`
- `auth`
- `config`
- `show`
- `set`
- `path`
- `validate`
- `crawl`
- `credits`
- `feedback`
- `init`
- `create`
- `list`
- `revoke`
- `keys`
- `mcp`
- `report`
- `install`
- `update`
- `completion`
- `doctor`
- `version`
- `settings`
- `uninstall`
- `self`
- `skills`
- `audit_website`
- `quick_check`
- `list_issues`
- `get_issue`
- `comment_on_issue`
- `get_report`
- `list_audits`
- `list_rules`
- `get_rule`

## Install

**Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"squirrelscan\": {\n      \"type\": \"http\",\n      \"url\": \"https://mcp.squirrelscan.com/mcp\"\n    }\n  }\n}"
```

## Blast radius

Moderate to extensive — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: mutates data; runs on someone else's infrastructure.
- Floor 29, ceiling 53 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/com.squirrelscan%2Fsquirrelscan
- Install plan: https://forgeregistry.com/api/v1/packages/com.squirrelscan%2Fsquirrelscan/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/com.squirrelscan%2Fsquirrelscan
- HTML page: https://forgeregistry.com/registry/com.squirrelscan%2Fsquirrelscan
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.