outscraper-mcp-server
Provides an MCP (Model Context Protocol) server that exposes Outscraper-based extraction tools (e.g., Google Maps/Google/Yelp/Trustpilot/Amazon reviews and business/contact data) to MCP clients (e.g., Claude Desktop, Cursor).
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Transport security (TLS) is not explicitly stated in the provided content; assume HTTPS by typical API practice but score conservatively. Authentication is via API key in environment variables (better than embedding in code/logs), but no scope granularity or security controls are described. License in metadata is MIT; dependency list is limited in the manifest, but no CVE/vulnerability status is provided.
⚡ Reliability
Best When
You need a standardized MCP tool interface for multi-source web/data extraction and you already have an Outscraper API key.
Avoid When
You require a documented, self-hostable REST/SDK interface with complete machine-readable specs or you need strong guarantees on idempotency/retry/error semantics at the MCP tool level.
Use Cases
- • AI-assisted business research and lead enrichment from multiple public web sources
- • Aggregating reviews and ratings for competitors or specific locations
- • Extracting contact info (emails/phones) and validating deliverability
- • Geocoding and reverse geocoding workflows via an agent
- • Bulk review scraping workflows with pagination/time filtering
Not For
- • Directly scraping sites where automated extraction is disallowed by the target service’s terms
- • User-specific or sensitive data processing without appropriate legal/compliance review
- • Use in a security-critical production environment without reviewing error handling, logging, and data retention
Interface
Authentication
Authentication is described as an environment variable containing an Outscraper API key. No mention of OAuth or scoped tokens in the provided content.
Pricing
Readme points to Outscraper pricing and notes request-based tracking; specific limits/costs are not provided in the package content.
Agent Metadata
Known Gotchas
- ⚠ LLM/agent callers may trigger high-volume extraction; pricing/rate limits are only broadly referenced, so agents should self-throttle/cap requests.
- ⚠ Because the MCP tool set is broad (25+ tools) but tool-level error/retry/idempotency semantics are not shown in the provided README, agents may need defensive handling for partial failures.
- ⚠ Ensure API key is correctly injected into the MCP server environment; misconfiguration will likely cause tool failures (exact error behavior not documented).
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for outscraper-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.