Thordata SERP MCP Server

Name: Thordata SERP MCP Server
Author: Thordata

by Thordataversion 0.1.0i★ –iRuns in the cloud

Registry nameio.github.Thordata/thordata-mcp

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Search & AI memory
You need to fill in: Authorization

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: Authorization

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Run this in your terminal

claude mcp add --transport http thordata https://mcp.thordata.com/mcp --header 'Authorization: your-value'

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "thordata": {
      "url": "https://mcp.thordata.com/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "thordata": {
      "type": "http",
      "url": "https://mcp.thordata.com/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

Authorization secret required HTTP header
Thordata SERP API key using the Bearer scheme.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account Thordata, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Search & AI memoryi

More stars than 0% of the other 7259 servers in this category
Published to the registry more recently than 73% of the other 7259 servers in this category
Basic checks equal to or better than 100% of the other 7259 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Thordata SERP MCP Server safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: Authorization

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 14 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated yesterday

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 20 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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:

https://mcp.thordata.com/YOUR_API_KEY/mcp

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

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

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

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

For a Claude Code one-line install, run:

claude mcp add --transport http thordata https://mcp.thordata.com/YOUR_API_KEY/mcp

3. Make your first request

A typical call flow is:

Read the thordata://engines resource to list supported engines.
Read thordata://engines/ 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:

"ok": true, "status": 200, "engine": "google", "data": {} }

`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

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

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.

Thordata SERP MCP Server

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

Thordata MCP Server

Official MCP Registry

Quick start

1. Get your API key

2. Connect your MCP client

3. Make your first request

What you can do

Authentication

Tools

list_engines

search

history

statistics

Resources

Building correct parameters

Error handling

`list_engines`

`search`

`history`

`statistics`