Metasearch MCP Server

Remote endpoint

MCP

https://metasearch.com.tr/mcp

Registry: tr.com.metasearch/metasearch-mcp

Connection model

Feed content is sent with the tool call. The public MCP endpoint currently requires no authentication and does not intentionally persist validation payloads.

Client setup guide GitHub

MCP tools

The same canonical feed engine powers format detection through platform validation.

detect_feed_format

normalize_hotel_feed

validate_feed

validate_wego_hotel_feed

validate_google_hotel_center_list

validate_trivago_hotel_data

validate_meta_catalog

validate_criteo_catalog

validate_hotel_master_data

compare_feed_readiness

compare_platform_requirements

suggest_feed_fixes

Resources

metasearch://about

metasearch://schema/canonical-hotel

metasearch://platform/wego

metasearch://platform/google-hotel-center

metasearch://platform/trivago

metasearch://platform/meta-catalog

metasearch://platform/criteo

metasearch://platform/hotel-master-data

Example agent flow

Detect the format of supplier_hotels.csv.
Normalize it to the canonical hotel model.
Compare Google Hotel Center, trivago and Wego requirements.
Validate the feed for each platform and suggest fixes.

Discovery and metadata

Registry server.json MCP Server Card AI Catalog Feed requirements

Discovery status

/mcp/server.json follows the MCP Registry format. /mcp/server-card and /.well-known/ai-catalog.json implement the experimental MCP Server Card / AI Catalog discovery approach and are not presented as mandatory core MCP protocol endpoints.

Meta and Criteo tools are readiness/mapping pre-checks, not official platform certification. Wego, Google Hotel Center and trivago checks derive from published requirements but do not replace each platform's own onboarding or validation process.