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.

io.github.bamchi/scrapi

NPM · @SCRAPI.AI/MCP-SERVER · 2 COMPONENTS

Web scraping for AI agents. Converts URLs to clean, LLM-ready Markdown with anti-bot bypass.

0 this week 80 Trust /100

Last scanned (14 hours ago)

Scores higher than 65% of npm 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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 47 of 149 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency44
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 320 tokens (~64/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
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 0
    • Security disclosure: unverified → fail ▼ functional
  • 3 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 1 Nov 26 +1
    • Stability: 0.97 → pass security
  • 31 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 25 Oct 26 +1
    • Stability: 0.97 → pass security
  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Stability: pass → 0.97 functional
  • 20 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 19 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
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 5 Nov 2026 · Analysed npm/@scrapi.ai/mcp-server@2.0.6

Provenance No attestation

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

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 2 findings
ID CVE Severity Vector Fix available
GHSA-3p6v-hrg8-8qj7 CVE-2025-2792 low yes
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 149 packages
Packages resolved 149
Deprecated 1
Stale 47
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~320 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_billing ~122

Retrieve MCP billing information: subscription details, available plans, daily usage history, or spending limits. Requires MCP API key (hsmcp_ prefix).

NameTypeReqDescription
actionstringyesWhat billing info to retrieve: subscription (current plan details), plans (available plans), daily_usage (credit usage history), spending_limits (daily spend limit status)
end_datestring–End date for daily_usage (YYYY-MM-DD). Default: today
start_datestring–Start date for daily_usage (YYYY-MM-DD). Default: 30 days ago

No output schema declared.

No examples provided.

get_usage ~39

Check API usage and remaining credits. Returns current plan, total credits, usage, remaining credits, and reset date. Supports both MCP and Legacy API keys.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

scrape_url ~60

Scrapes a webpage and returns the content in AI-readable Markdown format. Can access blocked sites through browser rendering.

NameTypeReqDescription
formatstring–Output format: markdown (default) or text
urlstringyesThe URL of the webpage to scrape

No output schema declared.

No examples provided.

scrape_urls ~62

Scrapes multiple webpages in parallel and returns the content in AI-readable Markdown format. Can access blocked sites through browser rendering.

NameTypeReqDescription
formatstring–Output format: markdown (default) or text
urlsarrayyesURLs to scrape (max 10)

No output schema declared.

No examples provided.

scraper_server_status ~37

Check the status of all ScraperServer instances. Shows server health, circuit breaker state, failure counts, and last success/failure times.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the io.github.bamchi/scrapi MCP server?

io.github.bamchi/scrapi runs locally as an npm package, launched with npx -y @scrapi.ai/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @scrapi.ai/mcp-server

# add to Claude Code
claude mcp add bamchi-scrapi -- npx -y @scrapi.ai/mcp-server
Common questions

What is the io.github.bamchi/scrapi MCP server?

io.github.bamchi/scrapi is an MCP server listed in the public MCP registry as io.github.bamchi/scrapi. Web scraping for AI agents. Converts URLs to clean, LLM-ready Markdown with anti-bot bypass. This page covers its npm package (@scrapi.ai/mcp-server).

Is the io.github.bamchi/scrapi MCP server safe to use?

io.github.bamchi/scrapi scores 80 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 5 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 io.github.bamchi/scrapi MCP server expose?

io.github.bamchi/scrapi exposes 5 tools: scrape_url, scrape_urls, get_usage, scraper_server_status, get_billing. Their descriptions and schemas cost roughly 320 tokens of context every time the server is loaded.

Is the io.github.bamchi/scrapi MCP server still maintained?

io.github.bamchi/scrapi 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 io.github.bamchi/scrapi MCP server under?

io.github.bamchi/scrapi declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.