Index / MCP servers / iVisa

iVisa MCP server

iVisa is a remote MCP server that gives an AI agent 1 tool, among them visa_availability. It answers at https://www.ivisa.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 5 September 2026; the last check, on 18 October 2026, succeeded.

Status
Answering
Tools
1
Official
yes, served from ivisa.com
Reliability
10 of 10 checks
Response time
359 ms
Transport
streamable HTTP
Last checked
18 October 2026

Check visa requirements and travel documents for international travel destinations.

Description as the publisher wrote it.

The 1 tool iVisa offers

ToolWhat it does
visa_availabilityProvides visa availability for a given country, destination, and currency
Inputs: nationality, destination, currency

Add iVisa to your AI client

Every block below points at https://www.ivisa.com/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http ivisa https://www.ivisa.com/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "ivisa": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://www.ivisa.com/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "ivisa": {
      "url": "https://www.ivisa.com/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "ivisa": {
      "type": "http",
      "url": "https://www.ivisa.com/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "ivisa": {
      "url": "https://www.ivisa.com/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "ivisa": {
      "serverUrl": "https://www.ivisa.com/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "ivisa": {
      "url": "https://www.ivisa.com/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: iVisa
version: 0.0.1
schema: v1
mcpServers:
  - name: iVisa
    type: streamable-http
    url: https://www.ivisa.com/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "ivisa": {
      "httpUrl": "https://www.ivisa.com/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "ivisa": {
      "type": "http",
      "url": "https://www.ivisa.com/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "ivisa": {
      "url": "https://www.ivisa.com/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fwww.ivisa.com%2Fmcp&type=streamable_http&id=ivisa&name=iVisa

Is iVisa up right now?

It answered our last check on 18 October 2026 in 359 ms. Over 10 checks since 5 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to iVisa

Questions about iVisa

Is there an official iVisa MCP server?

Yes. It is published by ivisa.com and served from www.ivisa.com, the vendor's own domain: https://www.ivisa.com/mcp.

How many tools does iVisa have?

1, as returned by the server's own tools/list on 31 August 2026: visa_availability.

Is iVisa down?

It answered our last check on 18 October 2026 in 359 ms. Over 10 checks since 5 September 2026 it answered 10.

How do I add iVisa to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://www.ivisa.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does iVisa need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: com.ivisa.www. Endpoint host: www.ivisa.com. ARD identifier: urn:air:com.ivisa.www:mcp:mcp. First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.