Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.mcparmory/scrapingant

PYPI · MCPARMORY-SCRAPINGANT · 2 COMPONENTS

Scrape webpages, handle JavaScript and CAPTCHA, extract structured data

−20 this week 60 Trust /100

Last scanned (20 hours ago)

Scores higher than 57% of PyPI servers

Category Web Scraping

Trust breakdown (7 categories)

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
  • No install/post-install scripts declared.Pass
  • 1 of 22 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2003 tokens (~333/item across 6 items; 6 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 Management60
  • Stability observed for 18 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
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "scrape_webpage_remove" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 6 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
Changelog

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 −6
    • Stability: pass → 0.60 functional
  • 3 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 31 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 30 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 29 Oct 26 +1
    • Stability: 0.97 → pass security
  • 28 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 22 Oct 26 +1
    • Stability: 0.97 → pass security
  • 21 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
Diagnostics

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/mcparmory-scrapingant@1.0.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Dependencies 22 packages
Packages resolved 22
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~2,003 tokens

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 →

Tool Tokens
get_usage ~25

Retrieve the current API credits usage status and consumption metrics for your Scrapingant account.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

scrape_webpage ~414

Scrape content from a webpage with optional browser rendering, JavaScript execution, and proxy configuration. Supports cookie injection, resource blocking, and element-specific wait conditions for dynamic content.

NameTypeReqDescription
block_resourcestring–Resource types to block from loading in the browser (e.g., image, stylesheet, script, font). Can be specified multiple times for multiple types. Only applies when browser rendering is enabled. Useful…
browserboolean–Whether to render the page using a headless browser to execute JavaScript and load dynamic content. Enabled by default. Disable to retrieve raw server response only.
cookiesstring–Session cookies to include with the scraping request, formatted as semicolon-separated key-value pairs (e.g., name1=value1;name2=value2). Useful for authenticated scraping.
js_snippetstring–Base64-encoded JavaScript code to execute after the page loads in the browser. Only applies when browser rendering is enabled. Useful for custom interactions like scrolling or form submission.
proxy_countrystring–Country code for the proxy location (e.g., US, GB, DE). If not specified, a random country will be used. Only applies when using a proxy.
proxy_typestring–Proxy type for the request: datacenter (faster, shared IPs) or residential (slower, real user IPs). Defaults to datacenter.
return_page_sourceboolean–Return the unaltered HTML source from the server without browser-based JavaScript rendering. Only applies when browser rendering is enabled. Useful for comparing server-side vs. client-side rendered…
urlstringyesThe target URL to scrape. Must be a valid, complete URL.
wait_for_selectorstring–CSS selector of an element to wait for before returning results. The scraper will poll until the element appears in the DOM. Only applies when browser rendering is enabled. Useful for waiting on dyna…

No output schema declared.

No examples provided.

scrape_webpage_modify ~400

Scrape a webpage with optional browser rendering, JavaScript execution, and proxy configuration. Supports waiting for dynamic content, blocking resources, and injecting custom scripts.

NameTypeReqDescription
block_resourcestring–Resource types to block from loading in the browser (e.g., image, stylesheet, script, font, xhr, fetch). Reduces bandwidth and speeds up scraping. Only applies when browser is enabled. Can be specifi…
browserboolean–Whether to use a headless browser for scraping to render JavaScript and handle dynamic content. Enabled by default. Required for JS execution, page waiting, and resource blocking features.
cookiesstring–HTTP cookies to include with the scraping request, formatted as semicolon-separated key-value pairs (e.g., name1=value1;name2=value2).
js_snippetstring–Base64-encoded JavaScript code to execute after the page loads in the browser. Only applies when browser is enabled. Useful for interactions, data extraction, or triggering additional content loads.
proxy_countrystring–Country code for the proxy location (e.g., US, GB, DE). If not specified, a random country will be used. Only applies when using a proxy.
proxy_typestring–Type of proxy to route the request through: datacenter (faster, shared IPs) or residential (slower, real user IPs). Defaults to datacenter.
return_page_sourceboolean–Return the unaltered HTML source as received from the server without JavaScript rendering. Only applies when browser is enabled. Disabled by default.
urlstringyesThe target URL to scrape. Must be a valid HTTP or HTTPS URL.
wait_for_selectorstring–CSS selector of an element to wait for before returning results. The scraper will poll until the element appears in the DOM. Only applies when browser is enabled.

No output schema declared.

No examples provided.

scrape_webpage_remove ~383

Scrape a webpage with optional browser rendering, JavaScript execution, and proxy configuration. Supports cookie injection, resource blocking, and element-waiting strategies for dynamic content extraction.

NameTypeReqDescription
block_resourcestring–Resource types to block from loading in the browser (e.g., image, stylesheet, script, font). Reduces bandwidth and speeds up scraping. Only applies when browser is enabled. Can be specified multiple…
browserboolean–Whether to use a headless browser for scraping to handle JavaScript-rendered content. Enabled by default. Required for JS execution and resource blocking features.
cookiesstring–HTTP cookies to include with the scraping request, formatted as semicolon-separated key-value pairs (e.g., name1=value1;name2=value2).
js_snippetstring–Base64-encoded JavaScript code to execute after the page loads in the browser. Only applies when browser is enabled. Useful for interactions, scrolling, or data extraction.
proxy_countrystring–Country code for the proxy location (e.g., US, GB, DE). If not specified, a random country will be used.
proxy_typestring–Type of proxy to route the request through: datacenter (faster, shared IPs) or residential (slower, real user IPs). Defaults to datacenter.
return_page_sourceboolean–Return the unaltered HTML as received from the server without JavaScript rendering. Only applies when browser is enabled. Disabled by default.
urlstringyesThe target URL to scrape. Must be a valid, complete URL.
wait_for_selectorstring–CSS selector of an element to wait for before returning results. The service will poll until the element appears in the DOM. Only applies when browser is enabled.

No output schema declared.

No examples provided.

scrape_webpage_replace ~395

Scrape a webpage with optional browser rendering, JavaScript execution, and proxy configuration. Supports cookie injection, resource blocking, and element-based wait conditions for dynamic content.

NameTypeReqDescription
block_resourcestring–Resource types to block from loading in the browser (e.g., image, stylesheet, script, font). Can be specified multiple times for multiple types. Only applies when browser is enabled. Reduces bandwidt…
browserboolean–Whether to use a headless browser for scraping to render JavaScript and handle dynamic content. Enabled by default. Required for JS execution, page source capture, and element waiting.
cookiesstring–Cookies to include with the scraping request, formatted as semicolon-separated key-value pairs (e.g., name1=value1;name2=value2).
js_snippetstring–Base64-encoded JavaScript code to execute after the page loads in the browser. Only applies when browser is enabled. Useful for interactions, scrolling, or data extraction.
proxy_countrystring–Country code for the proxy location (e.g., US, GB, DE). If not specified, a random country will be used. Only applies when using proxies.
proxy_typestring–Type of proxy to use for the request: datacenter (default) for speed or residential for authenticity. Datacenter proxies are faster; residential proxies better mimic real users.
return_page_sourceboolean–Return the unaltered HTML returned by the server without JavaScript rendering. Only applies when browser is enabled. When true, JavaScript will not be executed.
urlstringyesThe target URL to scrape. Must be a valid HTTP or HTTPS URL.
wait_for_selectorstring–CSS selector of an element to wait for before returning results. The scraper will poll until the element appears in the DOM. Only applies when browser is enabled.

No output schema declared.

No examples provided.

scrape_webpage_submit ~386

Scrape content from a webpage using optional headless browser rendering, JavaScript execution, and proxy configuration. Supports cookie injection, resource blocking, and element-specific wait conditions for dynamic content.

NameTypeReqDescription
block_resourcestring–Resource types to block from loading in the browser (e.g., image, stylesheet, script, font). Reduces bandwidth and speeds up scraping. Only applies when browser is enabled. Can be specified multiple…
browserboolean–Enable headless browser rendering to execute JavaScript and handle dynamic content. Defaults to true. When disabled, only raw server response is returned.
cookiesstring–HTTP cookies to include with the scraping request, formatted as semicolon-separated key-value pairs (e.g., name1=value1;name2=value2).
js_snippetstring–Base64-encoded JavaScript code to execute after the page loads in the browser. Only applies when browser is enabled. Useful for interactions, scrolling, or data extraction.
proxy_countrystring–Country code for proxy location (e.g., US, GB, DE). If not specified, a random country is selected. Only applies when using a proxy.
proxy_typestring–Proxy type for the request: datacenter (faster, shared IPs) or residential (slower, real user IPs). Defaults to datacenter.
return_page_sourceboolean–Return the unaltered page source as received from the server without JavaScript rendering. Only applies when browser is enabled. Defaults to false.
urlstringyesThe target URL to scrape. Must be a valid, complete URL.
wait_for_selectorstring–CSS selector of an element to wait for before returning results. The scraper will poll until the element appears or timeout occurs. Only applies when browser is enabled.

No output schema declared.

No examples provided.

Install

How do I install the com.mcparmory/scrapingant MCP server?

com.mcparmory/scrapingant runs locally as a PyPI package, launched with uvx mcparmory-scrapingant. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mcparmory-scrapingant

# add to Claude Code
claude mcp add com-mcparmory-scrapingant -- uvx mcparmory-scrapingant
Common questions

What is the com.mcparmory/scrapingant MCP server?

com.mcparmory/scrapingant is an MCP server listed in the public MCP registry as com.mcparmory/scrapingant. Scrape webpages, handle JavaScript and CAPTCHA, extract structured data. This page covers its PyPI package (mcparmory-scrapingant).

Is the com.mcparmory/scrapingant MCP server safe to use?

com.mcparmory/scrapingant scores 60 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 com.mcparmory/scrapingant MCP server expose?

com.mcparmory/scrapingant exposes 6 tools: scrape_webpage, scrape_webpage_submit, scrape_webpage_replace, scrape_webpage_modify, scrape_webpage_remove, get_usage. Their descriptions and schemas cost roughly 2,003 tokens of context every time the server is loaded.

Is the com.mcparmory/scrapingant MCP server still maintained?

com.mcparmory/scrapingant 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.

What licence is the com.mcparmory/scrapingant MCP server under?

com.mcparmory/scrapingant declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.