com.canienter/visa-check
REMOTE · API.CANIENTER.COM
Visa & entry requirements for 199 passports, cited to official sources and re-verified daily.
Available components
Last scanned (12 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 464 tokens (~154/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 8 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 9 Aug 26 0
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 · Probed https://api.canienter.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=canienter.com | CN=WE1,O=Google Trust Services,C=US | 5 Oct 2026 | 3 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 2085d9b4fdef80cc0e4da3a51528511a |
| SANs: canienter.com, api.canienter.com, *.api.canienter.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.canienter.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| canienter.com. | present | 2371 | 13 | Verified |
| api.canienter.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.canienter.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.canienter.com/mcp | Inconclusive | 405 |
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 →
check_entry_requirements Check entry requirements ~233
Whether a passport holder can enter a destination country: visa-free, visa on arrival, e-visa, eTA, or visa required — with allowed stay, official application portal, extended rules (passport validity, onward ticket, yellow fever, transit-without-visa) and source citations. Free tier: rate limited per caller (see /auth.md to register for a larger quota, or use the x402-paid HTTP API for unlimited access).
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | Destination country, ISO 3166-1 alpha-3 (e.g. JPN) |
| passport | string | yes | Passport country, ISO 3166-1 alpha-3 (e.g. NLD) |
| purpose | string | – | Travel purpose (default: tourism) |
| residence_permits_of | array | – | Issuers of residence permits held (ISO3 or SCHENGEN/EU/GCC) |
| transit | string | – | Optional transit country, ISO 3166-1 alpha-3 |
| visas_of | array | – | Issuers of visas held (ISO3 or SCHENGEN/EU/GCC) |
| Name | Type | Req | Description |
|---|---|---|---|
| allowed_stay_days | number|null | – | Maximum stay in days when the verdict grants one |
| apply | object|null | – | Official government application/information portal when action is required |
| dataset_version | string | – | Base-matrix revision (YYYY-MM-DD) |
| defaults_applied | array | – | Assumptions applied to answer (e.g. purpose=tourism, ordinary passport) |
| entry_rules | object | – | Destination entry rules: passport_validity, blank_pages, onward_ticket, yellow_fever, other_health, twov (transit-without-visa), residence_permit_exemptions, official_links, purpose_scope — each non-… |
| entry_rules_verification | object | – | Provenance of the curated entry-rules layer: verified_official_sources | stale | not_curated | needs_review, with last_verified and staleness_days |
| request_id | string | – | Unique id for reproducibility |
| requirement | string | – | visa_free | visa_on_arrival | e_visa | eta | visa_required | no_admission | unknown | needs_review |
| requirement_label | string | – | Human-readable verdict |
| verdict_verification | object | – | Provenance of the visa verdict itself — always derives from an aggregated secondary matrix (status secondary_source_only or needs_review), never claimed officially verified |
No examples provided.
evaluate_trip Evaluate a full trip (paid) ~120
Premium evaluation of a whole trip in one call: multiple passports (best passport per leg), documents held, multi-leg itineraries with transit legs, dates and purpose — with structured why[] explanations, conditions[], and verification states per decision. PAID endpoint: the call returns HTTP 402 x402 payment instructions unless the request carries an x402 payment header; any x402-capable client settles in USDC on Base and retries.
| Name | Type | Req | Description |
|---|---|---|---|
| traveler | object | yes | The traveler's documents |
| trip | object | yes | The itinerary to evaluate, in travel order |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | Present on the unpaid path: 'payment_required' |
| legs | array | – | One decision per leg: requirement, best_option (which held passport/document wins), why[] explanations with sources, conditions[] (validity, onward ticket, yellow fever, stay-duration fit), and a ver… |
| trip_summary | object | – | Aggregate outcome |
| x402_requirements | object|null | – | x402 v2 payment requirements (decoded from the PAYMENT-REQUIRED header): pay in USDC on Base and retry the same call |
No examples provided.
get_dataset_info Dataset & pricing info ~33
Coverage and freshness of the underlying visa-requirements dataset, plus endpoints and x402 pricing for the unlimited paid tier.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| docs | string | – | LLM-facing documentation URL |
| free_endpoint | object | – | The free rate-limited check endpoint |
| paid_endpoints | object | – | x402 pay-per-request endpoints (USDC on Base, no account) |
| transparency | string | – | Data-quality metrics URL |
No examples provided.
How do I install the com.canienter/visa-check MCP server?
com.canienter/visa-check is a hosted endpoint at https://api.canienter.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.canienter.com
claude mcp add --transport http com-canienter-visa-check 'https://api.canienter.com/mcp'
What is the com.canienter/visa-check MCP server?
com.canienter/visa-check is an MCP server listed in the public MCP registry as com.canienter/visa-check. Visa & entry requirements for 199 passports, cited to official sources and re-verified daily. This page covers its hosted endpoint (https://api.canienter.com/mcp).
Is the com.canienter/visa-check MCP server safe to use?
com.canienter/visa-check scores 81 out of 100 on VerifyMCP. 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 com.canienter/visa-check MCP server expose?
com.canienter/visa-check exposes 3 tools: check_entry_requirements, evaluate_trip, get_dataset_info. Their descriptions and schemas cost roughly 386 tokens of context every time the server is loaded.
Does the com.canienter/visa-check MCP server require authentication?
No. We connected to com.canienter/visa-check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.canienter/visa-check MCP server still maintained?
com.canienter/visa-check 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.