# Outscraper MCP Server (npm · outscraper-mcp)

Outscraper MCP business discovery, Maps intelligence, enrichment, reviews, and contact data.

- Trust score: 63/100 (medium)
- Change this week: +19
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.outscraper.com`: 33/100, [markdown](https://verifymcp.io/servers/outscraper-outscraper-mcp-server/mcp.md), [page](https://verifymcp.io/servers/outscraper-outscraper-mcp-server/mcp)
- npm · `outscraper-mcp`: 63/100 (this document), [markdown](https://verifymcp.io/servers/outscraper-outscraper-mcp-server/outscraper-mcp.md), [page](https://verifymcp.io/servers/outscraper-outscraper-mcp-server/outscraper-mcp)

## Channel facts

- Registry: `npm`
- Package: `outscraper-mcp`
- Version: `0.2.3`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 104 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 4673 tokens (~166/item across 28 items; 28 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add outscraper-outscraper-mcp-server -- npx -y outscraper-mcp
```

### Codex

```bash
codex mcp add outscraper-outscraper-mcp-server -- npx -y outscraper-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "outscraper-outscraper-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "outscraper-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add outscraper-outscraper-mcp-server --command npx --arg -y --arg outscraper-mcp
```

### Hermes

```yaml
mcp_servers:
  outscraper-outscraper-mcp-server:
    command: "npx"
    args: ["-y", "outscraper-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "outscraper-outscraper-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "outscraper-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 63, +44)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] Schema quality: unverified → good
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] MCP protocol: unverified → pass
- [functional] Licence: MIT

### 2026-08-01 (score 19, −7)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 26, −13)

- [security regression] Malware scan: pass → unverified

### 2026-07-30 (score 39, −5)

- [functional] First check of Schema quality: unverified

### 2026-07-27 (score 44)

First indexed and scored.

## MCP tools (28)

### `ai_scraper` (~371 tokens)

AI Scraper

Extract structured information from a web page with Outscraper AI Scraper.

Best for:
\- scraping one page and turning it into structured JSON
\- extracting company, people, product, or document metadata from a site
\- guiding extraction with both a prompt and a JSON-schema-like shape

This tool is best for extracting structured data from a single page.

How schema works:
\- schema describes the shape of the output you want back
\- use type="object" with properties for named fields
\- use type="array" with items when a field should be a list
\- add required when some fields must be present

Example schema:
{
  "type": "object",
  "required": [],
  "properties": {
    "company_name": { "type": "string" },
    "company_description": { "type": "string" },
    "people": {
      "type": "array",
      "items": { "type": "string" }
    }
  }
}

Execution notes:
\- execution_mode="sync" requests a direct response
\- execution_mode="async" returns a request id for polling with requests_get
\- if both prompt and schema are provided, prompt guides the extraction and schema shapes the output

Input parameters:

- `async` (boolean): Deprecated compatibility flag. Prefer execution_mode.
- `execution_mode` (string): Execution strategy. Use auto to let the MCP server choose between sync and async.
- `prompt` (string): Natural-language extraction instructions, for example what to summarize or pull from the page.
- `query` (string, required): One URL to scrape, for example https://outscraper.com.
- `schema` (object): Extraction schema describing the shape of the result. This is typically a JSON-schema-like object with type, properties, and optional required fields.

Output parameters:

- `async` (object)
- `data`
- `meta` (object)

### `businesses_search` (~305 tokens)

Outscraper Businesses Search

Search Outscraper businesses using structured filters, a natural-language query, or both.

Best for:
\- building lead lists from normalized business records
\- filtering by country, state, city, type, and other structured business fields
\- paginated browsing with cursor when you want repeatable result navigation

Prefer this tool when:
\- you already know the geography, categories, or other business filters you want
\- you want the normalized /businesses dataset rather than raw Google Maps search behavior
\- you need stable field selection and cursor-based pagination

Use this instead of google_maps_search when:
\- you want the normalized /businesses API
\- you need field selection, filters, or cursor pagination

Note:
\- according to the current OpenAPI, /businesses is a synchronous endpoint in this MCP server
\- async-style execution controls are intentionally not exposed here
\- structured filters are the most reliable input mode
\- live Outscraper testing showed that free-form query parsing may fail with "Could not parse query into a valid request format."

Input parameters:

- `cursor` (string): Pagination cursor from the previous response.
- `fields` (array): Specific fields to return for each business.
- `filters` (object): Structured Outscraper /businesses filters JSON.
- `include_total` (boolean): Whether Outscraper should include total matching count.
- `limit` (integer): Result page size.
- `query` (string): Optional natural-language business search query parsed by Outscraper.

Output parameters:

- `async` (object)
- `data`
- `meta` (object)

### `businesses_get` (~124 tokens)

Outscraper Business Details

Get one business by Outscraper business id.

Best for:
\- loading the full detail payload for a business found via businesses_search
\- fetching a smaller field-selected payload for one known business id

Use this after businesses_search when you already know the exact business id.

Do not use this for discovery:
\- use businesses_search to find records first
\- then call businesses_get for the exact item you want to enrich or inspect

Input parameters:

- `business_id` (string, required): Outscraper business id returned by /businesses search.
- `fields` (array): Specific fields to return.

Output parameters:

- `async` (object)
- `data`
- `meta` (object)

### `google_maps_search` (~337 tokens)

Google Maps Search

Search Google Maps places through Outscraper.

Best for:
\- ad hoc place discovery from one or more Google Maps queries
\- cases where the user thinks in Google Maps terms rather than /businesses filters
\- retrieving place results directly from the Google Maps search pipeline

Prefer this tool when:
\- the user gives Google Maps-style queries such as "restaurants brooklyn usa"
\- you want place discovery without building structured business filters first
\- you want async submissions for larger query batches or enriched Google Maps searches

Use businesses_search instead when:
\- you want normalized businesses filters or cursor pagination
\- you want to combine strict filters with natural-language business search

Use execution_mode="auto" when:
\- there are multiple queries
\- the limit is high
\- enrichments are requested

Input parameters:

- `async` (boolean): Deprecated compatibility flag. Prefer execution_mode.
- `coordinates` (string): Optional latitude,longitude coordinates bias supported by Outscraper.
- `drop_duplicates` (boolean): Drop duplicate places across results.
- `enrichment` (array): Optional enrichment names supported by Outscraper.
- `execution_mode` (string): Execution strategy. Use auto to let the MCP server choose between sync and async.
- `fields` (array): Specific place fields to return.
- `language` (string): Language code, for example en.
- `limit` (integer): Organizations per query limit.
- `query` (array, required): One or more Google Maps queries or place ids.
- `region` (string): Region code, for example us.
- `skip` (integer): Skip places count.
- `webhook` (string): Optional webhook URL for async completion.

Output parameters:

- `async` (object)
- `data`
- `meta` (object)

### `google_maps_reviews` (~379 tokens)

Google Maps Reviews

Fetch Google Maps reviews for place ids or place queries.

Best for:
\- review analysis
\- recent-review monitoring
\- targeted review extraction for specific places

Prefer this tool when:
\- the user needs review text, review counts, or review metadata
\- you already know the place or can identify it from a query
\- async polling is acceptable for heavier review jobs

Use async mode when:
\- review volume is large
\- you query many places in one request
\- you want to poll progress later with requests_get

Do not use this for basic place discovery:
\- use google_maps_search first
\- then use google_maps_reviews once you know the target place or query set

Input parameters:

- `async` (boolean): Deprecated compatibility flag. Prefer execution_mode.
- `cutoff` (string): Cutoff date/timestamp accepted by Outscraper.
- `cutoff_rating` (number): Minimum rating cutoff.
- `execution_mode` (string): Execution strategy. Use auto to let the MCP server choose between sync and async.
- `fields` (array): Specific review fields to return.
- `ignore_empty` (boolean): Skip places without reviews.
- `language` (string): Language code, for example en.
- `last_pagination_id` (string): Resume token from previous page.
- `limit` (integer): Maximum number of places to process.
- `query` (array, required): One or more place ids or Google Maps business queries.
- `region` (string): Region code, for example us.
- `reviews_limit` (integer): Maximum reviews per place.
- `reviews_query` (string): Optional keyword filter inside reviews.
- `sort` (string): Review sorting mode.
- `source` (string): Review source.
- `start` (string): Start date or offset accepted by Outscraper.
- `webhook` (string): Optional webhook URL for async completion.

Output parameters:

- `async` (object)
- `data`
- `meta` (object)

### `google_maps_photos` (~175 tokens)

Google Maps Photos

Fetch Google Maps photos with the documented /google-maps-photos endpoint.

Best for:
\- place photo extraction
\- menu photo retrieval
\- owner photo and latest photo analysis

Input parameters:

- `async` (boolean): Deprecated compatibility flag. Prefer execution_mode.
- `execution_mode` (string): Execution strategy. Use auto to let the MCP server choose between sync and async.
- `fields` (array): Specific fields to return.
- `language` (string): Language code.
- `limit` (integer): Maximum places to process.
- `photos_limit` (integer): Maximum photos per place.
- `query` (array, required): One or more Google Maps place queries or ids.
- `region` (string): Region code.
- `tag` (string): Optional photo filter tag.
- `webhook` (string): Optional webhook URL for async completion.

Output parameters:

- `async` (object)
- `data`
- `meta` (object)

### `google_search` (~172 tokens)

Google Search

Search Google with the documented /google-search endpoint.

Input parameters:

- `async` (boolean): Deprecated compatibility flag. Prefer execution_mode.
- `enrichment` (array): Optional documented enrichments.
- `execution_mode` (string): Execution strategy. Use auto to let the MCP server choose between sync and async.
- `fields` (array): Specific fields to return.
- `language` (string): Language code.
- `pages_per_query` (integer): Pages to fetch per query.
- `query` (array, required): One or more Google search queries.
- `region` (string): Region code.
- `skip` (integer): Skip results.
- `tbs` (string): Optional Google search tbs parameter.
- `uule` (string): Optional Google UULE location string.
- `webhook` (string): Optional webhook URL for async completion.

Output parameters:

- `async` (object)
- `data`
- `meta` (object)

### `google_search_images` (~139 tokens)

Google Search Images

Search Google Images with the documented /google-search-images endpoint.

Input parameters:

- `async` (boolean): Deprecated compatibility flag. Prefer execution_mode.
- `execution_mode` (string): Execution strategy. Use auto to let the MCP server choose between sync and async.
- `fields` (array): Specific fields to return.
- `language` (string): Language code.
- `limit` (integer): Items per query limit.
- `query` (array, required): One or more Google image search queries.
- `region` (string): Region code.
- `uule` (string): Optional Google UULE location string.
- `webhook` (string): Optional webhook URL for async completion.

Output parameters:

- `async` (object)
- `data`
- `meta` (object)

### `yellowpages_search` (~139 tokens)

Yellowpages Search

Search Yellowpages with the documented /yellowpages-search endpoint.

Input parameters:

- `async` (boolean): Deprecated compatibility flag. Prefer execution_mode.
- `enrichment` (array): Optional documented enrichments.
- `execution_mode` (string): Execution strategy. Use auto to let the MCP server choose between sync and async.
- `fields` (array): Specific fields to return.
- `limit` (integer): Maximum results.
- `location` (array): Optional locations paired with the search query.
- `query` (array, required): One or more Yellowpages search queries.
- `region` (string): Region code.
- `webhook` (string): Optional webhook URL for async completion.

Output parameters:

- `async` (object)
- `data`
- `meta` (object)

### `indeed_search` (~113 tokens)

Indeed Search

Search Indeed with the documented /indeed-search endpoint.

Input parameters:

- `async` (boolean): Deprecated compatibility flag. Prefer execution_mode.
- `enrichment` (array): Optional documented enrichments.
- `execution_mode` (string): Execution strategy. Use auto to let the MCP server choose between sync and async.
- `fields` (array): Specific fields to return.
- `limit` (integer): Maximum results.
- `query` (array, required): One or more Indeed search queries.
- `webhook` (string): Optional webhook URL for async completion.

Output parameters:

- `async` (object)
- `data`
- `meta` (object)

### `tripadvisor_search` (~130 tokens)

Tripadvisor Search

Search Tripadvisor with the documented /tripadvisor-search endpoint.

Input parameters:

- `async` (boolean): Deprecated compatibility flag. Prefer execution_mode.
- `execution_mode` (string): Execution strategy. Use auto to let the MCP server choose between sync and async.
- `fields` (array): Specific fields to return.
- `limit` (integer): Maximum results.
- `query` (array, required): One or more Tripadvisor search queries or URLs.
- `search_type` (string): Tripadvisor SearchType parameter from the documented endpoint.
- `skip` (integer): Skip results.
- `webhook` (string): Optional webhook URL for async completion.

Output parameters:

- `async` (object)
- `data`
- `meta` (object)

### `booking_reviews` (~157 tokens)

Booking Reviews

Fetch Booking reviews with the documented /booking-reviews endpoint.

Input parameters:

- `async` (boolean): Deprecated compatibility flag. Prefer execution_mode.
- `cutoff` (string): Cutoff value accepted by Outscraper.
- `execution_mode` (string): Execution strategy. Use auto to let the MCP server choose between sync and async.
- `fields` (array): Specific fields to return.
- `language` (string): Language code.
- `query` (array, required): One or more Booking URLs.
- `region` (string): Region code.
- `reviews_limit` (integer): Maximum reviews per query.
- `skip` (integer): Skip reviews.
- `sort` (string): Booking sort parameter.
- `webhook` (string): Optional webhook URL for async completion.

Output parameters:

- `async` (object)
- `data`
- `meta` (object)

### `yelp_reviews` (~142 tokens)

Yelp Reviews

Fetch Yelp reviews with the documented /yelp-reviews endpoint.

Input parameters:

- `async` (boolean): Deprecated compatibility flag. Prefer execution_mode.
- `cursor` (string): Pagination cursor.
- `cutoff` (string): Cutoff value accepted by Outscraper.
- `execution_mode` (string): Execution strategy. Use auto to let the MCP server choose between sync and async.
- `fields` (array): Specific fields to return.
- `query` (array, required): One or more Yelp business URLs.
- `reviews_limit` (integer): Maximum reviews per query.
- `sort` (string): Yelp sort parameter.
- `webhook` (string): Optional webhook URL for async completion.

Output parameters:

- `async` (object)
- `data`
- `meta` (object)

### `tripadvisor_reviews` (~131 tokens)

Tripadvisor Reviews

Fetch Tripadvisor reviews with the documented /tripadvisor-reviews endpoint.

Input parameters:

- `async` (boolean): Deprecated compatibility flag. Prefer execution_mode.
- `cutoff` (string): Cutoff value accepted by Outscraper.
- `execution_mode` (string): Execution strategy. Use auto to let the MCP server choose between sync and async.
- `fields` (array): Specific fields to return.
- `language` (string): Language code.
- `query` (array, required): One or more Tripadvisor URLs.
- `reviews_limit` (integer): Maximum reviews per query.
- `webhook` (string): Optional webhook URL for async completion.

Output parameters:

- `async` (object)
- `data`
- `meta` (object)

### `tp_data` (~111 tokens)

Trustpilot Data (Legacy Alias)

Legacy alias for trustpilot_data. Prefer trustpilot_data for new integrations.

Input parameters:

- `async` (boolean): Deprecated compatibility flag. Prefer execution_mode.
- `enrichment` (array): Optional documented enrichments.
- `execution_mode` (string): Execution strategy. Use auto to let the MCP server choose between sync and async.
- `fields` (array): Specific fields to return.
- `query` (array, required): One or more Trustpilot domains or review URLs.
- `webhook` (string): Optional webhook URL for async completion.

Output parameters:

- `async` (object)
- `data`
- `meta` (object)

### `trustpilot_data` (~110 tokens)

Trustpilot Data

Fetch Trustpilot business data with the documented /trustpilot endpoint.

Input parameters:

- `async` (boolean): Deprecated compatibility flag. Prefer execution_mode.
- `enrichment` (array): Optional documented enrichments.
- `execution_mode` (string): Execution strategy. Use auto to let the MCP server choose between sync and async.
- `fields` (array): Specific fields to return.
- `query` (array, required): One or more Trustpilot domains or review URLs.
- `webhook` (string): Optional webhook URL for async completion.

Output parameters:

- `async` (object)
- `data`
- `meta` (object)

### `tp_reviews` (~130 tokens)

Trustpilot Reviews (Legacy Alias)

Legacy alias for trustpilot_reviews. Prefer trustpilot_reviews for new integrations.

Input parameters:

- `async` (boolean): Deprecated compatibility flag. Prefer execution_mode.
- `execution_mode` (string): Execution strategy. Use auto to let the MCP server choose between sync and async.
- `fields` (array): Specific fields to return.
- `languages` (array): Language filters.
- `query` (array, required): One or more Trustpilot domains or review URLs.
- `reviews_limit` (integer): Maximum reviews per query.
- `skip` (integer): Skip reviews.
- `webhook` (string): Optional webhook URL for async completion.

Output parameters:

- `async` (object)
- `data`
- `meta` (object)

### `trustpilot_reviews` (~130 tokens)

Trustpilot Reviews

Fetch Trustpilot reviews with the documented /trustpilot-reviews endpoint.

Input parameters:

- `async` (boolean): Deprecated compatibility flag. Prefer execution_mode.
- `execution_mode` (string): Execution strategy. Use auto to let the MCP server choose between sync and async.
- `fields` (array): Specific fields to return.
- `languages` (array): Language filters.
- `query` (array, required): One or more Trustpilot domains or review URLs.
- `reviews_limit` (integer): Maximum reviews per query.
- `skip` (integer): Skip reviews.
- `webhook` (string): Optional webhook URL for async completion.

Output parameters:

- `async` (object)
- `data`
- `meta` (object)

### `emails_validator` (~107 tokens)

Emails Validator

Validate email addresses with the documented /email-validator endpoint.

Best for:
\- deliverability checks
\- validating outbound lead lists
\- filtering invalid email inputs before enrichment or outreach

Input parameters:

- `async` (boolean): Deprecated compatibility flag. Prefer execution_mode.
- `execution_mode` (string): Execution strategy. Use auto to let the MCP server choose between sync and async.
- `query` (array, required): One or more email addresses to validate.
- `webhook` (string): Optional webhook URL for async completion.

Output parameters:

- `async` (object)
- `data`
- `meta` (object)

### `phones_enricher` (~72 tokens)

Phones Enricher

Enrich phone numbers using the documented /phones-enricher endpoint.

Best for:
\- carrier lookup
\- phone validation
\- message deliverability checks

Note: this endpoint is synchronous only and does not support async execution or webhooks.

Input parameters:

- `query` (array, required): One or more phone numbers to enrich.

Output parameters:

- `async` (object)
- `data`
- `meta` (object)

### `chain_info` (~144 tokens)

Chain Info

Detect chain membership using the documented ai_chain_info enrichment.

This tool uses the documented enrichment on top of the Google Maps search pipeline.
Use it when you want to know whether a business is part of a chain.

Input parameters:

- `async` (boolean): Deprecated compatibility flag. Prefer execution_mode.
- `execution_mode` (string): Execution strategy. Use auto to let the MCP server choose between sync and async.
- `language` (string): Language code.
- `limit` (integer): Organizations per query limit.
- `query` (array, required): One or more Google Maps-style business queries.
- `region` (string): Region code.
- `webhook` (string): Optional webhook URL for async completion.

Output parameters:

- `async` (object)
- `data`
- `meta` (object)

### `company_insights` (~291 tokens)

Company Insights

Get structured company-level insight data from Outscraper.

Best for:
\- enriching known companies or domains
\- pulling structured company metadata instead of raw search results
\- larger async enrichment jobs that can be tracked later with requests_get

Prefer this tool when:
\- the user already has domains or company URLs
\- the goal is firmographics, company profile data, size, revenue, industry, or founding details
\- you want structured company enrichment rather than contact extraction

Use async mode when:
\- you send many companies at once
\- the endpoint is expected to do expensive enrichment work

Use emails_and_contacts instead when:
\- the user mainly wants emails, phones, socials, or people/contact data
\- company profile enrichment is secondary to lead/contact discovery

Returns:
\- direct response payload in sync mode
\- async request metadata in async mode

Input parameters:

- `async` (boolean): Deprecated compatibility flag. Prefer execution_mode.
- `enrichments` (array): Optional enrichments supported by Outscraper for company insights.
- `execution_mode` (string): Execution strategy. Use auto to let the MCP server choose between sync and async.
- `fields` (array): Specific company insight fields to return. Leave empty to receive the default payload.
- `query` (array, required): One or more company domains, company names, or URLs supported by Outscraper.
- `webhook` (string): Optional webhook URL for async completion.

Output parameters:

- `async` (object)
- `data`
- `meta` (object)

### `emails_and_contacts` (~249 tokens)

Emails And Contacts

Find emails, phones, and social/contact data from one or more company domains.

Best for:
\- domain-based lead enrichment
\- finding reachable company contacts from a known website
\- quick contact discovery before running heavier enrichment flows

Prefer this tool when:
\- the user already knows the company website or domain
\- the main goal is contact discovery rather than company metadata
\- you want emails, phones, socials, and website-derived contact details

Use async mode when:
\- you send many domains at once
\- you expect the crawl/enrichment to take longer
\- you want to track progress later with requests_get

Use company_insights instead when:
\- the user wants firmographics, company profile, revenue, size, or founding details
\- contact data is not the main objective

Input parameters:

- `async` (boolean): Deprecated compatibility flag. Prefer execution_mode.
- `execution_mode` (string): Execution strategy. Use auto to let the MCP server choose between sync and async.
- `preferred_contacts` (array): Optional contact-role prioritization.
- `query` (array, required): One or more domains or URLs, for example outscraper.com.
- `webhook` (string): Optional webhook URL for async completion.

Output parameters:

- `async` (object)
- `data`
- `meta` (object)

### `ping` (~60 tokens)

Outscraper Ping

Check whether the Outscraper MCP server is running and return basic server metadata.

Best for:
\- validating local or container startup
\- confirming the MCP server is reachable before making live API calls
\- lightweight health checks in demos, IDE setups, or registry validation

Output parameters:

- `async` (object)
- `data`
- `meta` (object)

### `balance_get` (~102 tokens)

Outscraper Balance

Fetch the current Outscraper account balance and billing summary for the active API key.

Best for:
\- checking whether the key is attached to a funded account
\- confirming account status before running larger jobs
\- reading upcoming invoice and usage billing details

Use this when:
\- you want a quick health check for the current API key/account
\- you need to confirm available balance before large async jobs
\- you are debugging whether billing or account status might explain API behavior

Output parameters:

- `async` (object)
- `data`
- `meta` (object)

### `requests_get` (~143 tokens)

Outscraper Request Status

Check the status of an asynchronous Outscraper request.

Use this after calling any tool with execution_mode="async" or after an auto-selected async submission.
Typical flow:
1\. call google_maps_reviews, company_insights, emails_and_contacts, or google_maps_search with execution_mode="async"
2\. capture the returned request id
3\. poll requests_get until the job is completed or failed

Use this tool when:
\- a previous tool returned an async request id
\- you want to know whether the request is Pending, Success, or Failure
\- you need the completed data from a previously submitted async job

Input parameters:

- `request_id` (string, required): Async request id.

Output parameters:

- `async` (object)
- `data`
- `meta` (object)

### `requests_list` (~96 tokens)

Outscraper Request History

List recent Outscraper requests by bucket.

Best for:
\- debugging async flows
\- seeing running, completed, or failed jobs
\- checking what was recently submitted through the current API key

Use this when:
\- you lost a request id and want to find recent jobs
\- you want a quick view of recent running or finished requests
\- you are debugging async submissions across tools

Input parameters:

- `type` (string): Optional request bucket.

Output parameters:

- `async` (object)
- `data`
- `meta` (object)

### `requests_delete` (~114 tokens)

Outscraper Request Delete

Delete or terminate an asynchronous Outscraper request by request id.

Best for:
\- cleaning up queued or no-longer-needed async jobs
\- stopping work you no longer want to keep polling
\- testing the full async request lifecycle from MCP

Use this carefully:
\- it is intended for cleanup or cancellation
\- only use it when you are sure the request is no longer needed
\- after deletion, the original async request should not be expected to complete normally

Input parameters:

- `request_id` (string, required): Async request id to delete.

Output parameters:

- `async` (object)
- `data`
- `meta` (object)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/outscraper-outscraper-mcp-server/outscraper-mcp#diagnostics

## Score history

- 2026-08-03: 63
- 2026-08-02: 63
- 2026-08-01: 19
- 2026-07-31: 26
- 2026-07-30: 39
- 2026-07-28: 44
- 2026-07-27: 44

## Links

- npm package: https://www.npmjs.com/package/outscraper-mcp
- Socket report: https://socket.dev/npm/package/outscraper-mcp
- Repository: https://github.com/outscraper/outscraper-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/outscraper-outscraper-mcp-server/outscraper-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/outscraper-outscraper-mcp-server/outscraper-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/outscraper-outscraper-mcp-server/outscraper-mcp