# com.canienter/visa-check (remote · api.canienter.com)

Visa & entry requirements for 199 passports, cited to official sources and re-verified daily.

- Trust score: 70/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-18

## Components

- remote · `api.canienter.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/com-canienter-visa-check/api.md), [page](https://verifymcp.io/servers/com-canienter-visa-check/api)

## Channel facts

- Endpoint: `https://api.canienter.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-18.

- **Endpoint Security**: 71/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-canienter-visa-check https://api.canienter.com/mcp
```

### Codex

```toml
[mcp_servers.com-canienter-visa-check]
url = "https://api.canienter.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-canienter-visa-check": {
      "type": "remote",
      "url": "https://api.canienter.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-canienter-visa-check --url https://api.canienter.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-canienter-visa-check:
    url: "https://api.canienter.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-canienter-visa-check": {
      "type": "http",
      "url": "https://api.canienter.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-08-18 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-16 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-14 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-12 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-11 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-10 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-09 (score 65)

First indexed and scored.

## MCP tools (3)

### `check_entry_requirements` (~233 tokens)

Check entry requirements

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).

Input parameters:

- `destination` (string, required): Destination country, ISO 3166-1 alpha-3 (e.g. JPN)
- `passport` (string, required): 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)

Output parameters:

- `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

### `evaluate_trip` (~120 tokens)

Evaluate a full trip (paid)

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.

Input parameters:

- `traveler` (object, required): The traveler's documents
- `trip` (object, required): The itinerary to evaluate, in travel order

Output parameters:

- `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

### `get_dataset_info` (~33 tokens)

Dataset & pricing info

Coverage and freshness of the underlying visa-requirements dataset, plus endpoints and x402 pricing for the unlimited paid tier.

Output parameters:

- `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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-canienter-visa-check/api#diagnostics

## Score history

- 2026-08-18: 70
- 2026-08-17: 69
- 2026-08-16: 69
- 2026-08-15: 68
- 2026-08-14: 68
- 2026-08-13: 67
- 2026-08-12: 67
- 2026-08-11: 66
- 2026-08-10: 65
- 2026-08-09: 65

## Links

- Remote endpoint: https://api.canienter.com/mcp
- Website: https://canienter.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-canienter-visa-check/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-canienter-visa-check/api.json
- HTML version of this page: https://verifymcp.io/servers/com-canienter-visa-check/api