Scrappa
REMOTE · SCRAPPA.CO · SCANNED OCT 5
Scraping API for Google Search, Maps, Flights, Jobs, YouTube, LinkedIn, Trustpilot and more.
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability82
- 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
- Tool/resource definitions use about 314 tokens (~104/item across 3 items; 2 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: schema churn in the 5 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
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 2 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Scrappa MCP server?
Scrappa is a hosted endpoint at https://scrappa.co/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 · scrappa.co
claude mcp add --transport http co-scrappa-scrappa 'https://scrappa.co/mcp'
{
"mcpServers": {
"co-scrappa-scrappa": {
"url": "https://scrappa.co/mcp"
}
}
} {
"servers": {
"co-scrappa-scrappa": {
"type": "http",
"url": "https://scrappa.co/mcp"
}
}
} [mcp_servers.co-scrappa-scrappa] url = "https://scrappa.co/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"co-scrappa-scrappa": {
"type": "remote",
"url": "https://scrappa.co/mcp",
"enabled": true
}
}
} openclaw mcp add co-scrappa-scrappa --url 'https://scrappa.co/mcp' --transport streamable-http
mcp_servers:
co-scrappa-scrappa:
url: "https://scrappa.co/mcp" {
"McpServers": {
"co-scrappa-scrappa": {
"Transport": "http",
"Url": "https://scrappa.co/mcp"
}
}
} assistant mcp add co-scrappa-scrappa -t streamable-http -u 'https://scrappa.co/mcp'
{
"mcpServers": {
"co-scrappa-scrappa": {
"type": "http",
"url": "https://scrappa.co/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.
- 2 Oct 26 +6
- Stability: 0.03 → fail ▼ security
- A breaking change shipped without a version bump: still 2.0.0 ▼ security
- Tool “bing-webmaster-report” was removed ▼ security
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- The server changed its declared name: Scrappa API → Scrappa security
- Tool “call-endpoint” rewrote its description, which is the text the model reads security
- Tool “search-endpoints” rewrote its description, which is the text the model reads security
- Schema quality: 446 → 314 ▲ functional
- Tool “call-endpoint” changed its title: Call Endpoint Tool → Call an API endpoint cosmetic
- Tool “search-endpoints” changed its title: Search Endpoints Tool → Find API endpoints cosmetic
- 1 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 30 Sept 26 65
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 5 Oct 2026 · Probed https://scrappa.co/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=scrappa.co | CN=WE1,O=Google Trust Services,C=US | 17 Sept 2026 | 16 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 55fe198e82895cec0ea33c368d173d53 |
| SANs: scrappa.co, *.scrappa.co | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of scrappa.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| scrappa.co. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://scrappa.co/mcp | Verified | 200 | |
| http (plaintext) | http://scrappa.co/mcp | HTTPS enforced | 301 | https://scrappa.co/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 →
call-endpoint Call an API endpoint ~106
Fetch data from a Scrappa API endpoint, including data from third-party sites. Use Find API endpoints to discover an endpoint and its parameters. Requests may use credits on your Scrappa account.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint | string | yes | The endpoint name from search-endpoints results (e.g. "kununu-search", "simple-search") |
| params | string | – | JSON object of parameters to pass to the endpoint (e.g. {"query": "pizza berlin", "page": "1"}) |
No output schema declared.
No examples provided.
search-endpoints Find API endpoints ~66
Find Scrappa API endpoints by keyword. Returns matching endpoint names, descriptions, and parameters. Use a returned endpoint name with Call an API endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search term to find endpoints (e.g. "google maps reviews", "flights", "linkedin profile") |
No output schema declared.
No examples provided.
What is the Scrappa MCP server?
Scrappa is an MCP server listed in the public MCP registry as co.scrappa/scrappa. Scraping API for Google Search, Maps, Flights, Jobs, YouTube, LinkedIn, Trustpilot and more. This page covers its hosted endpoint (https://scrappa.co/mcp).
Is the Scrappa MCP server safe to use?
Scrappa scores 72 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 Scrappa MCP server expose?
Scrappa exposes 2 tools: search-endpoints, call-endpoint. Their descriptions and schemas cost roughly 172 tokens of context every time the server is loaded.
Does the Scrappa MCP server require authentication?
No. We connected to Scrappa without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Scrappa MCP server still maintained?
Scrappa is still listed as active in the MCP registry. We last reached this channel on 5 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.