Use InstaVision from Claude, ChatGPT and your AI tools.
Connect it once as an MCP server. Then ask in plain words — your assistant runs the search, reads the proof and exports the list, on your credits.
https:/ / instavision.co/ api/ connect/ mcpConnect in three steps
Add a custom connector
In claude.ai, open Settings → Connectors and choose Add custom connector.
Paste the server URL
Name it InstaVision and paste the URL above.
https:// instavision.co/ api/ connect/ mcp Sign in and ask
Sign in to InstaVision when Claude asks, approve access, then describe who you need in any chat.
Add a custom MCP server
On chatgpt.com, open Plugins (chatgpt.com/plugins), select + and choose Add custom MCP server. No such option? Turn on Developer mode in Settings → Apps → Advanced settings; in a Business, Enterprise or Edu workspace an admin enables it.
Paste the server URL
Name it InstaVision, paste the MCP server URL above under Connection, and pick OAuth for authentication. Confirm the warning, then select Create as a plugin.
Sign in and ask
Sign in to InstaVision and approve access. In a new chat, type @, pick InstaVision and describe who you need. ChatGPT asks you to confirm before a search spends credits.
Needs a paid ChatGPT plan — Plus, Pro, Business, Enterprise or Edu. Add it on the web; it then works in your ChatGPT account.
Ask Grok Bot to add it
In a Grok Bot chat, write: “Add a custom MCP server called instavision at https://instavision.co/api/connect/mcp”. Say “custom”, or it looks for a marketplace plugin. Check the URL it shows and choose Add it.
Sign in
On the card Grok Bot posts, choose Authorize, sign in to InstaVision in the browser and approve access.
Ask
Type @, pick InstaVision and describe who you need. The server is shared by every Bot on your Grok account.
Sign-in keeps failing? Create a key in Settings → API keys and ask Grok Bot to add a custom MCP server at https://instavision.co/api/mcp/mcp with the header Authorization: Bearer <your key>. It keeps the key on the server entry, not in the URL.
Remote, with your API key in a header
Paste into a terminal (bash or zsh) and press Enter. It then waits for your key: paste it and press Enter. The key isn't shown or saved to your shell history; Claude Code stores it in ~/.claude.json and makes the server available in every project.
read -rs INSTAVISION_API_KEY && claude mcp add --scope user --transport http instavision https://instavision.co/api/mcp/mcp --header "Authorization: Bearer $INSTAVISION_API_KEY"
Remote, with your API key in a header
Add to ~/.cursor/mcp.json, then restart Cursor. It reads the key from the INSTAVISION_API_KEY environment variable, so set that in the environment it starts from.
{"mcpServers":{"instavision":{"url":"https://instavision.co/api/mcp/mcp","headers":{"Authorization":"Bearer ${env:INSTAVISION_API_KEY}"}}}}Remote, with your API key in a header
Run in a terminal. It reads the key from the INSTAVISION_API_KEY environment variable, so set that in the environment it starts from.
codex mcp add instavision --url https://instavision.co/api/mcp/mcp --bearer-token-env-var INSTAVISION_API_KEY
Remote, with your API key in a header
Add to .vscode/mcp.json in your workspace. VS Code asks for the key once, when the server starts, and stores it for later.
{
"inputs": [
{
"type": "promptString",
"id": "instavision-api-key",
"description": "InstaVision API key",
"password": true
}
],
"servers": {
"instavision": {
"type": "http",
"url": "https://instavision.co/api/mcp/mcp",
"headers": { "Authorization": "Bearer ${input:instavision-api-key}" }
}
}
}Through the instavision-mcp npx bridge (needs Node.js)
Settings → Developer → Edit Config, add the block below with your key in place of iv_sk_..., then restart Claude Desktop. It runs the npx bridge, which needs Node.js.
{
"mcpServers": {
"instavision": {
"command": "npx",
"args": ["-y", "instavision-mcp"],
"env": { "INSTAVISION_API_KEY": "iv_sk_..." }
}
}
}On Windows, if npx fails to launch, use "command": "cmd" with "args": ["/c", "npx", "-y", "instavision-mcp"].
Client asks for an API key instead? Create one in Settings → API keys and paste it there. Keep it private — it spends your credits.
What your assistant can do
The same engine as the website. These are the tools it reaches for most; others manage your plan and the accounts you've already received.
- Launch a search from a descriptionA plain-language brief in, a running search out — with the spending cap you agreed.
launch_discovery - Check statusHow many found so far, and why it stopped.
get_run_status - Read results with proofThe matches with their reasons, page by page — profile text comes back as data, never as instructions.
get_run_results - Export PDFA shareable PDF of the results, behind a link that expires after 1 hour.
export_run_pdf - Open extra matchesWhen a search verified more accounts than you asked for, open them at the price of a match each — with your yes.
open_extra_matches - Repeat a search weeklyThe same brief every week, for accounts you don't have yet. You pay per verified match; turn it off anytime.
set_weekly_search - Check balanceCredits left and your plan — with one link to subscribe when you have none.
get_balance - Estimate creditsThe most a search can cost before you say yes. Works without an API key.
estimate_credits
Illustration — the accounts and the conversation are made up.