Screaming Frog SEO Spider MCP Server (headless)
PYPI · SCREAMING-FROG-MCP
Headless Screaming Frog SEO Spider via its CLI: run crawls, export and filter data, no GUI needed.
Available components
Last scanned (14 hours ago)
Scores higher than 92% of PyPI servers
Category Marketing and SEO
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to bzsasson/screaming-frog-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 18 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1103 tokens (~110/item across 10 items; 9 tools + 1 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 Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
- 5 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +4
- Stability: unverified → 0.27 ▲ functional
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 5 Nov 2026 · Analysed pypi/screaming-frog-mcp@0.4.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | bzsasson/screaming-frog-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/bzsasson/screaming-frog-mcp/.github/workflows/publish.yml@refs/tags/v0.4.3 |
| Rekor log index | 3294881614 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:e39c2534d09f31c62aadee6730b0e77b213aa340ca2c8679e1f1f9cb090481f1 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| 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 →
aggregate_crawl_data ~248
Aggregate CSV data from an export: row counts and group-by breakdowns. Use instead of read_crawl_data when the question needs counts or a distribution ("how many 404s", "status code breakdown") rather than the rows themselves. Args: export_id: The export_id from export_crawl file: CSV filename to aggregate (from the file list in export_crawl output) group_by: Optional column name; counts rows per distinct value of it top: Max distinct values to show, most common first (default 20, max 100) filter_column: Optional column name to filter by before aggregating filter_value: Optional value to match in the filter column filter_mode: How to match filter_value: "contains" (default), "exact", or "regex" Returns: Total matching row count, plus per-value counts with percentages when group_by is set.
| Name | Type | Req | Description |
|---|---|---|---|
| export_id | string | yes | – |
| file | string | yes | – |
| filter_column | – | – | – |
| filter_mode | – | – | – |
| filter_value | – | – | – |
| group_by | – | – | – |
| top | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
crawl_site ~160
Start a background Screaming Frog crawl that saves to SF's internal database. Args: url: The URL to crawl (e.g. https://example.com) config_file: Optional path to a .seospiderconfig file for crawl settings. To limit the number of URLs crawled, set the limit in a config file (Configuration > Spider > Limits in the SF GUI) and pass it here. label: Optional label for identifying this crawl (e.g. 'freshgovjobs') Returns: A crawl_id to use with crawl_status to check progress. The crawl runs in the background - use crawl_status to poll.
| Name | Type | Req | Description |
|---|---|---|---|
| config_file | – | – | – |
| label | – | – | – |
| url | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
crawl_status ~41
Check the status of a running or completed crawl. Args: crawl_id: The crawl_id returned by crawl_site
| Name | Type | Req | Description |
|---|---|---|---|
| crawl_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
delete_crawl ~62
Delete a crawl from Screaming Frog's internal database to free disk space. Args: db_id: The Database ID from list_crawls WARNING: This permanently deletes the crawl data. It cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| db_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
export_crawl ~206
Load a saved crawl from SF's database and export data as CSV files. Args: db_id: The Database ID from list_crawls (e.g. '1234' or a crawl identifier) export_tabs: Comma-separated export tabs (default: Internal:All,Response Codes:All,Page Titles:All,Meta Description:All,H1:All,H2:All,Images:All,Canonicals:All,Directives:All). See the export-reference resource for all options. bulk_export: Optional bulk export types (e.g. 'Links:All Inlinks,Content:Soft 404 Inlinks') save_report: Optional reports to save (e.g. 'Crawl Overview') Returns: An export_id and list of generated CSV files. Use read_crawl_data to read them.
| Name | Type | Req | Description |
|---|---|---|---|
| bulk_export | – | – | – |
| db_id | string | yes | – |
| export_tabs | – | – | – |
| save_report | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_crawls ~47
List all crawls saved in Screaming Frog's internal database. Returns crawl names, Database IDs, and sizes. Use the Database ID with export_crawl or delete_crawl.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
read_crawl_data ~258
Read CSV data from an export. Use after export_crawl. Args: export_id: The export_id from export_crawl file: CSV filename to read (from the file list in export_crawl output) limit: Max rows to return (default 100, max 1000) offset: Number of rows to skip (for pagination) filter_column: Optional column name to filter by filter_value: Optional value to match in the filter column filter_mode: How to match filter_value: "contains" (default, case-insensitive substring), "exact" (case-insensitive exact match), or "regex" (Python regex) columns: Optional comma-separated column names to return. Wide exports (Internal:All has dozens of columns) flood the context; request just the ones you need, e.g. "Address,Status Code". Returns: CSV data as formatted text with column headers.
| Name | Type | Req | Description |
|---|---|---|---|
| columns | – | – | – |
| export_id | string | yes | – |
| file | string | yes | – |
| filter_column | – | – | – |
| filter_mode | – | – | – |
| filter_value | – | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
sf_check ~31
Verify that Screaming Frog SEO Spider is installed and the CLI is accessible. Returns version info and license status.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
storage_summary ~34
Show disk usage of Screaming Frog's internal crawl storage. Returns total size and per-crawl breakdown of ProjectInstanceData.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the Screaming Frog SEO Spider MCP Server (headless) server?
Screaming Frog SEO Spider MCP Server (headless) runs locally as a PyPI package, launched with uvx screaming-frog-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · screaming-frog-mcp
claude mcp add bzsasson-screaming-frog-mcp -- uvx screaming-frog-mcp
What is the Screaming Frog SEO Spider MCP Server (headless) server?
Screaming Frog SEO Spider MCP Server (headless) is listed in the public MCP registry as io.github.bzsasson/screaming-frog-mcp. Headless Screaming Frog SEO Spider via its CLI: run crawls, export and filter data, no GUI needed. This page covers its PyPI package (screaming-frog-mcp).
Is the Screaming Frog SEO Spider MCP Server (headless) server safe to use?
Screaming Frog SEO Spider MCP Server (headless) scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 Screaming Frog SEO Spider MCP Server (headless) server expose?
Screaming Frog SEO Spider MCP Server (headless) exposes 9 tools: sf_check, crawl_site, crawl_status, list_crawls, export_crawl, and 4 more. Their descriptions and schemas cost roughly 1,087 tokens of context every time the server is loaded.
Is the Screaming Frog SEO Spider MCP Server (headless) server still maintained?
Screaming Frog SEO Spider MCP Server (headless) is still listed as active in the MCP registry. We last reached this channel on 5 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 Screaming Frog SEO Spider MCP Server (headless) server under?
Screaming Frog SEO Spider MCP Server (headless) 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 Screaming Frog SEO Spider MCP Server (headless) server?
VerifyMCP ran 16 checks on Screaming Frog SEO Spider MCP Server (headless), covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.