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