# Viajante (npm · @viajante/mcp)

Flight and hotel search for the terminal, Python, and AI assistants.

- Trust score: 49/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@viajante/mcp`: 49/100 (this document), [markdown](https://verifymcp.io/servers/felipebasurto-viajante/viajante-mcp.md), [page](https://verifymcp.io/servers/felipebasurto-viajante/viajante-mcp)
- pypi · `viajante`: 24/100, [markdown](https://verifymcp.io/servers/felipebasurto-viajante/viajante.md), [page](https://verifymcp.io/servers/felipebasurto-viajante/viajante)

## Channel facts

- Registry: `npm`
- Package: `@viajante/mcp`
- Version: `1.5.5`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to felipebasurto/viajante).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- **Capabilities**: 0/100
  - Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.

**Unverified: 5 categories.** Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you.

## Install

### How do I install the Viajante MCP server?

Viajante runs locally as an npm package, launched with npx -y @viajante/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add felipebasurto-viajante -- npx -y @viajante/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "felipebasurto-viajante": {
      "command": "npx",
      "args": [
        "-y",
        "@viajante/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "felipebasurto-viajante": {
      "command": "npx",
      "args": [
        "-y",
        "@viajante/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add felipebasurto-viajante -- npx -y @viajante/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "felipebasurto-viajante": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@viajante/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add felipebasurto-viajante --command npx --arg -y --arg @viajante/mcp
```

### Hermes

```yaml
mcp_servers:
  felipebasurto-viajante:
    command: "npx"
    args: ["-y", "@viajante/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "felipebasurto-viajante": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@viajante/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add felipebasurto-viajante -t stdio -c npx -a -y @viajante/mcp
```

### Other

```json
{
  "mcpServers": {
    "felipebasurto-viajante": {
      "command": "npx",
      "args": [
        "-y",
        "@viajante/mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 49, 0)

- [security] Stability: Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.
- [security] Tool safety: Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.
- [functional] Tool coverage: Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.
- [functional] Capabilities: Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.
- [functional] Schema quality: Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.
- [functional] Package version: 1.5.4 → 1.5.5

### 2026-11-04 (score 49, 0)

- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [security] Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- [functional regression] Security disclosure: fail → unverified
- [functional] Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional] Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- [functional] Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.
- [functional] Package version: 1.5.2 → 1.5.4

### 2026-10-26 (score 49, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-25 (score 49, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-19 (score 49, 0)

- [functional regression] Security disclosure: unverified → fail
- [functional] Package version: 1.5.0 → 1.5.2
- [functional] Package version: 1.5.0 → 1.5.1

### 2026-10-18 (score 49, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-15 (score 49, 0)

- [security] Stability: Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.
- [security] Tool safety: Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.
- [functional] Capabilities: Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.
- [functional] Tool coverage: Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.
- [functional] Schema quality: Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.

### 2026-10-12 (score 49, 0)

- [functional regression] Security disclosure: unverified → fail

## MCP tools (0)

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/felipebasurto-viajante/viajante-mcp#diagnostics

## Score history

- 2026-11-05: 49
- 2026-11-04: 49
- 2026-11-03: 49
- 2026-11-02: 49
- 2026-11-01: 49
- 2026-10-31: 49
- 2026-10-30: 49
- 2026-10-29: 49
- 2026-10-28: 49
- 2026-10-27: 49
- 2026-10-26: 49
- 2026-10-25: 49
- 2026-10-24: 49
- 2026-10-23: 49
- 2026-10-22: 49
- 2026-10-21: 49
- 2026-10-20: 49
- 2026-10-19: 49
- 2026-10-18: 49
- 2026-10-17: 49
- 2026-10-16: 49
- 2026-10-15: 49
- 2026-10-14: 49
- 2026-10-13: 49
- 2026-10-12: 49
- 2026-10-11: 49
- 2026-10-06: 49
- 2026-10-04: 49
- 2026-10-03: 49
- 2026-10-02: 34

## Common questions

### What is the Viajante MCP server?

Viajante is an MCP server listed in the public MCP registry as io.github.felipebasurto/viajante. Flight and hotel search for the terminal, Python, and AI assistants. This page covers its npm package (@viajante/mcp).

### Is the Viajante MCP server safe to use?

Viajante scores 49 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### Is the Viajante MCP server still maintained?

Viajante is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Viajante MCP server under?

Viajante declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Viajante MCP server?

VerifyMCP ran 9 checks on Viajante, covering Malware scan, Known CVEs, Install scripts, Dependency health and 5 more. 5 items could not be completed, a gap on our side rather than a finding about Viajante: Schema quality, Stability, Tool coverage, Tool safety and 1 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@viajante/mcp
- Socket report: https://socket.dev/npm/package/@viajante/mcp
- Repository: https://github.com/felipebasurto/viajante
- Changelog RSS feed: https://verifymcp.io/servers/felipebasurto-viajante/viajante-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/felipebasurto-viajante/viajante-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/felipebasurto-viajante/viajante-mcp.json
- HTML version of this page: https://verifymcp.io/servers/felipebasurto-viajante/viajante-mcp