Server data from the Official MCP Registry
Hotel and travel feed validation, normalization and requirement comparison.
About
Hotel and travel feed validation, normalization and requirement comparison.
Remote endpoints: streamable-http: https://metasearch.com.tr/mcp
Security Report
Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.
12 tools verified · Open access · No issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Found in Source Code
Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.
How to Connect
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"tr-com-metasearch-metasearch-mcp": {
"url": "https://metasearch.com.tr/mcp"
}
}
}Documentation
View on GitHubFrom the project's GitHub README.
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
| Target | Mode |
|---|---|
| Google Hotel Center | Published-contract validation |
| Wego Hotels | Published-contract validation |
| trivago hotel data | Published-contract validation |
| Meta Catalog | Readiness / mapping pre-check |
| Criteo Catalog | Readiness / mapping pre-check |
| Generic hotel master data | Platform-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
| Tool | Purpose |
|---|---|
detect_feed_format | Detect supported structured feed formats |
normalize_hotel_feed | Normalize common hotel field aliases |
validate_feed | Run target-aware validation |
validate_google_hotel_center_list | Validate Google Hotel Center hotel-list data |
validate_wego_hotel_feed | Validate Wego hotel-feed data |
validate_trivago_hotel_data | Validate trivago hotel data |
validate_meta_catalog | Run Meta catalog readiness checks |
validate_criteo_catalog | Run Criteo catalog readiness checks |
validate_hotel_master_data | Run generic hotel master-data quality checks |
compare_feed_readiness | Compare feed readiness across targets |
compare_platform_requirements | Compare target requirements |
suggest_feed_fixes | Produce 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
- MCP documentation
- Hotel Feed Validator
- Hotel feed requirements comparison
- Validate hotel feeds with MCP
- Client setup
- Troubleshooting
- Discovery metadata
- Changelog
Contributing
Issues and focused pull requests are welcome. See CONTRIBUTING.md.
License
MIT. See LICENSE.
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Fetch
Freeby Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
mcp-creator-python
Freeby mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
FinAgent
Freeby mcp-marketplace · Finance
Free stock data and market news for any MCP-compatible AI assistant.