check_entry_requirements — visa check MCP Tool Read-only
check_entry_requirements
(check entry requirements) is one of 3 tools on the
visa check
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_entry_requirements from your client
- Claude Code visa check check_entry_requirements run in your project directory
- Claude Desktop visa check check_entry_requirements ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor visa check check_entry_requirements ~/.cursor/mcp.json
- VS Code visa check check_entry_requirements .vscode/mcp.json
- Zed visa check check_entry_requirements ~/.config/zed/settings.json
- Windsurf visa check check_entry_requirements ~/.codeium/windsurf/mcp_config.json
- Cline visa check check_entry_requirements ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI visa check check_entry_requirements ~/.gemini/settings.json
- Grok visa check check_entry_requirements .mcp.json (in your project root)
- ChatGPT visa check check_entry_requirements Settings → Connectors → Advanced → Developer mode
- Claude.ai visa check check_entry_requirements Settings → Connectors → Add custom connector
- LangChain visa check check_entry_requirements pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http visa-check https://api.canienter.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.