scraperapi-mcp-server

Provides an MCP server interface for ScraperAPI (a scraping/proxy service), enabling AI agents to call scraping-related tools via the Model Context Protocol.

Evaluated Apr 04, 2026 (25d ago)
Homepage ↗ DevTools mcp scraping web-proxy agents tooling scraperapi
⚙ Agent Friendliness
45
/ 100
Can an agent use this?
🔒 Security
54
/ 100
Is it safe for agents?
⚡ Reliability
8
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
55
Documentation
40
Error Messages
0
Auth Simplicity
70
Rate Limits
25

🔒 Security

TLS Enforcement
85
Auth Strength
55
Scope Granularity
30
Dep. Hygiene
50
Secret Handling
50

Scraping/proxy tooling typically requires an API key; strength depends on how the MCP server stores/handles that key and whether it uses least-privilege headers/scopes. TLS and secret-handling specifics are not evidenced in the provided content and should be verified in the MCP server implementation/docs.

⚡ Reliability

Uptime/SLA
0
Version Stability
0
Breaking Changes
0
Error Recovery
30
AF Security Reliability

Best When

You want LLM/agent tool calls to fetch web content through ScraperAPI using a standardized MCP integration.

Avoid When

You require REST/GraphQL/SDK-centric integrations only, or you need strict guarantees about pagination/error semantics not covered by the MCP tool contract.

Use Cases

  • Agent-driven web scraping workflows
  • Gathering web page content for downstream extraction/summarization
  • Automated research pipelines that need scraping as a tool action

Not For

  • High-volume large-scale scraping without confirming the provider’s terms/limits
  • Use cases requiring complex custom crawling logic beyond the exposed MCP tools

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: API key / token for ScraperAPI (implied typical setup)
OAuth: No Scopes: No

Auth details and exact header/parameter names are not available from the provided prompt content; evaluation assumes common ScraperAPI key-based auth but should be confirmed in the repo docs.

Pricing

Free tier: No
Requires CC: No

Pricing not provided in the supplied content; ScraperAPI commonly uses usage-based billing—confirm in ScraperAPI docs and the MCP server README.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Scraping results may be non-deterministic (dynamic pages, anti-bot behavior, target-site changes).
  • Agents may need to throttle to avoid provider rate limits; retry behavior may vary by tool implementation.
  • Tool inputs (URLs/headers/cookies) may require careful validation/sanitization before calling the MCP tools.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for scraperapi-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered