_ registry / mcp streamable-http · checked 1h ago

orizn-visa

https://visa.orizn.app

Registry code: 4b279087d9a9c274

api record

Visa requirements for 199 passports across 250 destinations. Without a key, quick_visa_check answers one pair at a time, in English, 10 checks a day. About a fifth of the pairs carry an individual verification date and an official source URL; the rest are derived from the published annexes. Free API key: https://visa.orizn.app/visa-api/register?source=mcp-remote — 100 requests/month, no card, and it unlocks documents, fees, processing times, transit rules and 15 languages. Then reconnect with the key: https://visa.orizn.app/mcp?key=<key>, or an Authorization: Bearer <key> header.

endpoint
https://visa.orizn.app/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
10 · newcomer
_ is it live, free and safe measured by this hub
Is orizn-visa live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is orizn-visa free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does orizn-visa have?
6 tools: quick_visa_check, check_transit_visa, compare_destinations, get_coverage_stats, get_recent_changes, check_visa_requirement.
Is orizn-visa safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.4%· all time 99.4%

latency
195ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 644 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • check visa requirements for a passport and destination
  • get visa database coverage
takes → gives
text → data
tools
2 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
2

distinct

settlements
3

last 2026-11-09

received on chain
0.09 USDC

counted from three payers (thin, concentrated)

