AI Agents Can Now Check Visa Status. Why the Read-Only Part Matters
Synergised Consulting Ltd
Last Updated: 9 November 2026
An AI agent can now check travel authorisation status through a standard interface: an MCP server gives the agent read-only tools to answer whether a trip needs an authorisation, whether an application has been approved, and whether an existing approval is still live, while any actual submission stays interface: an MCP server gives the agent read-only tools to answer whether a trip needs an authorisation, whether an application has been approved, and whether an existing approval is still live, while any actual submission stays behind an explicit human go-ahead. The interesting boundary is that there is no public API to call for these checks: when a status genuinely matters, the government's own advice is to check its official site. That read-only shape, not the travel use case, is what generalises.
What an MCP status server actually gives an agent
An MCP server for travel authorisations gives an agent a short list of tools: check whether a passport and destination combination requires an authorisation, look up the documents and fees, estimate processing time, create a link to the application, and read back the status of applications made through that provider. The Model Context Protocol is the specification that makes this work without a custom integration per system: servers expose tools that an agent discovers and calls at runtime, each with a defined schema [1].
The protocol's own specification is explicit about where control sits. Tools are model-controlled, meaning the model can invoke them automatically, and for that reason the spec recommends that there should always be a human in the loop with the ability to deny a tool invocation [1]. A status server built to that recommendation separates its tools into two groups: the ones that answer questions, which the agent can call freely, and the one that files something, which waits for a person to confirm. The agent is a caller. It is never the authority.
The three status types an agent must separate
The questions people ask about travel authorisations look like one question and are actually three. Requirement status asks whether an authorisation is needed at all for this passport and destination. Application status asks whether a submitted application is approved, refused or pending. Validity status asks whether an existing approval still covers the traveller's passport and travel dates. An agent that keeps the three apart answers precisely and cites the right source for each; an agent that merges them produces the confident, useless answer that stalls a booking.
Work through a concrete example. A founder is booking a trip to New York and asks an assistant whether "the visa is sorted". A useful answer separates the three questions. Requirement: yes, an ESTA is needed for this passport. Application: it was submitted on Tuesday, so it must be confirmed at least 72 hours before boarding, per CBP's own guidance [2]. Validity: this is a new application, so nothing is live yet; the fee is $40 and an approval generally lasts two years or until the passport expires, whichever comes first [2]. Three answers, each from a different source, each actionable.
Why there is no government API to call
Here is the part that surprises people: there is no public API that returns an individual's ESTA or ETA status. For ESTA, CBP's advice to anyone who used a third-party site is to take the application number and check on the official government site, because the government has no way of knowing whether the information passed through that site was accurate [2]. CBP has warned travellers directly against third-party ESTA sites, which it says are not endorsed by, associated with, or affiliated in any way with the US government, and it states plainly that using one does not expedite approval [3]. For UK visas, GOV.UK answers the question through its own Check UK visa service [6]. When even the application channel is this tightly controlled, an agent has no back door: it works from official guidance, reads application status through a provider's interface where one exists, and directs everything else to the official site with a link. An agent that cannot verify something should say so, not improvise.
What this looks like in practice, done well and done badly
Done well: the agent is connected to the official guidance, answers the requirement question in seconds, notes that a Visa Waiver Program trip is limited to 90 days or less [4], and flags that an application it cannot see must be checked on esta.cbp.dhs.gov before the 72-hour window closes. The owner confirms the submission itself, once, in one place.
Done badly: the agent is pointed at no verified source and answers from memory. Travel rules change and model knowledge ages, so the answer is delivered confidently and wrong in exactly the cases that cost money: a lapsed approval, a passport renewed since the authorisation was granted, a nationality that needs a full visa. The failure is invisible until boarding.
The same pattern works for status checks you can build today
The travel example matters because it shows a shape, not because readers are booking flights through agents. Every business has regulated status lookups: is this company still active, has this filing been made, is this certification current. Wherever an official body publishes its register, the same read-first design applies.
The Companies House API is a working UK example: the register of companies is public, the data is live and real-time, and access is through a simple REST interface [5]. An agent given a read-only tool against that register can answer "is this supplier's company still active and who are its directors" in seconds, with the answer coming from the official source rather than from the model's memory. That is a lookup a small business can genuinely delegate, because the tool cannot change anything; it can only read. GOV.UK's own Check UK visa service shows the complementary case: where no API exists, the correct delegation is a direct link to the official checker, not a paraphrase [6].
Where the line sits for your own workflows
Three rules travel straight from this pattern into any business workflow. First, give the agent read-only tools wherever possible; a tool that answers questions cannot do damage the way a tool that files paperwork can. Second, put anything that writes, submits or pays behind an explicit approval, and name the person who gives it; the specification's human-in-the-loop recommendation exists precisely for this [1]. Third, keep a register of which lookups are delegated, which official source each one reads from, and where the write gates are. The register is what lets you answer, months later, what the agent was actually allowed to do.
What this means for your first hundred days
In discovery workshops, owners rarely arrive with a list of what to automate. It gets built in the conversation, walking through a normal week task by task, and the tasks that separate themselves first are exactly this kind: repetitive, low-risk lookups that someone performs again and again through a normal week, where the answer exists in an official system and the only real work is fetching it. Status checks fit that description almost perfectly.
So the operating question this news raises for a new owner is narrow and practical: which status lookups in your business does someone perform repeatedly, from an official source, with no judgement attached? Those are the first candidates for a read-only agent tool, with the submission-style steps left behind a named approval. Start with one, keep the tool register current, and expand only when the first one has quietly stopped costing anyone time.
Sources
- [1] Model Context Protocol specification, Tools:
- [2] US Embassy in the UK, CBP's Electronic System for Travel Authorization (ESTA):
- [3] US Customs and Border Protection, CBP Warns Against Third-Party Site Use for ESTA Applications:
- [4] Official ESTA Application Website, US Customs and Border Protection:
- [5] Companies House API overview:
- [6] GOV.UK, Check UK visa: