# metasearch MCP

> Hotel and travel feed validation, normalization and requirement comparison.

- name: tr.com.metasearch/metasearch-mcp
- version: 1.1.0
- connection class: R0 (autonomous)
- trust: 95/100
- quality: 79/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/tr.com.metasearch%2Fmetasearch-mcp
- tools: https://api.protogrid.dev/v1/servers/tr.com.metasearch%2Fmetasearch-mcp/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "metasearch-mcp": {
      "type": "http",
      "url": "https://metasearch.com.tr/mcp"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 98
- freshness: 100
- provenance: 85
- drivers: +repository +dns-namespace +website +reachable +uptime-96% +updated-12d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 79/100 (good)

### protocol: 88 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- warn `protocol.list_ttl`: tools/list declares ttlMs 0, so clients re-fetch it on every use

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 12 of 12 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 2,524 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 25 (weight 15)

- warn `stability.changes`: 12 tool changes in 30 days
- fail `stability.rug_pull`: 1 tools kept their name but changed most of their description in 30 days; review before trusting them

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 12, about 2,524 tokens to load them all
- tool set hash: d8c76b17e2e8e6169b5abbee30394f64
- tools last changed: 2026-10-09T17:40:06.904Z
- badge: [![protogrid quality](https://protogrid.dev/badge/tr.com.metasearch/metasearch-mcp.svg)](https://protogrid.dev/servers/tr.com.metasearch/metasearch-mcp)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-09 `suggest_feed_fixes` changed (title, description, inputSchema, outputSchema, annotations)
  - before: Validate a feed for one target and turn validation issues into deterministic remediation suggestions.
  - after: Validate a supplied feed for one target and turn deterministic validation issues into remediation actions for the affected records.
- 2026-10-09 `compare_platform_requirements` changed (title, description, inputSchema, outputSchema, annotations)
  - before: Compare published or readiness-oriented field requirements across supported hotel/catalog platforms before designing a feed mapping.
  - after: Compare documented or readiness-oriented field requirements across supported hotel and catalog platforms before designing a feed mapping.
- 2026-10-09 `compare_feed_readiness` changed (title, description, inputSchema, outputSchema, annotations)
  - before: Run the same static feed through multiple platform rule packs and compare readiness scores and issue counts.
  - after: Run the same static feed through multiple platform rule packs and compare readiness scores, errors, warnings and validation issues.
- 2026-10-09 `validate_hotel_master_data` changed (title, inputSchema, outputSchema, annotations)
- 2026-10-09 `validate_criteo_catalog` changed (title, description, inputSchema, outputSchema, annotations)
  - before: Check a product/travel catalog for Criteo import readiness, content coverage, IDs, URLs and images.
  - after: Check a product or travel catalog for Criteo import readiness, content coverage, IDs, URLs and images.
- 2026-10-09 `validate_meta_catalog` changed (title, description, inputSchema, outputSchema, annotations)
  - before: Check a hotel/travel catalog for Meta mapping and catalog readiness. This is not official Meta certification.
  - after: Check a hotel or travel catalog for Meta mapping and catalog readiness. This is not official Meta certification.
- 2026-10-09 `validate_trivago_hotel_data` changed (title, inputSchema, outputSchema, annotations)
- 2026-10-09 `validate_google_hotel_center_list` changed (title, description, inputSchema, outputSchema, annotations)
  - before: Validate a Google Hotel Center Hotel List static feed, including identifiers, address, country and phone/geo requirements.
  - after: Validate a Google Hotel Center Hotel List static feed, including identifiers, address, country and phone or geo requirements.
- 2026-10-09 `validate_wego_hotel_feed` changed (title, inputSchema, outputSchema, annotations)
- 2026-10-09 `validate_feed` changed (title, description, inputSchema, outputSchema, annotations) **meaning changed**
  - before: Validate a static hotel or catalog feed for a selected target platform.
  - after: Validate a supplied static hotel or catalog feed against one selected platform rule pack or the generic hotel master-data audit.

Full history: https://api.protogrid.dev/v1/servers/tr.com.metasearch%2Fmetasearch-mcp/changes

## Remotes

- https://metasearch.com.tr/mcp (streamable-http, auth none, reachable true, uptime30d 0.9574468)

## Packages

_none_

## Tools (12)

- `compare_feed_readiness`: Run the same static feed through multiple platform rule packs and compare readiness scores, errors, warnings and validation issues.
- `compare_platform_requirements`: Compare documented or readiness-oriented field requirements across supported hotel and catalog platforms before designing a feed mapping.
- `detect_feed_format`: Detect whether a supplied hotel or catalog feed payload is JSON, NDJSON, XML, CSV or TSV before parsing or validation.
- `normalize_hotel_feed`: Parse a hotel feed and normalize common supplier or platform aliases into a canonical hotel-record shape without changing the source payload.
- `suggest_feed_fixes`: Validate a supplied feed for one target and turn deterministic validation issues into remediation actions for the affected records.
- `validate_criteo_catalog`: Check a product or travel catalog for Criteo import readiness, content coverage, IDs, URLs and images.
- `validate_feed`: Validate a supplied static hotel or catalog feed against one selected platform rule pack or the generic hotel master-data audit.
- `validate_google_hotel_center_list`: Validate a Google Hotel Center Hotel List static feed, including identifiers, address, country and phone or geo requirements.
- `validate_hotel_master_data`: Run a platform-independent hotel master-data quality audit.
- `validate_meta_catalog`: Check a hotel or travel catalog for Meta mapping and catalog readiness. This is not official Meta certification.
- `validate_trivago_hotel_data`: Validate CSV or JSON hotel inventory against trivago FastConnect's published Hotel Data requirements.
- `validate_wego_hotel_feed`: Validate a static hotel feed against Wego-oriented published requirements and data-quality checks.