Pulse
Description
Access comprehensive travel and location data to streamline trip planning and destination research. Discover curated activities and points of interest for any location worldwide. Retrieve real-time geographic and recreational information to build better travel experiences.
What our measurements say
Pulse is a remote MCP server published at mcp.1trip.app. It has been probed 6 times since 9/10/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 614 ms, a delay an agent will notice. It exposes a broad tool surface of 29 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Tools cover end-to-end trip planning needs (costs, safety, itineraries, etc.)
- Some tools have detailed parameter requirements and use cases
- Includes unique features like persona-based planning and community routes
Weaknesses
- Several tool names are ambiguous (e.g., 'get_sponge_stats', 'get_trip_patterns')
- Multiple tools handle similar functions (e.g., 'save_trip' vs 'save_to_planner')
- Parameter requirements are inconsistently documented
- Error handling and limitations are only mentioned in a few tools
get_sponge_stats— Name doesn't clearly indicate it's about system statisticslist_destinations— Function overlaps with 'compare_destinations'get_weather_forecast— Parameter requirements (date range) not explicitly marked as requiredsuggest_itinerary_nearby— Limited city support not clearly communicated in descriptionget_trip_patterns— Description cuts off mid-sentence, making purpose unclear
Verdict
Event narrative
Risk: medium
- 2026-09-10T21:16:35.016Z — era changed from auth-gated to legacy · server now operates under legacy framework
- 2026-09-11T07:35:54.413Z — complianceScore increased from null to 100 · system achieved full compliance with regulations
Advice
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test not run this round
- Cold-start: cold 208ms → warm 200ms (penalty 8ms)
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Server build: — → 8.3.0
- Supported versions: — → 2025-11-25
- Era changed: Auth-gated → Legacy
- Added to watch — era: Auth-gated
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/onetrip-pulse)<a href="https://mcpmetrics.io/servers/onetrip-pulse"><img src="https://mcpmetrics.io/badge/onetrip/pulse/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 see