# Connect an AI Assistant (MCP)

> Use Fidro from ChatGPT, Claude, Cursor, VS Code, Codex or Claude Code through the Fidro MCP server.

**Category:** getting-started | **Last updated:** September 6, 2026

---

Fidro has an MCP server at `https://fidro.io/mcp`. Connect it to an AI assistant and you can ask things like "is this signup risky?", "where is this IP?" or "add this email to our blocklist" without leaving the chat. It uses the [Model Context Protocol](https://modelcontextprotocol.io), which ChatGPT, Claude, Cursor, VS Code, Codex, Claude Code, Gemini CLI and Windsurf all speak.

Access is through OAuth, not API keys. The first time an assistant connects, Fidro sends you to a consent screen, you approve it, and the assistant receives a token limited to your account. No key ever leaves the dashboard.

## What the assistant can do

| Tool | What it does | Plan |
|------|--------------|------|
| `validate_signup` | Score an email and/or IP the same way the `/validate` endpoint does: disposable email, VPN, proxy, Tor, geo-mismatch, blocklists. | All plans |
| `lookup_ip` | Location and network details for one IP address. | All plans |
| `get_account_status` | Your plan, this month's usage and remaining quota. | All plans |
| `list_blocklist` | Read your account's blocklist entries, filtered by type, value or severity. | Starter and above |
| `add_to_blocklist` | Add an email, IP, domain or card fingerprint to your blocklist. | Starter and above |
| `remove_from_blocklist` | Remove an entry. The assistant has to confirm with you first. | Starter and above |

Validations and IP lookups made through an assistant run against live data and **count against your monthly quota** exactly like a live API request. They appear in your audit log under a key called "Connected assistants (MCP)". An assistant cannot create or delete API keys, change your plan or touch billing.

## Connect from your assistant

### ChatGPT

1. Open **Settings**, then **Connectors**, then **Create** (you need Developer mode enabled under Settings, Apps and Connectors, Advanced settings).
2. Name it `Fidro`, paste `https://fidro.io/mcp` as the server URL, leave authentication on **OAuth** and save.
3. Click **Connect**. ChatGPT opens the Fidro consent screen. Approve it.

ChatGPT will then offer Fidro's tools in any conversation where you enable the connector.

### Claude (web and desktop)

1. Open **Settings**, then **Connectors**, then **Add custom connector**.
2. Name it `Fidro` and paste `https://fidro.io/mcp`. Leave the client ID and secret empty.
3. Click **Add**, then **Connect** and approve on the consent screen.

### Claude Code

```bash
claude mcp add -s user --transport http fidro https://fidro.io/mcp
claude mcp login fidro
```

The `-s user` flag registers the server for every project. Without it the server is only visible in the directory you ran the command from.

### Codex

```bash
codex mcp add fidro --url https://fidro.io/mcp
codex mcp login fidro
```

### Cursor

Open **Cursor Settings**, then **MCP**, then **Add new MCP server**, choose the **Streamable HTTP** transport and enter `https://fidro.io/mcp`. Or add this to `.cursor/mcp.json`:

```json
{
  "mcpServers": {
    "fidro": {
      "url": "https://fidro.io/mcp"
    }
  }
}
```

Cursor prompts you to sign in the first time it uses the server.

### VS Code

Run **MCP: Add Server** from the command palette, choose **HTTP**, enter `https://fidro.io/mcp` and name it `fidro`. Or add this to `.vscode/mcp.json`:

```json
{
  "servers": {
    "fidro": {
      "type": "http",
      "url": "https://fidro.io/mcp"
    }
  }
}
```

### Gemini CLI

```bash
gemini mcp add --transport http fidro https://fidro.io/mcp
```

### Windsurf

Add the same `url` entry under `mcpServers` in Windsurf's `mcp_config.json`.

## Things to try

- "Validate this signup: alice@mailinator.com from 185.220.101.1."
- "Where is 203.0.113.9 and is it a VPN?"
- "How much of my Fidro quota is left this month?"
- "Show me every IP on our blocklist with severity 8 or higher."
- "Add chargebacks@example.com to the blocklist with reason 'disputed twice'."

## Managing access

Every assistant you connect is listed under **Connected assistants** on the [API keys](/app/api-keys) page. **Disconnect** revokes that assistant's tokens immediately; it will have to go through the consent screen again to reconnect. Tokens expire after an hour and refresh on their own for 90 days of inactivity.

## Troubleshooting

**"API keys are not accepted by the MCP server"**
The assistant is sending an `sk_live_` or `sk_test_` key as the bearer token. MCP uses OAuth; remove the key from the server config and let the assistant sign in.

**The consent screen says the app cannot be authorised**
The assistant registered with a redirect URL Fidro does not recognise. Reconnect from the assistant's own settings rather than a copied config, so it registers a fresh client.

**"Monthly request quota exceeded"**
The assistant's validations share your account quota. Wait for the reset date shown in the message or upgrade from [account settings](/app/settings/account).

**"Blocklists are not included in your current plan"**
The three blocklist tools need Starter or above. Validations and IP lookups work on every plan.

**Claude Code says "No MCP server named fidro"**
The server was added without `-s user`, so it only exists in one project directory. Run the `claude mcp add` command again with `-s user`.