Visa Requirements
NPM · @PIPEWORX/MCP-VISA-REQUIREMENTS · 2 COMPONENTS
Visa Requirements MCP — passport visa rules for any nationality → destination pair
Available components
Last scanned (1 hour ago)
Scores higher than 81% of npm servers
Category Maps and Location
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-visa-requirements). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 536 tokens (~178/item across 3 items; 3 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 Management23
- Stability observed for 7 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
- 5 Nov 26 +4
- Stability: unverified → 0.23 ▲ functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 80
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-visa-requirements@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-visa-requirements |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-visa-requirements/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560979911 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:8a86cc4d1927450513883ecbde1bb10bd6cfb5bf5790751b5a07451f17059afba4c3291ad40cafd83eb51ff7ad56ee6e24b45fa24d7a9388dedb948bb |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
visa_free_destinations ~161
Where can holders of a given passport travel without a visa? Lists every destination grouped by requirement: visa-free (with allowed stay days), visa on arrival, e-visa, eTA — plus counts for visa-required and no-admission. Optional filter to a single category. Answers "visa-free countries for X passport holders". Data: Passport Index snapshot (2026-02-18). Example: visa_free_destinations({ passport: "Germany" })
| Name | Type | Req | Description |
|---|---|---|---|
| passport | string | yes | Passport / nationality — ISO2, ISO3, or country name |
| requirement | string | – | Optional: return only destinations in this category (default: full lists for visa_free, visa_on_arrival, e_visa, eta, plus counts for the rest) |
No output schema declared.
No examples provided.
visa_passport_compare ~140
Compare passport power: for 2-5 passports, how many destinations each can enter visa-free / on arrival / with e-visa or eTA / visa required (passport-ranking mobility comparison). With exactly 2 passports, also lists destinations where the requirements differ (up to 30). Data: Passport Index snapshot (2026-02-18). Example: visa_passport_compare({ passports: ["US", "India"] })
| Name | Type | Req | Description |
|---|---|---|---|
| passports | array | yes | 2-5 passports to compare — ISO2, ISO3, or country names, e.g. ["US", "IN"] or ["Germany", "Japan", "Singapore"] |
No output schema declared.
No examples provided.
visa_requirement ~178
Do I need a visa? Visa requirement for one passport (nationality) traveling to one destination country — returns visa-free (with allowed stay days when known), visa on arrival, e-visa, eTA, visa required, or no admission. Covers 199×199 country pairs. Data: community-maintained Passport Index snapshot (last updated 2026-02-18) — verify with official sources before travel. Example: visa_requirement({ passport: "United States", destination: "Brazil" })
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | Destination country — ISO2, ISO3, or country name, e.g. "BR", "Japan", "Türkiye" |
| passport | string | yes | Passport / nationality — ISO2, ISO3, or country name, e.g. "US", "DEU", "South Korea", "UK" |
No output schema declared.
No examples provided.
How do I install the Visa Requirements MCP server?
Visa Requirements runs locally as an npm package, launched with npx -y @pipeworx/mcp-visa-requirements. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-visa-requirements
claude mcp add pipeworx-io-visa-requirements -- npx -y @pipeworx/mcp-visa-requirements
What is the Visa Requirements MCP server?
Visa Requirements is an MCP server listed in the public MCP registry as io.github.pipeworx-io/visa-requirements. Visa Requirements MCP, passport visa rules for any nationality → destination pair. This page covers its npm package (@pipeworx/mcp-visa-requirements).
Is the Visa Requirements MCP server safe to use?
Visa Requirements scores 84 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.
What tools does the Visa Requirements MCP server expose?
Visa Requirements exposes 3 tools: visa_requirement, visa_free_destinations, visa_passport_compare. Their descriptions and schemas cost roughly 479 tokens of context every time the server is loaded.
Is the Visa Requirements MCP server still maintained?
Visa Requirements 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 Visa Requirements MCP server under?
Visa Requirements declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.