Cruise Itinerary vs Decodo
Cruise Itinerary lists no tools and runs remotely and Decodo lists no tools and runs locally.
| Fact | Cruise Itinerarycom.cruise-itinerary/mcp | Decodoio.github.Decodo/mcp-server |
|---|---|---|
| Score | Not checked yet | Not checked yet |
| Status | Not checked yet | Not checked yet |
| Tools | 0 | 0 |
| Can write data | No tools listed | No tools listed |
| Runs | Remote | Local |
| Needs first | – | Node.js |
| Licence | Not stated | ISC |
| Latest version | 1.0.0 | 1.7.0 |
| Known advisories | Not checked yet | 0 |
| Works in | Claude Desktop, Claude Code, Cursor, VS Code, Devin Desktop, Zed, Cline, Continue, Goose, LM Studio, Gemini CLI, Codex, oterm, Agenvoy, Amp, AnythingLLM, Augment Code, Bob Shell, ECA, Kiro, Kiro CLI | Claude Desktop, Claude Code, Cursor, VS Code, Devin Desktop, Zed, Cline, Continue, Goose, LM Studio, Gemini CLI, Codex, mcp-client-cli, oterm, TUUI, BoltAI, Agenvoy, Amp, AnythingLLM, Augment Code, Bob Shell, ECA, Kiro, Kiro CLI |
| Downloads last week | Not known | Not known |
| Install | Install Cruise Itinerary | Install Decodo |
Scores and status come with our own checks, which have not run on these servers yet. The rest is from the publishers' registry entries, package registries and advisory databases.
Compare Cruise Itinerary with othersCompare Decodo with others