https://mcp.desafiocomunicacion.com/mcp ↗
Servicios de Google Ads, medición, automatización, casos y contacto.
Desafío Comunicación is a remote MCP server published at mcp.desafiocomunicacion.com. It has been probed 6 times since 9/12/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 305 ms, placing it among the faster endpoints. It offers a narrow, focused set of 6 tools. On the protocol side it speaks the 2026-07-28 stateless spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
search — Parameter 'type' lacks defined allowed valueslist_case_studies — Functionally overlaps with 'search' for case filteringrecommend_service — No explicit error handling for invalid inputRisk: low
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Tools the server advertised in the latest measurement — measured, not catalog-claimed.
searchBusca servicios, casos, preguntas frecuentes e información pública aprobada de Desafío Comunicación. Úsala cuando la necesidad todavía no corresponde a un identificador conocido.
querystringrequiredtypestringlimitintegerlanguagestringget_serviceDevuelve la ficha verificable de un servicio de Desafío por su identificador estable.
service_idstringrequiredlanguagestringrecommend_serviceRelaciona una necesidad con servicios públicos de Desafío. La salida es orientativa, explica el encaje y no promete resultados.
needstringrequiredcompany_typestringlanguagestringlist_case_studiesLista únicamente casos publicados, filtrados opcionalmente por servicio o tecnología.
service_idstringtechnologystringlimitintegerlanguagestringget_companyDevuelve identidad, posicionamiento y capacidades públicas de Desafío Comunicación.
languagestringget_contactDevuelve los canales públicos y el siguiente paso para contactar. No envía mensajes ni formularios.
intentstringlanguagestringDerived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/com-desafiocomunicacion-services)<a href="https://mcpmetrics.io/servers/com-desafiocomunicacion-services"><img src="https://mcpmetrics.io/badge/com.desafiocomunicacion/services/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to seeThe catalog entries whose name and description are closest to this one, found with the same index the search box uses.
Google Maps places, reviews, contributor history, photos and posts as JSON. No Google Cloud.
Free real-time Google Flights search — one-way and round-trip — with no API key and no signup. ### What it returns - Live fares with airline, stops, duration and a bookable link - **Google's own price insights** (`price_insights_low` / `price_insights_high`) plus a low / typical / high verdict, so an agent can tell the user whether a fare is actually a good deal — most flight APIs don't expose this at all - Round-trip priced as **paired legs**, not two one-ways stitched together ### Flexible dates in a single call Pass a departure date range and/or several destinations, and the server fans out internally and merges the results. *"Cheapest flight to Sri Lanka anywhere in October"* is **one** tool call, not thirty. Every response carries `search_coverage` stating exactly which dates were searched, so a sampled scan is never mistaken for an exhaustive one. ### Tools | Tool | What it does | | --- | --- | | `search_oneway_flights` | One-way search — a single date, or a date range | |
Real-Time Google Flights API to get live flight details and pricing. Supports all basic & advanced filters for querying oneway & roundtrip flights.
1 Google Search endpoints. Pay per call in USDC via x402.
Multiple Gmail accounts, editable Google Sheets & Docs for AI agents. Deny-by-default access rules.
The Google for AI agents — company intel, competitor tracking, market research via MCP. JSON output
| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-13 01:33:33 | Dual-era | 200 | 252 | 200 | 300 | 2026-07-28 |
| 2026-09-12 23:31:36 | Dual-era | 200 | 397 | 200 | 386 | 2026-07-28 |
| 2026-09-12 21:29:15 | Dual-era | 200 | 279 | 200 | 268 | 2026-07-28 |
| 2026-09-12 19:27:29 | Dual-era | 200 | 395 | 200 | 305 | 2026-07-28 |
| 2026-09-12 17:24:09 | Dual-era | 200 | 281 | 200 | 255 | 2026-07-28 |
| 2026-09-12 15:21:42 | Dual-era | 200 | 449 | 200 | 448 | 2026-07-28 |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.
Comments
Sign in to write a comment
No comments yet. Be the first.