metasearch MCP

tr.com.metasearchv1.1.0更新於 Oct 8, 2026

Hotel and travel feed validation, normalization and requirement comparison.

已驗證Streamable HTTP可網頁執行Business & CommerceData & Analytics

概覽

AI 產生的概覽

讓助理驗證、正規化並比較飯店與旅遊資料饋送，對照 Google Hotel Center、Wego、trivago 等平台要求。

功能
這是一個針對飯店資料饋送工作流程的遠端 MCP 伺服器。其工具可偵測結構化饋送格式、正規化常見飯店欄位別名、執行依目標區分的驗證，並比較 Google Hotel Center、Wego、trivago、Meta Catalog、Criteo Catalog 等平台的就緒度或要求，另含通用飯店主資料品質檢查。它也會提供確定性的修復建議。
適用情境
適合在把飯店庫存饋送提交到旅遊或商品目錄平台之前進行準備或稽核，也適合比較不同平台的要求。亦可用於正規化雜亂的飯店資料集，並說明缺少或無效的欄位。
執行需求
遠端 streamable HTTP 端點，不需要安裝套件或本機執行環境。未宣告驗證、環境變數或標頭。用戶端需能透過網路連線至該遠端端點。
安裝前請注意
饋送內容會提交給第三方遠端服務；供應商聲稱不保存饋送內容、遙測僅記錄工具名稱與目標，但這只是供應商自述。請勿把憑證或密鑰當作饋送內容傳送。該伺服器聲明為獨立服務，並非所列平台的官方認證服務。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 metasearch MCP，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "metasearch-mcp": {
      "type": "http",
      "url": "https://metasearch.com.tr/mcp"
    }
  }
}

README

metasearch MCP

[Validate MCP metadata] [License: MIT]

Remote Model Context Protocol (MCP) server for hotel and travel feed validation, normalization, readiness checks, and platform requirement comparison.

Operated by metasearch.com.tr and published under the domain-owned MCP Registry identity:

text
tr.com.metasearch/metasearch-mcp

Remote endpoint:

text
https://metasearch.com.tr/mcp

The server is independent and is not an official certification service for Google, Wego, trivago, Meta, or Criteo.

What it does

The server gives AI agents deterministic tools for hotel-feed workflows:

  • detect structured feed formats,
  • normalize common hotel field aliases,
  • validate hotel feeds,
  • compare readiness across platforms,
  • compare platform requirements,
  • suggest remediation steps.

Validation targets

TargetMode
Google Hotel CenterPublished-contract validation
Wego HotelsPublished-contract validation
trivago hotel dataPublished-contract validation
Meta CatalogReadiness / mapping pre-check
Criteo CatalogReadiness / mapping pre-check
Generic hotel master dataPlatform-independent quality check

Published-contract and readiness modes are deliberately kept separate. Undocumented mandatory fields are not invented.

Connect

Claude Code

bash
claude mcp add --transport http metasearch https://metasearch.com.tr/mcpclaude mcp list

Cursor

Add to .cursor/mcp.json:

json
{  "mcpServers": {    "metasearch": {      "url": "https://metasearch.com.tr/mcp"    }  }}

VS Code / GitHub Copilot

Add to .vscode/mcp.json:

json
{  "servers": {    "metasearch": {      "type": "http",      "url": "https://metasearch.com.tr/mcp"    }  }}

Additional setup examples live under examples/.

Available tools

ToolPurpose
detect_feed_formatDetect supported structured feed formats
normalize_hotel_feedNormalize common hotel field aliases
validate_feedRun target-aware validation
validate_google_hotel_center_listValidate Google Hotel Center hotel-list data
validate_wego_hotel_feedValidate Wego hotel-feed data
validate_trivago_hotel_dataValidate trivago hotel data
validate_meta_catalogRun Meta catalog readiness checks
validate_criteo_catalogRun Criteo catalog readiness checks
validate_hotel_master_dataRun generic hotel master-data quality checks
compare_feed_readinessCompare feed readiness across targets
compare_platform_requirementsCompare target requirements
suggest_feed_fixesProduce deterministic remediation guidance

See docs/tools.md for details.

Example prompts

Examples include:

  • "Validate this hotel CSV for Google Hotel Center."
  • "Compare this feed against Wego and trivago requirements."
  • "Normalize this hotel dataset and show missing fields."
  • "Explain how to fix the validation errors without inventing unsupported fields."

See examples/prompts.md.

Privacy and data handling

The validation workflow is designed not to persist submitted feed payloads. Operational telemetry records tool name and explicit target only; it does not intentionally record feed contents.

Do not send credentials or secrets as feed content. See docs/privacy-and-security.md and SECURITY.md.

Official MCP Registry

The canonical registry descriptor is server.json.

Registry identity:

text
tr.com.metasearch/metasearch-mcp

The namespace is authenticated using ownership of metasearch.com.tr.

Companion CLI and Node.js SDK

For local development and CI pipelines, use @metasearch/feed-validator:

bash
npx @metasearch/feed-validator validate hotels.csv --target google-hotel-center

Source: metasearchcomtr/feed-validator

Documentation

Contributing

Issues and focused pull requests are welcome. See CONTRIBUTING.md.

License

MIT. See LICENSE.

來源：README.md，提交 d7b2b9e

工具

0
工具後設資料尚未被收錄。

版本歷史

1
  1. v1.1.0最新Oct 8, 2026