Thordata SERP MCP Server

Name: Thordata SERP MCP Server
Author: Thordata

作者：Thordata版本 0.1.0i★ –i在云端运行

注册名称io.github.Thordata/thordata-mcp

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在云端运行
传输方式: Streamable HTTP
分类: 搜索与 AI 记忆
你需要填写：Authorization

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
需要你自己填写： Authorization

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

这个地址需要在请求的 header 中放入密钥，而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

在终端中运行这条命令

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

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个地址需要在请求的 header 中放入密钥，而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

Authorization 机密必填 HTTP header
Thordata SERP API key using the Bearer scheme.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

我们还没有读取这个服务器的工具列表；我们会轮流检查各个端点。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 Thordata 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
… 尚未检查
端点有响应
尚未检查；我们会轮流检查各个端点
… 尚未检查
使用 OAuth 登录
尚未检查；我们会轮流检查各个端点
… 尚未检查
工具描述中没有隐藏指令
尚未检查；我们会在检查端点时读取工具列表

与“搜索与 AI 记忆”中的其他服务器比较i

星标数多于此分类中其他 7264 个服务器的 0%
发布到注册中心的时间比此分类中其他 7264 个服务器的 73% 更新
基础检查结果等于或优于此分类中其他 7264 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Thordata SERP MCP Server 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：Authorization

它在我的电脑上运行还是在云端？

它在作者的云端运行。通过互联网连接，无需安装，但你发送的内容会经过作者的服务器。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.1.0）于14天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。

有什么可以替代它？

同一分类中有：Context7, Codebase Memory, Exa

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Context7

作者：upstash

Up-to-date docs for AI agents

电脑或云端★ 64,224MIT昨天更新

安装

Codebase Memory

作者：DeusData

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

在你的电脑上运行★ 48,148MIT21天前更新

安装

Exa

作者：exa-labs

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

在云端运行★ 5,213MIT上个月更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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.