Thordata SERP MCP Server

io.github.ThordataPublished by GitHub account Thordatav0.1.0Updated Oct 24, 2026

Thordata SERP search, history, statistics, and engine schemas for MCP clients.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping Data & Analytics

Server details

Identifier: io.github.Thordata/thordata-mcp
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Oct 24, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account Thordata for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.Thordata%2Fthordata-mcp.svg)](https://sourceweft.com/mcp/io.github.Thordata%2Fthordata-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Hosted Thordata SERP MCP server that lets an assistant run live search-engine queries and review its own search history and usage statistics.

What you can do: Run real-time SERP searches on supported engines such as Google, Google Images, Google Maps and Bing, with engine-specific parameters and JSON or HTML response formats.
List available engines and read per-engine schema resources to build valid query parameters.
Query SERP request history for the API key's account, filtered by query, engine, status and time range.
Query SERP usage statistics for a date range, optionally per engine and timezone.
When to use it: Use it when an assistant needs live search-engine results rather than a static index, or when you want to check how much SERP quota an account has used. It is a hosted endpoint, so it suits clients that can connect to a remote MCP URL without installing anything.
Requirements: A remote MCP endpoint at mcp.thordata.com; no local install or build. A Thordata SERP API key from the Thordata dashboard, supplied either in the connection URL path or as an Authorization Bearer header (an X-Thordata-Serp-Token header is also listed as compatible). Network access to the hosted endpoint.

Before you install

The API key is a paid-service credential: searches consume Thordata SERP quota and may incur charges. The default setup puts the key in the URL path, which the README notes can appear in access logs and referrers, so prefer the Authorization header where supported. History and statistics expose account usage data for the key's owner; the key is forwarded per request to Thordata.

Installation

In SourceWeft

Open Thordata SERP MCP Server in the dashboard and add it to a workspace.
Connect Authorization token credentials. They are stored privately and never shown on public pages.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Thordata%2Fthordata-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "thordata-serp": {
      "type": "http",
      "url": "https://mcp.thordata.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

Thordata MCP Server

Connect Thordata SERP to MCP-compatible AI agents and clients for real-time search, usage history, and statistics.

The Thordata SERP MCP Server exposes Thordata search capabilities through the Model Context Protocol (MCP), making it easy to integrate live search tools into agents, workflows, and MCP clients. In addition to real-time SERP requests, it also provides access to search history, usage statistics, and engine schema resources for richer integrations.

Official MCP Registry

This server is published in the official MCP Registry as io.github.Thordata/thordata-mcp.

View the official Registry entry

The Registry entry points to the hosted Thordata MCP endpoint and provides standardized connection metadata for compatible clients.

Quick start

Most users connect to the hosted Thordata MCP endpoint — no installation, no local build. You only need a Thordata SERP API key.

1. Get your API key

2. Connect your MCP client

Point your MCP client at the hosted endpoint and put your API key in the URL path. Your key is used per request; Thordata never stores a shared credential on your behalf.

The default connection URL is:

Replace YOUR_API_KEY with your Thordata SERP API key and use this MCP client configuration:

json

{  "mcpServers": {    "thordata": {      "url": "https://mcp.thordata.com/YOUR_API_KEY/mcp"    }  }}

{  "mcpServers": {    "thordata": {      "url": "https://mcp.thordata.com/YOUR_API_KEY/mcp"    }  }}

If your client supports custom headers, you can instead use the Bearer configuration:

json

{  "mcpServers": {    "thordata": {      "url": "https://mcp.thordata.com/mcp",      "headers": {        "Authorization": "Bearer YOUR_API_KEY"      }    }  }}

{  "mcpServers": {    "thordata": {      "url": "https://mcp.thordata.com/mcp",      "headers": {        "Authorization": "Bearer YOUR_API_KEY"      }    }  }}

For a Claude Code one-line install, run:

3. Make your first request

A typical call flow is:

Read the thordata://engines resource to list supported engines.
Read thordata://engines/<engine-key> for the engine you want.
Build params from that engine's schema.
Call the search tool.

What you can do

search — run a real-time SERP search on any supported engine.
list_engines — see the current engine list, query field, and schema resources.
history — query SERP request history for your own account.
statistics — query SERP usage statistics for your own account.

History and statistics are scoped to the API key you send; you cannot query another user's data.

Authentication

Supported token delivery methods:

Default: https://mcp.thordata.com/YOUR_API_KEY/mcp (token in the path).
Optional: Authorization: Bearer YOUR_API_KEY with https://mcp.thordata.com/mcp.
Compatible: X-Thordata-Serp-Token: YOUR_API_KEY.

Notes:

The hosted path-token URL is the default connection method.
The Bearer form is available for clients that support custom headers.
A path token can appear in access logs and referrers, so the hosted endpoint always uses HTTPS.
Query-string tokens are not accepted.
Your API key is forwarded per request and is never included in MCP result metadata; it is redacted from returned data and error text.
Your engine availability and access level are decided by the Thordata SERP service using your API key.

Tools

`list_engines`

Returns the current schema version, audience, default engine, engine list, query field for each engine, and its resource URI.

`search`

Executes a Thordata SERP search request.

Parameter	Required	Description
`engine`	No	Thordata engine key such as `google`, `google_images`, `google_maps`, or `bing`. The schema default is used when omitted.
`q`	No	Convenience search input. It is mapped to the engine's declared query field when that field is not `q`.
`json`	No	Response format: `1`, `2`, or `3`. Defaults to `1`.
`params`	No	Engine-specific parameters defined by the engine resource. Unsupported keys are ignored.
`response_mode`	No	`complete` or `compact`. Compact mode removes common metadata fields.

A successful result uses this envelope:

`history`

Queries SERP request history for the API-key owner.

Parameter	Required	Description
`page`	No	Page number. Defaults to `1`.
`page_size`	No	Page size. Defaults to `20`.
`search_query`	No	Search query filter.
`search_engine`	No	Thordata engine-key filter.
`status`	No	`all`, `success`, or `error`. Defaults to `all`.
`start_time`	No	Start time in Unix seconds.
`end_time`	No	End time in Unix seconds.
`timezone`	No	IANA timezone or numeric offset.

`statistics`

Queries SERP usage statistics for the API-key owner.

Parameter	Required	Description
`start_date`	Yes	Start date in `YYYY-MM-DD`.
`end_date`	Yes	End date in `YYYY-MM-DD`.
`engines`	No	Comma-separated engine string or string array.
`timezone`	No	IANA timezone or offset such as `+08:00`.

Resources

Building correct parameters

Only fields declared by the selected engine schema are sent. When you build a request:

The final engine value is always the selected engine key.
Top-level q and json override values with the same names in params; json defaults to 1.
Null values, empty strings, and empty arrays are omitted. Numeric zero and boolean false are preserved.

Serialization rules by field type:

string and options values are sent as they are; Google Flights departure_id and arrival_id are normalized to uppercase.
boolean (switch) values are serialized as true or false.
number values are serialized as strings.
array (multi_select) values are joined with commas, and every element must be a scalar. The country restriction field cr is declared as an array in the current schemas, so it is sent comma-joined exactly as given.
object values are serialized as JSON.
Unknown parameters are ignored, and the selected engine remains authoritative.

Response format:

json=1: structured JSON only.
json=2: JSON and HTML when supported.
json=3: HTML only when supported.

complete mode returns the full result; compact mode strips common metadata fields.

Error handling

The server normalizes responses and surfaces failures as MCP tool errors:

Successful business codes are treated as success; all other non-success codes, non-2xx responses, transport failures, and error text are treated as failures.
Double-encoded JSON payloads are unwrapped, and user tokens are redacted before results or errors are returned to you.

Source: README.md at commit 47a9e61

Tools

This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

v0.1.0LatestOct 24, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts

Resource	Description
`thordata://engines`	Index of the current supported engine definitions.
`thordata://engines/<engine-key>`	Groups, fields, controls, defaults, options, and conditions for one engine.