workingproxysites.
[ new post ]
[ menu ]

directory

boards

[all]

information

Provider integration · Official publisher

Thordata MCP

Thordata’s hosted MCP integration is focused on search-engine results. It suits research that needs current result pages or regional comparisons, with usage inspection alongside search. Use the SERP API account and connection documented here for that scope.

Server publisher: Thordata. Guide maintained by Working Proxy Sites.

Documentation reviewed · Next review

What you can use it for

  • Collect search-result evidence for a research question.
  • Compare localized search results using the chosen engine’s parameters.
  • Review the account’s SERP activity after a search workflow.

Documented capabilities: Web search.

Account & usage

Account required
Yes
Required product
Thordata SERP API.
Billing basis
SERP plans provide response allowances. The billing guide charges successful HTTP 200 searches, including successful responses with few or no matching results; other status codes are not billed. Provider pricing.

When to choose Thordata MCP

A useful fit when

  • Collecting source candidates for a current research question.
  • Comparing a query across target markets using supported search parameters.

Check another approach when

  • A workflow needing arbitrary page extraction or interactive browser actions from this integration.
  • Managing residential proxy credentials through the documented SERP tools.
Sources: Thordata official MCP product page, Thordata MCP quickstart and tools

Connect to Thordata MCP

Choose a connection profile below and replace credential placeholders in your own MCP client. The transport describes the MCP connection.

Hosted SERP MCP

Streamable HTTP · hosted

Endpoint
https://mcp.thordata.com/YOUR_API_TOKEN/mcp
Authentication
Thordata SERP API token replaces YOUR_API_TOKEN in the endpoint path.

Before you connect

  • Thordata account with SERP API access and available request allowance.
  • SERP API token from the dashboard.
  • An MCP client supporting remote HTTP connections.

Cursor mcp.json (JSON) Sources: Thordata official MCP product page, Thordata MCP quickstart and tools, Cursor MCP configuration reference

Cursor: .cursor/mcp.json (project) or ~/.cursor/mcp.json (global). Configuration guide.

{
  "mcpServers": {
    "thordata": {
      "type": "http",
      "url": "https://mcp.thordata.com/YOUR_API_TOKEN/mcp"
    }
  }
}

Compare a search topic across markets with Thordata

A suggested sequence using the documented tools. Check the connected server's tool schema before making a call.

  1. Choose the research scope

    Decide which markets and language settings matter before starting. Keep the question consistent so results can be compared.

    Tools: list_engines

    Sources: Thordata official MCP product page

  2. Prepare and run the searches

    Read the selected engine’s schema, then submit each market’s parameter set. Keep source URLs alongside the returned evidence.

    Tools: search

    Sources: Thordata MCP quickstart and tools, Thordata SERP API account setup

  3. Review request activity

    After the research pass, inspect history and usage statistics. Use the billing guide when interpreting successful versus rejected requests.

    Tools: history, statistics

    Sources: Thordata MCP quickstart and tools, Thordata SERP billing instructions

Selected tools & example tasks

Troubleshoot the connection

A successful request used allowance despite a short result set

Billing follows a successful HTTP 200 response, rather than the number of matches returned. Check the account’s response allowance before running a large set of queries.

Sources: Thordata SERP billing instructions, Thordata SERP API pricing

Limits & undocumented behavior

  • This record covers the hosted SERP integration. The reviewed tools do not establish general page extraction, browser control or proxy-account management.
  • The documented connection places the API token in the URL path. Treat the completed URL as a credential and keep shared examples placeholder-only.
  • Engine-specific search parameters must follow the corresponding schema resource. A field accepted by one engine may not apply to another.

Thordata MCP: questions & answers

Which Thordata product does this MCP use?

This setup uses the SERP API. Other Thordata scraping and proxy products have their own interfaces and requirements.

Sources: Thordata official MCP product page, Thordata SERP API account setup
Do I need to install a Python package?

The documented hosted setup uses a remote URL in an MCP client. This listing does not require a local Python server.

Sources: Thordata official MCP product page, Cursor MCP configuration reference
How is SERP usage billed?

The published plans allocate responses. The billing guide treats HTTP 200 searches as chargeable independently of the number of results, and lists other status codes as unbilled.

Sources: Thordata SERP API pricing, Thordata SERP billing instructions

Sources & review history

This listing is documentation-confirmed. We reviewed the primary sources below; this is not a successful live connection test.

Record updated . Review due .

  1. Thordata official MCP product pageChecked · Provider-maintained hosted integration and .com token-path template; Search-oriented scope and localized research uses
  2. Thordata MCP quickstart and toolsChecked · Endpoint authentication, exact tool names and engine schema resources
  3. Thordata SERP API account setupChecked · Account activation, API token and search configuration
  4. Thordata SERP billing instructionsChecked · Successful-request charging and error-status meanings
  5. Thordata SERP API pricingChecked · SERP response allowances and commercial plans
  6. Cursor MCP configuration referenceChecked · Remote HTTP client configuration format

Spotted a change? Share the source and the affected setup step in Site Feedback.

Alternatives to Thordata MCP

These integrations share documented capabilities with Thordata MCP. Compare their setup and product requirements for your task.

Apify MCP

Find Apify Actors, inspect their inputs and pricing, run a selected Actor, and retrieve its dataset through the official MCP server.

Shared capabilities
Web search
Connection choices
Streamable HTTP · Local stdio
Product to check
Apify Actors and platform usage
Compare setup & authentication →

Bright Data MCP

Search the public web, retrieve page content and use optional browser tools through Bright Data’s hosted or local MCP integration.

Shared capabilities
Web search
Connection choices
Streamable HTTP · Local stdio
Product to check
Bright Data Web Unlocker API; additional products may be used by optional tools.
Compare setup & authentication →

Decodo MCP

Retrieve pages, search results and supported structured targets through Decodo’s Web Scraping API.

Shared capabilities
Web search
Connection choices
Streamable HTTP
Product to check
Decodo Web Scraping API.
Compare setup & authentication →

Evomi MCP

Inspect Evomi proxy products, targeting and usage, rotate sessions, and run scraping jobs through a local Python MCP server.

Shared capabilities
Web search
Connection choices
Local stdio
Product to check
Evomi Public API access plus the proxy or Scraper API product used by the tool.
Compare setup & authentication →