metasearch MCP

tr.com.metasearchv1.1.0Updated Oct 8, 2026

Hotel and travel feed validation, normalization and requirement comparison.

VerifiedStreamable HTTPWeb executableBusiness & CommerceData & Analytics

Overview

AI-generated overview

Lets an assistant validate, normalize and compare hotel and travel feeds against platform requirements such as Google Hotel Center, Wego and trivago.

What it does
A remote MCP server for hotel-feed workflows. Tools detect structured feed formats, normalize common hotel field aliases, run target-aware validation, and compare readiness or requirements across platforms including Google Hotel Center, Wego, trivago, Meta Catalog and Criteo Catalog, plus a generic hotel master-data quality check. It also produces deterministic remediation suggestions for validation errors.
When to use it
Useful when preparing or auditing hotel inventory feeds before submitting them to travel or catalog platforms, or when comparing what different platforms require. Also suited to normalizing messy hotel datasets and explaining missing or invalid fields.
Requirements
A remote streamable HTTP endpoint; no package or local runtime is needed. No authentication, environment variables or headers are declared. The assistant or client must be able to reach the remote endpoint over the network.
Before you install
Feed payloads are submitted to a third-party remote service; the provider states payloads are not persisted and telemetry records only tool name and target, but this is the provider's own claim. Do not send credentials or secrets as feed content. The server is stated to be independent and not an official certification service for the named platforms.

Installation

In SourceWeft

  1. Open metasearch MCP in the dashboard and add it to a workspace.
  2. 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.

Other MCP clients

Add this to your client's mcpServers config.

{
  "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.

Source: README.md at commit d7b2b9e

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.1.0LatestOct 8, 2026