Head to head
IWE vs travelMCP Directory
Same numbers we show everywhere else, lined up. Ratings come from users, the grade comes from our scanner, adoption comes from public registries.
No reviews yet
Markdown knowledge base as agent memory. Runs against the notes directory it is started in.
Full listingtravelMCP Directory
Cai.omnitravel/travelmcp-directoryNo reviews yet
Search MCP servers, agent skills and APIs for travel: hotel ID mapping, rates, rooms.
Full listingThe short version
Neither has been reviewed yet, so the comparison rests on the scan and the public usage numbers. The safety scan favours IWE (94/100 against 69). travelMCP Directory is hosted and callable through the gateway; IWE runs on your own machine. IWE has noticeably more public adoption.
| IWE | travelMCP Directory | |
|---|---|---|
| User rating | No reviews yet | No reviews yet |
| Safety grade | A94/100 | C69/100 |
| Adoption | Established | New |
| GitHub stars | 1.7k | – |
| Downloads / week | 136 | – |
| Runs where | Your machine (local) | Hosted (remote) |
| Gateway-ready | No | Yes |
| Tools | — | 3 |
| Write actions | — | — |
| Price per call | Free | Free |
| Licence | Apache-2.0 | — |
| Last release | 2026-09-19 | — |
| Category | AI and agents | AI and agents |