io.github.bamchi/scrapi
REMOTE · SCRAPI.AI · 2 COMPONENTS · SCANNED SEP 20
Web scraping for AI agents. Converts URLs to clean, LLM-ready Markdown with anti-bot bypass.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 300 tokens (~60/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
How do I install the io.github.bamchi/scrapi MCP server?
io.github.bamchi/scrapi is a hosted endpoint at https://scrapi.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · scrapi.ai
claude mcp add --transport http bamchi-scrapi 'https://scrapi.ai/mcp'
{
"mcpServers": {
"bamchi-scrapi": {
"url": "https://scrapi.ai/mcp"
}
}
} {
"servers": {
"bamchi-scrapi": {
"type": "http",
"url": "https://scrapi.ai/mcp"
}
}
} [mcp_servers.bamchi-scrapi] url = "https://scrapi.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bamchi-scrapi": {
"type": "remote",
"url": "https://scrapi.ai/mcp",
"enabled": true
}
}
} openclaw mcp add bamchi-scrapi --url 'https://scrapi.ai/mcp' --transport streamable-http
mcp_servers:
bamchi-scrapi:
url: "https://scrapi.ai/mcp" {
"McpServers": {
"bamchi-scrapi": {
"Transport": "http",
"Url": "https://scrapi.ai/mcp"
}
}
} assistant mcp add bamchi-scrapi -t streamable-http -u 'https://scrapi.ai/mcp'
{
"mcpServers": {
"bamchi-scrapi": {
"type": "http",
"url": "https://scrapi.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
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 20 Sept 2026 · Probed https://scrapi.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=scrapi.ai | CN=YE2,O=Let's Encrypt,C=US | 11 Aug 2026 | 9 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5894430976373d4f0a4848db1bd2415518f |
| SANs: scrapi.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of scrapi.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| scrapi.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://scrapi.ai/mcp | Verified | 200 | |
| http (plaintext) | http://scrapi.ai/mcp | HTTPS enforced | 301 | https://scrapi.ai/mcp |
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 →
get_billing ~111
Retrieve MCP billing information: subscription details, available plans, daily usage history, or spending limits.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | What billing info to retrieve: subscription (current plan details), plans (available plans), daily_usage (credit usage history), spending_limits (daily spend limit status) |
| end_date | string | – | End date for daily_usage (YYYY-MM-DD). Default: today |
| start_date | string | – | Start date for daily_usage (YYYY-MM-DD). Default: 30 days ago |
No output schema declared.
No examples provided.
get_usage ~30
Check API usage and remaining credits. Returns current plan, subscription credits, purchased credits, and total remaining credits.
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.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Output format: markdown (default) or text |
| url | string | yes | The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Output format: markdown (default) or text |
| urls | array | yes | URLs 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.
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 hosted endpoint (https://scrapi.ai/mcp).
Is the io.github.bamchi/scrapi MCP server safe to use?
io.github.bamchi/scrapi scores 89 out of 100 on VerifyMCP. 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 300 tokens of context every time the server is loaded.
Does the io.github.bamchi/scrapi MCP server require authentication?
Yes. io.github.bamchi/scrapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.