English Français العربية

metasearch MCP

Official registry Maps, travel and weather

Hotel and travel feed validation, normalization and requirement comparison.

Source code Website Documentation

What can you do with metasearch MCP?

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

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http metasearch-mcp 'https://metasearch.com.tr/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "metasearch-mcp": {
            "type": "http",
            "url": "https://metasearch.com.tr/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. metasearch MCP
  2. What it does
  3. Validation targets
  4. Connect
  5. Available tools
  6. Example prompts
  7. Privacy and data handling
  8. Registry and discovery
  9. Companion CLI and Node.js SDK
  10. Documentation
  11. Contributing
  12. License

metasearch MCP

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:

tr.com.metasearch/metasearch-mcp

Remote endpoint:

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 validation and readiness checks are deliberately kept separate. Undocumented mandatory fields are not invented.

Connect

Claude Code
claude mcp add --transport http metasearch https://metasearch.com.tr/mcp
claude mcp list
Cursor

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "metasearch": {
      "url": "https://metasearch.com.tr/mcp"
    }
  }
}
VS Code / GitHub Copilot

Add to .vscode/mcp.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.

Registry and discovery

The canonical registry descriptor is server.json.

Registry identity:

tr.com.metasearch/metasearch-mcp

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

For third-party registry and directory submissions, use the canonical metadata in docs/discovery.md. This keeps names, descriptions, categories, endpoint details and privacy claims consistent across listings.

Companion CLI and Node.js SDK

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

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.

Frequently asked questions

What is metasearch MCP?

Hotel and travel feed validation, normalization and requirement comparison.

How do I install metasearch MCP?

It runs as a remote server. In Claude Code: claude mcp add --transport http metasearch-mcp 'https://metasearch.com.tr/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does metasearch MCP need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is metasearch MCP open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains metasearch MCP?

It is published by metasearchcomtr. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.