certainlyscraped
PYPI · CERTAINLYSCRAPED
Hybrid scraper with escalating effort: cheapest fetch first, reports why each page stopped.
Available components
Last scanned (20 hours ago)
Scores higher than 57% of PyPI servers
Category Web Scraping
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 14 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency84
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to vhsgreed/certainlyscraped). View diagnostics → Pass
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 622 tokens (~155/item across 4 items; 4 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage67
- 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 2 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 1 Nov 26 59
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 4 Nov 2026 · Analysed pypi/certainlyscraped@0.4.5
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 | vhsgreed/certainlyscraped |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/vhsgreed/certainlyscraped/.github/workflows/release.yml@refs/tags/v0.4.5 |
| Rekor log index | 3625764093 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:1559baa41a61ab09e39a266a04d973e24a98c5d6c74895e2c7aa910563c4f814 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 14 packages
| Packages resolved | 14 |
|---|---|
| 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 →
init ~107
Draft a scrape config for a listing page and return it as YAML text. Returns {status: ok|error, config (YAML text, ready to pass to `scrape`), items (guessed items selector), fields (guessed field specs), rows_preview (first 3 extracted rows), note (item count and per-field coverage)}. The selectors are guesses: check the coverage and test a field with try_selector before trusting them.
| Name | Type | Req | Description |
|---|---|---|---|
| url | – | – | – |
No output schema declared.
No examples provided.
probe ~114
Classify a page's anti-bot defences before scraping it. Returns {status: ok|blocked|error, tier (1-2 reachable here; 3 means walled), note, body_size, markers, private_refused, embedded}. Call this first: it decides whether scraping is worth it and whether embedded JSON could replace selectors. Private/loopback addresses are refused (status error, private_refused true) unless the server was started with --allow-private.
| Name | Type | Req | Description |
|---|---|---|---|
| url | – | – | – |
No output schema declared.
No examples provided.
scrape ~301
Run an inline YAML/JSON scrape config and return rows plus a dataset. `config` is config TEXT (not a path). Allowed keys: url, pages, urls, concurrency, items, fields, paginate, max_pages, rate_limit_sec, timeout, tier, max_tier, max_retries, cooldown_sec, per_proxy_rate_sec, output. `proxy`/`proxies`/`cookies`/ `since`/`snapshot`/`fetcher` are refused; tiers are capped at 2. A config may use pages (a {n} template range) or urls (a list) instead of a top-level url. Per-call bounds (notes say when one applied): max_pages 100, pages range 100, urls 100, concurrency 1-16, rate_limit_sec 0-30, per_proxy_rate_sec 0-30, timeout 1-120 s, max_retries 0-3, cooldown_sec 0-60. Returns {status: complete | incomplete | too_few_rows | blocked | error, rows (up to max_rows, default 50, cap 500), row_count (the true total), dataset_path (full JSONL in the server's working directory), pages (per-page outcomes), notes}. Park the full dataset path; the response is truncated.
| Name | Type | Req | Description |
|---|---|---|---|
| config | – | – | – |
| max_rows | – | – | – |
| min_rows | – | – | – |
No output schema declared.
No examples provided.
try_selector ~100
Test a CSS selector against the live page and show what it finds. Returns {status: ok|nothing|error, matches, values (up to 20), tags, warnings, hints}. Pass `within` (an items selector) to test how a field selector resolves inside each item, exactly as scrape would. A malformed selector is an error result, never an exception.
| Name | Type | Req | Description |
|---|---|---|---|
| selector | – | – | – |
| url | – | – | – |
| within | – | – | – |
No output schema declared.
No examples provided.
How do I install the certainlyscraped MCP server?
certainlyscraped runs locally as a PyPI package, launched with uvx certainlyscraped. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · certainlyscraped
claude mcp add vhsgreed-certainlyscraped -- uvx certainlyscraped
What is the certainlyscraped MCP server?
certainlyscraped is an MCP server listed in the public MCP registry as io.github.vhsgreed/certainlyscraped. Hybrid scraper with escalating effort: cheapest fetch first, reports why each page stopped. This page covers its PyPI package (certainlyscraped).
Is the certainlyscraped MCP server safe to use?
certainlyscraped scores 59 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 certainlyscraped MCP server expose?
certainlyscraped exposes 4 tools: probe, init, try_selector, scrape. Their descriptions and schemas cost roughly 622 tokens of context every time the server is loaded.
Is the certainlyscraped MCP server still maintained?
certainlyscraped is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.