Home / MCP registry index / app.dreamfare/mcp
Dreamfare
app.dreamfare/mcp in the official MCP registry.
Endpoint https://api.dreamfare.app/mcp.
The registry describes it as: Travel tools for AI agents: plan and edit real trips, search stays and tours, import travel videos.
We read its 21 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
get_trip create_trip add_to_trip edit_trip delete_trip plan_trip search_car_rentals search_trains search_stays search_activities search_places search_flights research_options import_places get_profile update_profile list_library edit_library manage_crew explore_trips display_card
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/app-dreamfare-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.