Remote MCP server for hotel and travel feed validation, normalization and platform requirement comparison.
- ✓Open-source license (MIT)
- ✓Actively maintained (<30d)
- ✓Clear description
- ✓Topics declared
- ✓Documented (README)
claude mcp add metasearch-mcp -- npx -y @metasearch/feed-validator{
"mcpServers": {
"metasearch-mcp": {
"command": "npx",
"args": ["-y", "@metasearch/feed-validator"]
}
}
}Resumen de MCP Servers
# metasearch MCP
[](https://github.com/metasearchcomtr/metasearch-mcp/actions/workflows/validate.yml)
[](LICENSE)
Remote Model Context Protocol (MCP) server for **hotel and travel feed validation, normalization, readiness checks, and platform requirement comparison**.
Operated by [metasearch.com.tr](https://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
| 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 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/mcp
claude 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/`](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](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](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](docs/privacy-and-security.md) and [SECURITY.md](SECURITY.md).
## Official MCP Registry
The canonical registry descriptor is [`server.json`](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`](https://www.npmjs.com/package/@metasearch/feed-validator):
```bash
npx @metasearch/feed-validator validate hotels.csv --target google-hotel-center
```
Source: [metasearchcomtr/feed-validator](https://github.com/metasearchcomtr/feed-validator)
## Documentation
- [MCP documentation](https://metasearch.com.tr/en/mcp)
- [Hotel Feed Validator](https://metasearch.com.tr/en/tools/hotel-feed-validator)
- [Hotel feed requirements comparison](https://metasearch.com.tr/en/compare/hotel-feed-requirements)
- [Validate hotel feeds with MCP](https://metasearch.com.tr/en/resources/validate-hotel-feeds-with-mcp)
## Contributing
Issues and focused pull requests are welcome. See [CONTRIBUTING.md](CONTRIBUTING.md).
## License
MIT. See [LICENSE](LICENSE).
Lo que la gente pregunta sobre metasearch-mcp
¿Qué es metasearchcomtr/metasearch-mcp?
+
metasearchcomtr/metasearch-mcp es mcp servers para el ecosistema de Claude AI. Remote MCP server for hotel and travel feed validation, normalization and platform requirement comparison. Tiene 0 estrellas en GitHub y su última actualización registrada es del 2026-10-08.
¿Cómo se instala metasearch-mcp?
+
Puedes instalar metasearch-mcp clonando el repositorio (https://github.com/metasearchcomtr/metasearch-mcp) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.
¿Es seguro usar metasearchcomtr/metasearch-mcp?
+
Nuestro agente de seguridad ha analizado metasearchcomtr/metasearch-mcp y le ha asignado un Trust Score de 95/100 (tier: Verified). Revisa el desglose completo de comprobaciones superadas y flags en esta página.
¿Quién mantiene metasearchcomtr/metasearch-mcp?
+
metasearchcomtr/metasearch-mcp es mantenido por metasearchcomtr. La última actividad registrada en GitHub es del 2026-10-08, con 0 issues abiertos.
¿Hay alternativas a metasearch-mcp?
+
Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.
Despliega metasearch-mcp en tu cloud
Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.
¿Mantienes este repo? Añade un badge a tu README
Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.
[](https://claudewave.com/repo/metasearchcomtr-metasearch-mcp)<a href="https://claudewave.com/repo/metasearchcomtr-metasearch-mcp"><img src="https://claudewave.com/api/badge/metasearchcomtr-metasearch-mcp" alt="Featured on ClaudeWave: metasearchcomtr/metasearch-mcp" width="320" height="64" /></a>Más MCP Servers
Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.
User-friendly AI Interface (Supports Ollama, OpenAI API, ...)
An open-source AI agent that brings the power of Gemini directly into your terminal.
Real-time global intelligence dashboard. AI-powered news aggregation, geopolitical monitoring, and infrastructure tracking in a unified situational awareness interface
🕷️ An adaptive Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
The fastest path to AI-powered full stack observability, even for lean teams.