Travel Entry Requirements returns what a destination asks of a visitor's passport and health documents: how long the passport must stay valid and from when, and whether a yellow fever certificate is required. Paid plans add a passport check against your trip dates, the blank pages it needs, the Schengen 10-year issue rule, the current UK and US travel advisory levels and plain-English guidance for each rule.
Enable Travel Entry Requirements and it becomes a tool your agent calls over MCP to check itself against live data before it answers — grounding the response instead of guessing.
Travel Entry Requirements rides the one VerveContext MCP endpoint alongside 300+ other sources, so adding it to an agent is a toggle, not an integration.
The agent pulls travel entry requirements at answer time and can carry the source with the result, so the reasoning stays current and auditable.
Point your agent framework at the VerveContext endpoint. Every enabled source — this one included — becomes a tool the model can call. No per-source plumbing.
{
"mcpServers": {
"vervecontext": {
"url": "https://api.vervecontext.com/v1/mcp",
"headers": { "x-api-key": "vc_live_••••" }
}
}
}Each call returns structured fields your agent can read.
destinationdestinationNamepassportValidityblankPagesRequiredpassportCheckyellowFeveradvisoriesrulesUpdatedAtHow to ground an agent in it over MCP.
Same data, same VerveContext account, same credit balance — one key works on all of them.