io.github.forgemeshlabs/travel-assistant-mcp
NPM · @FORGEMESHLABS/TRAVEL-ASSISTANT-MCP · SCANNED SEP 24
No-key travel MCP for Claude Desktop, Codex-style agents, Hermes, and other clients.
Available components
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 22 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 721 tokens (~144/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.forgemeshlabs/travel-assistant-mcp server?
io.github.forgemeshlabs/travel-assistant-mcp runs locally as an npm package, launched with npx -y @forgemeshlabs/travel-assistant-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @forgemeshlabs/travel-assistant-mcp
claude mcp add forgemeshlabs-travel-assistant-mcp -- npx -y @forgemeshlabs/travel-assistant-mcp
{
"mcpServers": {
"forgemeshlabs-travel-assistant-mcp": {
"command": "npx",
"args": [
"-y",
"@forgemeshlabs/travel-assistant-mcp"
]
}
}
} {
"servers": {
"forgemeshlabs-travel-assistant-mcp": {
"command": "npx",
"args": [
"-y",
"@forgemeshlabs/travel-assistant-mcp"
]
}
}
} codex mcp add forgemeshlabs-travel-assistant-mcp -- npx -y @forgemeshlabs/travel-assistant-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"forgemeshlabs-travel-assistant-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@forgemeshlabs/travel-assistant-mcp"
],
"enabled": true
}
}
} openclaw mcp add forgemeshlabs-travel-assistant-mcp --command npx --arg -y --arg @forgemeshlabs/travel-assistant-mcp
mcp_servers:
forgemeshlabs-travel-assistant-mcp:
command: "npx"
args: ["-y", "@forgemeshlabs/travel-assistant-mcp"] {
"McpServers": {
"forgemeshlabs-travel-assistant-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@forgemeshlabs/travel-assistant-mcp"
]
}
}
} assistant mcp add forgemeshlabs-travel-assistant-mcp -t stdio -c npx -a -y @forgemeshlabs/travel-assistant-mcp
{
"mcpServers": {
"forgemeshlabs-travel-assistant-mcp": {
"command": "npx",
"args": [
"-y",
"@forgemeshlabs/travel-assistant-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Analysed npm/@forgemeshlabs/travel-assistant-mcp@0.2.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
build_booking_link ~181
Generate only an external booking link for an already chosen route. Use after route details are known or after compare_routes/search_travel_options; do not use as the first step when the user still needs search guidance. Read-only, no authentication, no booking completion, and no reservation side effects. The returned link may be commission-eligible and is disclosed in output.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | ISO 4217 currency code (default: USD). |
| departure_date | string | – | Departure date in YYYY-MM-DD format. Optional. |
| destination | string | – | Destination IATA code (e.g. 'CDG'). Case-insensitive. |
| origin | string | – | Origin IATA code (e.g. 'IAH'). Case-insensitive. |
| return_date | string | – | Return date in YYYY-MM-DD format. Optional — omit for one-way. |
No output schema declared.
No examples provided.
compare_routes ~101
Compare two or more airport route pairs side by side. Use when the user is choosing between alternate origins, destinations, or airports; use search_travel_options for one dated route and get_airport_info for a single airport lookup. Read-only, no authentication, no booking side effects. Responses may include commission-eligible external booking links for each route.
| Name | Type | Req | Description |
|---|---|---|---|
| routes | array | yes | Array of route pairs to compare. Minimum 1, typically 2-5. |
No output schema declared.
No examples provided.
explain_travel_timing ~120
Explain general travel timing and logistics, including booking windows, airport arrival timing, layovers, and seasonal considerations. Use for advice questions like when to book or how early to arrive; use search_travel_options when the user wants route-specific flight search. Read-only, no authentication, no external booking link, and no booking side effects.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | – | Destination IATA code. Optional — used to determine if route is international. |
| origin | string | – | Origin IATA code. Optional — used to determine if route is international. |
No output schema declared.
No examples provided.
get_airport_info ~95
Look up metadata for one airport by IATA code. Use to validate or explain a single airport code before route planning; use search_travel_options for an actual trip search and compare_routes for multiple origin-destination pairs. Read-only, no authentication, no external booking links, and no booking side effects.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Three-letter IATA airport code (e.g. 'SFO'). Case-insensitive. |
No output schema declared.
No examples provided.
search_travel_options ~224
Primary travel search workflow for one origin-destination airport pair. Use when the user wants flight/trip options for a specific route; use compare_routes for multiple routes, build_booking_link only when route details are already known, and get_airport_info only to validate one airport. Read-only, no authentication, no booking side effects. return_date is optional; omit it for one-way trips. Responses include route metadata and may include commission-eligible external booking links.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | ISO 4217 currency code (default: USD). Used in booking link parameters. |
| departure_date | string | – | Departure date in YYYY-MM-DD format. Optional — omit for open date searches. |
| destination | string | yes | Destination airport IATA code (e.g. 'LHR', 'NRT'). Case-insensitive. |
| origin | string | yes | Origin airport IATA code (e.g. 'LAX', 'JFK'). Case-insensitive. |
| return_date | string | – | Return date in YYYY-MM-DD format. Omit for one-way trips. |
No output schema declared.
No examples provided.
What is the io.github.forgemeshlabs/travel-assistant-mcp server?
io.github.forgemeshlabs/travel-assistant-mcp is listed in the public MCP registry as io.github.forgemeshlabs/travel-assistant-mcp. No-key travel MCP for Claude Desktop, Codex-style agents, Hermes, and other clients. This page covers its npm package (@forgemeshlabs/travel-assistant-mcp).
Is the io.github.forgemeshlabs/travel-assistant-mcp server safe to use?
io.github.forgemeshlabs/travel-assistant-mcp scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. 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.
What tools does the io.github.forgemeshlabs/travel-assistant-mcp server expose?
io.github.forgemeshlabs/travel-assistant-mcp exposes 5 tools: search_travel_options, get_airport_info, compare_routes, build_booking_link, explain_travel_timing. Their descriptions and schemas cost roughly 721 tokens of context every time the server is loaded.
Is the io.github.forgemeshlabs/travel-assistant-mcp server still maintained?
io.github.forgemeshlabs/travel-assistant-mcp is still listed as active in the MCP registry. We last reached this channel on 24 September 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 io.github.forgemeshlabs/travel-assistant-mcp server under?
io.github.forgemeshlabs/travel-assistant-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.