Local MCP capabilities provider for Expo
Nothing to run from here
squirrelscan is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
18
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Audit websites for SEO, performance, security, accessibility and agent experience issues.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http mcp-squirrelscan-com-squirrelscan-mcp https://mcp.squirrelscan.com/mcp
# 2 — ask your agent for something these tools do
# run_audit, get_audit_status, list_audits and 15 more
squirrelscan costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MSAll 1 server
mcp.squirrelscan.com1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http mcp-squirrelscan-com-squirrelscan-mcp https://mcp.squirrelscan.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
18 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Run a cloud audit of a website (crawl + 260+ rule analysis + report). Credits are spent as the audit runs (pay-as-you-go). The dry run is optional: pass confirm: true on the first call to start straight away. Without confirm, an audit whose estimate is over the org's auto-run threshold comes back as status "confirmation_required" with the estimate to show the user, and you call again with confirm:
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Website URL to audit, e.g. https://example.com (scheme optional). |
| confirm | boolean | no | Approve the credit spend. Set true to start immediately. Omitting it returns an estimate first for anything over the auto-run threshold, and starts the audit anyway for anything at or under it. |
| max_credits | integer | no | Spend guard: refuse to start if the upper-bound estimate exceeds this many credits. |
| coverage | string | no | Crawl coverage profile (default fast, 10 pages). Deeper coverage crawls more pages and costs more credits. |
| max_pages | integer | no | Cap the crawl at this many pages for this run. Overrides the coverage profile's page count, so max_pages: 1 audits just the entry URL for the cheapest possible run. A value above the plan's per-audit |
| render | boolean | no | Render pages in a headless browser (default true). Catches JavaScript-dependent issues; costs extra credits per page. |
| ephemeral | boolean | no | One-shot check: run the audit and return the report without adding the site to the organization's website list, and without consuming a slot against the plan's website limit. Use for any 'just check t |
| kind | string | no | Classify the site: 'owned' for something the user runs and monitors, 'prospect' for a lead or competitor audited once. Filterable in list_websites so a prospect cleanup can never sweep up a live site. |
Poll a running audit by run_id (from run_audit or list_audits). Status pending/running means keep polling (every 15-30 seconds) — the response includes a progress field (phase, message, page/link counts) when available. Status completed means the report is ready: call get_report with the same run_id. Status failed/cancelled includes the error and completion reason.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| run_id | string | yes | Run id returned by run_audit or listed by list_audits. |
List the organization's audit runs: currently active (pending/running) plus recent runs of any status. Pass website_id (from list_websites) to get one website's full audit history, oldest runs included, and page through it with limit/offset using the returned total/has_more. This is the way to reach the preserved reports of a soft-deleted website: its runs still list under its old website_id. tota
| Parameter | Type | Required | Notes |
|---|---|---|---|
| website_id | string | no | Only return runs of this website (id from list_websites, run_audit, or add_website). Works for soft-deleted websites too. |
| limit | integer | no | Max recent runs to return (default 20, max 100). |
| offset | integer | no | Pagination offset into the recent runs (default 0). Use with total/has_more. |
List websites the organization has audited, with their latest run status, health score, and owned/prospect kind. Each row carries last_run_id (the latest run, any status) and last_report_run_id / last_report_id (the latest completed run whose report has not been deleted) — pass last_report_run_id to get_report to read a website's newest report without knowing a run id in advance, or list_audits wi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Page size (default 50). |
| offset | integer | no | Pagination offset (default 0). |
| kind | string | no | Filter by classification. Unclassified sites count as 'owned', so 'prospect' never returns a site nobody explicitly marked disposable. Omit for all websites. |
Register a website with the organization without running an audit (run_audit registers automatically, so this is only needed to set a site up ahead of time). Returns the website_id; idempotent per domain, so calling it again returns the existing website. Pass kind to classify it as owned or prospect up front.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Website URL to register, e.g. https://example.com (scheme optional). |
| kind | string | no | Classify the site: 'owned' for something the user runs and monitors, 'prospect' for a lead or competitor. Filterable in list_websites. Unclassified sites read as 'owned', so only an explicit 'prospect |
Delete a website from the organization (soft delete: past audits, reports, and issues are preserved, and published report links keep working). Frees a slot under the plan's website limit. Re-adding the same domain later registers a fresh website with a new website_id. Call once without confirm to see what will happen; call again with confirm: true to delete. To remove many sites at once, use delet
| Parameter | Type | Required | Notes |
|---|---|---|---|
| website_id | string | yes | Website id from list_websites, run_audit, or add_website. |
| confirm | boolean | no | Approve the deletion. Omit on the first call to see the effect; set true to delete after the user approves. |
Delete up to 50 websites in one call, for cleaning up a dashboard that has filled with one-off or prospect audits. Same soft delete as delete_website (past audits, reports, and issues are preserved, published report links keep working, slots are freed) and the same two-step confirm: call once without confirm to see the domain behind every id, then again with confirm: true. EVERY result echoes the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| website_ids | array | yes | Website ids from list_websites (1 to 50). Duplicates are collapsed. |
| confirm | boolean | no | Approve the deletions. Omit on the first call to see which domain each id resolves to; set true to delete after the user approves. |
Fetch the finished report for an audit run (use the run_id from run_audit once get_audit_status shows completed). Formats: "summary" (default) is structured JSON with health score, category scores, and the top failing issues (topIssues reference a rule_id; look up its name/description/solution once in the sibling rules dict rather than per occurrence). Each topIssues row carries provenance: "c
| Parameter | Type | Required | Notes |
|---|---|---|---|
| run_id | string | yes | Run id returned by run_audit or listed by list_audits. |
| format | string | no | summary (default): JSON scores + top issues. llm: compact text for LLM context. markdown: full report. |
| top_issue_limit | integer | no | summary format only: max top issues to include (default 25). |
List a website's open audit issues (like a bug tracker: each issue is one failing rule with occurrences across pages, numbered per website). Returns issues sorted by severity, plus severity and status summaries. Use the issue number with get_issue for full detail and comments. Filter by status/severity/category to narrow down.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| website_id | string | yes | Website id from list_websites, run_audit, or list_audits. |
| status | string | no | Filter by issue status (omit for all statuses). |
| severity | string | no | Filter by severity. |
| category | string | no | Filter by rule category code (e.g. seo, performance, security). |
| limit | integer | no | Page size (default 50). |
| offset | integer | no | Pagination offset (default 0). |
Fetch one issue by website_id + issue number, including its full description, recommendation, affected pages, occurrence detail from the latest report (which page/image/URL, snippets), and comment thread. Use comment_on_issue to add analysis or a fix note to the thread.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| website_id | string | yes | Website id the issue belongs to. |
| issue_number | integer | yes | Issue number from list_issues. |
| occurrence_limit | integer | no | Max occurrences to include (default 20); see occurrence_count/truncated. |
Post a comment on a website issue — use it to record analysis, a proposed fix, or what you changed, so the team sees it in the dashboard issue thread. Markdown is supported.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| website_id | string | yes | Website id the issue belongs to. |
| issue_number | integer | yes | Issue number from list_issues. |
| body | string | yes | Comment body (markdown supported). |
Browse the catalog of 260+ audit rules that run during an audit, grouped into categories (crawlability, meta tags, performance, security, accessibility, content, and more). Filter by category code or search by keyword to find what a specific rule checks. Use get_rule for one rule's full detail.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | Filter to one category code (see the categories list in the response). |
| search | string | no | Case-insensitive keyword match on rule id, name, and description. |
Fetch one audit rule by id (e.g. "meta/title-length"), including what it checks, how to fix it (recommendation), its severity and score weight, a docs link, and whether it is a cloud (credit-billed) rule. Rule ids appear in report topIssues and issue rule_id fields.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rule_id | string | yes | Rule id like "crawl/canonical-chain" (category/slug). |
Identify the current credentials: how you are authenticated, which organization you act for, the plan, and the current credit balance. Call this first in a session to orient yourself before running audits.
No parameter schema on file.
Get the organization's credit balance: monthly credits (reset each billing period) and pack credits (purchased, never expire). Audits spend credits pay-as-you-go while they run; run_audit shows an upper-bound estimate before starting. Top up at https://app.squirrelscan.com/billing.
No parameter schema on file.
Audit the organization's credit accounting log: grants (signup/monthly/pack/promo), debits (audit_base 50cr + render 2cr/page + folded 0-cost services), refunds, and adjustments — newest first, paginated. Each debit/refund carries run_id so you can group a single audit's spend. Use this to explain why an audit cost what it cost or to reconcile a balance. For one audit's per-feature breakdown, us
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max transactions to return (default 25, max 100). |
| cursor | string | no | Opaque pagination cursor from a previous page's next_cursor. |
Mint a new squirrelscan API key for this organization (requires credentials carrying the keys:write scope, which OAuth sign-in grants). The key is returned EXACTLY ONCE: show it to the user immediately and suggest saving it as the SQUIRRELSCAN_API_KEY environment variable for the CLI, CI, and MCP. Minted keys cannot themselves mint keys.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Human-readable label shown in the dashboard, e.g. "ci" or "claude-code". |
| scopes | array | no | Scopes to grant (default: audits:write, audits:read, credits:read, org:read). Grantable: audits:write, audits:read, credits:read, org:read, org:write. |
| expires_in_days | integer | no | Expire the key after this many days (default: never expires). |
Report your experience using squirrelscan mid-session: a bug, a missing feature, what worked, what confused you, missing report data, or tool ergonomics. Reviewed by the team to improve the product — use it any time something surprises you, not just at the end of a session. Works with any authenticated credentials, including read-only API keys.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | yes | bug_report (a defect in squirrelscan itself — wrong or missing rule result, crash, broken tool), feature_request (something squirrelscan should do but doesn't), what_worked (something worked well), co |
| message | string | yes | Free-text feedback (truncated at 2000 chars). |
| run_id | string | no | Audit run id this feedback relates to, if any (from run_audit/get_report). Verified against your credentials' runs before being attached. |
| website_id | string | no | Website id this feedback relates to, if any (from list_websites). Verified against your org's websites before being attached. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install squirrelscan or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.0.1.
0.0.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish squirrelscan can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.