Travel Assistant MCP: why it is not safe to use
Travel Assistant MCP passed our review; we found disclosed third-party data flows, local JSON caching, and no hidden instructions or embedded secrets.
What we found
Our review of Travel Assistant MCP did not identify a security or privacy issue that would block use. The inspected README and server code openly describe the skill's tools and orchestration behavior, and we did not find hidden or disguised instructions. The skill sends travel-related queries to disclosed third-party services used for its stated purpose, including SerpAPI for flights, hotels, events, and finance lookups, plus Nominatim and the National Weather Service for geocoding and weather. We did not find evidence of undisclosed destinations, remote code download, or remote code execution. We also did not find hardcoded live credentials, access to unrelated local credentials, privilege escalation behavior, or dangerous destructive commands. The inspected code writes cached JSON result files locally.
What to do instead
If you use this skill, treat it as a travel helper that shares relevant query data with the named external services to fulfill requests. Review those providers' terms and privacy practices, supply API keys through environment variables as intended, and avoid including unnecessary sensitive personal data in prompts. If local caching is a concern in your environment, review how cached JSON result files are stored and retained before deployment.
Source: https://github.com/skarlekar/mcp_travelassistant
We report what our security review found at the time we checked, with the goal of keeping people safe. Projects change; if a maintainer has since fixed this, we are glad to recheck it. Email hello@agentpod.com.