_ what it can do 6 tools
2 open1 auth-required 3 never probed 3 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_coverage_stats reads open 12h ago

    How big the Orizn visa database is: pairs, passports, destinations, enriched records, translations and languages. Says nothing about any specific country pair — use quick_visa_check or check_visa_requirement for that. Keyless, free, and costs nothing against any quota. Call it when the user asks how complete the data is, or to confirm this server is reachable before a longer session.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • get_recent_changes open 12h ago

    Recently changed visa rules — what changed, for which passport/destination pair, on what date, and from which official source. STATUS: Orizn's change feed is currently OFF and this tool returns {status:"unavailable", changes: []}. It was shut down because it was publishing internal data edits as if they were official policy changes. An empty answer here therefore means "Orizn has no verified change data", NEVER "nothing changed" — do not tell the user rules are stable, tell them to check the destination's official immigration source, and use check_visa_requirement for the current rule with its verification date. Keyless, costs nothing.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "limit": {
          "type": "number",
          "description": "Maximum number of changes to return (1-200, default 50)."
        },
        "since": {
          "type": "string",
          "description": "Optional ISO date (YYYY-MM-DD) — only changes detected on or after this date."
        },
        "passport": {
          "type": "string",
          "description": "Optional ISO 3166-1 alpha-3 passport code to filter on (e.g. 'FRA')."
        },
        "destination": {
          "type": "string",
          "description": "Optional ISO 3166-1 alpha-3 destination code to filter on (e.g. 'JPN')."
        }
      },
      "additionalProperties": false
    }
    arguments 23 lines
  • check_visa_requirement auth-required 4h ago

    [needs a free API key — this call will fail without one: https://visa.orizn.app/visa-api/register?source=mcp-remote, then reconnect with ?key=<key>] THE default visa tool: the full entry record for ONE passport travelling to ONE destination. Returns the requirement (visa_free / visa_required / e_visa / visa_on_arrival / eta / no_admission), days allowed, a written description, required documents, application steps, visa types, cost, validity, max stay, processing time, passport validity months, visa fees, photo specs, vaccinations, insurance, safety advisory, health requirements, overstay penalties, entry by mode (air/land/sea), transit rules, remote-work visa, extension rules, minor rules, dual-nationality and passport-stamp warnings, and embassies — in any of 15 languages, on every plan including free (fr, en, es, pt, de, ja, ko, zh, ru, it, ar, hi, th, vi, tl). Call it whenever the user asks whether they need a visa, what documents or vaccinations are needed, what a visa costs, how long it takes, how long they can stay, or what happens if they overstay. Needs an Orizn API key on this MCP connection and costs 1 request against that key's monthly quota. On the free plan the deep fields come back as {upgrade: "Available on Starter plan or above"} instead of data — report that as a plan limit, never as missing data. Reading the reply: every deep field carries a `granularity`. "destination" means the value describes the destination country for all nationalities (fees, processing days, transit, overstay, safety); "passport" means it describes the passport for all destinations (reciprocity history, stamp and dual-nationality warnings). Only the requirement, visa-free days, description and documents are pair-specific. A field Orizn does not have comes back as {status: "unavailable"} — say so rather than filling the gap, and `as_of` is the reference date of that field, not live data.

    mcp-tool

    {
      "type": "object",
      "required": [
        "passport",
        "destination"
      ],
      "properties": {
        "lang": {
          "type": "string",
          "description": "Language of the written fields. One of: fr, en, es, pt, de, ja, ko, zh, ru, it, ar, hi, th, vi, tl. Defaults to en. Available on every plan, free included."
        },
        "passport": {
          "type": "string",
          "description": "Passport country, ISO 3166-1 alpha-3 (e.g. FRA for France)."
        },
        "destination": {
          "type": "string",
          "description": "Country being entered, ISO 3166-1 alpha-3 (e.g. JPN for Japan)."
        }
      },
      "additionalProperties": false
    }
    arguments 22 lines
  • quick_visa_check reads unknown 4h ago

    Does this passport need a visa for this destination? Returns the requirement, the number of visa-free days, and — when that exact pair has been individually re-verified — the date it was. One pair per call, English only. Prefer it when the user wants a plain yes/no; switch to check_visa_requirement as soon as they need documents, fees, processing times, transit rules, or an answer in another language. Works with NO API key, 10 checks per day per network — the only tool that answers a traveller's question keyless. With a key it costs 1 request. Free API key: https://visa.orizn.app/visa-api/register?source=mcp-remote — 100 requests/month, no card, and it unlocks documents, fees, processing times, transit rules and 15 languages. Then reconnect with the key: https://visa.orizn.app/mcp?key=<key>, or an Authorization: Bearer <key> header.

    mcp-tool

    {
      "type": "object",
      "required": [
        "passport",
        "destination"
      ],
      "properties": {
        "passport": {
          "type": "string",
          "description": "Passport country, ISO 3166-1 alpha-3 (e.g. FRA)"
        },
        "destination": {
          "type": "string",
          "description": "Destination country, ISO 3166-1 alpha-3 (e.g. JPN)"
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • check_transit_visa unknown 12h ago

    [needs a free API key — this call will fail without one: https://visa.orizn.app/visa-api/register?source=mcp-remote, then reconnect with ?key=<key>] Transit and layover rules for a country being connected through: airside/landside rules and how many free transit hours its main hubs grant. Call it for layovers, stopovers and connecting flights — not for entering a country as a destination, which is check_visa_requirement. IMPORTANT: this data is modelled PER TRANSIT COUNTRY, not per passport nationality. The answer is the same for every passport, the `passport` argument is recorded but does not narrow the result, and only 44 transit countries are covered. Present the reply as general hub rules to confirm with the airline or the transit country's authority, never as a per-nationality ruling. When the country is not covered the tool answers {status: "unavailable"} instead of guessing. Needs the Starter plan ($149/month, 30,000 requests) or above and costs 1 request. On a free key this call is refused before anything is charged, with the upgrade link.

    mcp-tool

    {
      "type": "object",
      "required": [
        "passport",
        "transit_country"
      ],
      "properties": {
        "lang": {
          "type": "string",
          "description": "Language code. One of: fr, en, es, pt, de, ja, ko, zh, ru, it, ar, hi, th, vi, tl. Defaults to en."
        },
        "passport": {
          "type": "string",
          "description": "Traveller's passport, ISO 3166-1 alpha-3 (e.g. IND). Recorded, but does not narrow the answer."
        },
        "transit_country": {
          "type": "string",
          "description": "Country being transited, ISO 3166-1 alpha-3 (e.g. ARE for a Dubai layover, TUR for Istanbul)."
        }
      },
      "additionalProperties": false
    }
    arguments 22 lines
  • compare_destinations unknown 4h ago

    [needs a free API key — this call will fail without one: https://visa.orizn.app/visa-api/register?source=mcp-remote, then reconnect with ?key=<key>] Compare up to 2525 destinations costs 25 requests. Ask for the destinations the user actually named, not a whole region. Needs the Starter plan ($149/month, 30,000 requests) or above; on a free key this call is refused before anything is charged, with the upgrade link.

    mcp-tool

    {
      "type": "object",
      "required": [
        "passport",
        "destinations"
      ],
      "properties": {
        "lang": {
          "type": "string",
          "description": "Language of the description field. One of: fr, en, es, pt, de, ja, ko, zh, ru, it, ar, hi, th, vi, tl. Defaults to en."
        },
        "passport": {
          "type": "string",
          "description": "Traveller's passport, ISO 3166-1 alpha-3 (e.g. FRA)."
        },
        "destinations": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "1 to 25 ISO 3166-1 alpha-3 destination codes, e.g. [\"JPN\",\"THA\",\"VNM\"]. Duplicates are removed before billing."
        }
      },
      "additionalProperties": false
    }
    arguments 25 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 4b279087d9a9c274.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4b279087d9a9c274/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/4b279087d9a9c274/badge.svg)](https://brick.blue/agent/4b279087d9a9c274?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.