Visa Grep Sign in

Connect Visa Grep to your AI assistant

Ask your AI assistant about any employer's H-1B record and the rules behind it, and get answers with the government's own numbers and citations. Visa Grep is an MCP server, so it works in ChatGPT, Claude and any other app that speaks MCP. Free with a Visa Grep account.

ChatGPT Claude Coding tools

Server URL
https://visagrep.com/mcp
Transport
Streamable HTTP
Sign-in
Google (OAuth), or an API key
Limits
1,000 requests a day and 60 a minute, per account
Server URL
https://visagrep.com/mcp
Or send a key
Authorization: Bearer vg_...

What it is

MCP, the Model Context Protocol, is the open standard AI assistants use to call tools from other services. Visa Grep's MCP server gives your assistant three tools, the same lookups as the API. They only read: they can't change anything, in Visa Grep or anywhere else.

The MCP server's tools
ToolWhat it doesSame as
search_companiesFinds a company by name.GET /api/v1/search
get_companyOne company's whole record.GET /api/v1/companies/{key}
search_regulationsPassages from the H-1B rules.GET /api/v1/regulations

Your assistant reads the numbers and citations the tools return, under the same rules as every page here: no predictions, no rankings, and the Department of Labor's and USCIS's counts kept apart.

ChatGPT

  1. Turn on developer mode

    In ChatGPT on the web, open Settings, then Security and login, and turn on Developer mode.

  2. Add the server

    Go to Plugins and choose +. Give it a name, such as Visa Grep, and under Connection paste this URL, then create it:

    Server URL
    https://visagrep.com/mcp
  3. Sign in and allow

    ChatGPT sends you to Visa Grep. Sign in with Google on Visa Grep, then choose Allow. You don't need a key: the app gets its own access, which you can disconnect on your account page.

  4. Use it in a chat

    Start a new chat and add Visa Grep from the tools menu.

Developer mode is on ChatGPT's paid plans. In a Business, Enterprise or Edu workspace, an admin may have to allow it first.

Claude

  1. Open Connectors

    In claude.ai or Claude Desktop, go to Customize, then Connectors, and choose Add custom connector.

  2. Paste the URL

    Give it a name, such as Visa Grep, and this URL, then choose Add:

    Server URL
    https://visagrep.com/mcp
  3. Sign in and allow

    Choose Connect. Sign in with Google on Visa Grep, then choose Allow. You don't need a key: the app gets its own access, which you can disconnect on your account page.

Connectors you add there work in Claude Desktop and the Claude mobile apps too. On a Team or Enterprise plan, an Owner adds it first, under Organization settings, Connectors, Add, Custom, then each person connects with their own account.

Coding tools

Add the server, then sign in from the tool, or send a key instead.

Shell
claude mcp add --transport http visagrep https://visagrep.com/mcp

Then, in Claude Code, run /mcp, choose visagrep and sign in. Your browser opens Visa Grep: sign in with Google and choose Allow. Or skip signing in and send a key from your account page:

Shell
claude mcp add --transport http visagrep https://visagrep.com/mcp --header "Authorization: Bearer vg_..."
Shell
codex mcp add visagrep --url https://visagrep.com/mcp
codex mcp login visagrep

The login opens Visa Grep in your browser: sign in with Google and choose Allow. Or, in ~/.codex/config.toml, read a key from your account page out of an environment variable:

TOML
[mcp_servers.visagrep]
url = "https://visagrep.com/mcp"
bearer_token_env_var = "VISAGREP_API_KEY"
Shell
gemini mcp add --transport http visagrep https://visagrep.com/mcp

Then, in Gemini CLI, run /mcp auth visagrep and sign in. Or send a key from your account page:

Shell
gemini mcp add --transport http --header "Authorization: Bearer vg_..." visagrep https://visagrep.com/mcp

For GitHub Copilot, in .vscode/mcp.json. VS Code asks you to sign in the first time it starts the server.

JSON
{
  "servers": {
    "visagrep": {
      "type": "http",
      "url": "https://visagrep.com/mcp"
    }
  }
}

In ~/.cursor/mcp.json, with a key from your account page in place of vg_.... Or leave out headers and sign in when Cursor asks.

JSON
{
  "mcpServers": {
    "visagrep": {
      "url": "https://visagrep.com/mcp",
      "headers": {
        "Authorization": "Bearer vg_..."
      }
    }
  }
}

Any other app

Any app that speaks MCP over streamable HTTP can use the same URL. If it can sign in with OAuth, sign in with Google and allow it. If it can't, send your key from your account page as a header on every request:

Header
Authorization: Bearer vg_...

Sign-in works for apps that come back to a web address or to your own computer. An app that asks to come back to its own link scheme, such as myapp://, is refused: use a key there.

Limits

1,000 requests a day and 60 a minute, per account, shared with the API. Every request counts, including the few each connection makes to start, and a request over a limit is refused, not charged. More on limits.

What to ask

Once it's added, ask in your own words. For example:

  • Does Infosys sponsor H-1B visas? Show the DOL and USCIS numbers separately.
  • What did Google offer software engineers on its H-1B filings last year?
  • Has Stripe filed green cards for its employees?
  • What does the law say about cap-exempt employers? Cite the rule.

Your assistant answers from the records, which are the past. It won't predict anyone's case, and none of this is legal advice.

Privacy

Connecting stores the app's name, when you allowed it and when it last made a request, and hashes of its tokens; never your questions. What the app does with the answers is up to its maker's policies. The details are in our Privacy Policy.