Huntertech MCP connects an assistant to vendor incident status. No API key is required for active incidents.

Add the server with the client steps below, then call a public tool to confirm it. Sign in with Huntertech OAuth when resolved history or account tools are needed.

- Add the Huntertech MCP server
- Confirm the connection with a public tool call
- Sign in with OAuth if resolved incident history or account tools are needed

---

## Huntertech MCP endpoints

Streamable HTTP (recommended for most clients):

`https://mcp.huntertech.io/mcp`

Sign-in URL. This returns 401 until the user signs in, then serves that plan's tools:

`https://mcp.huntertech.io/mcp/auth`

SSE (Perplexity and other SSE-only clients):

`https://mcp.huntertech.io/mcp/sse`

Compatibility on the main site:

- `POST https://www.huntertech.io/api/v1/mcp`
- `GET https://www.huntertech.io/api/v1/mcp/sse`

Product overview: `https://www.huntertech.io/vendor-mcp`

---

## Install for your agent

Use the section that matches the user's client.

### Cursor

Prefer the one-click deep link when the user is on a machine with Cursor installed:

```
cursor://anysphere.cursor-deeplink/mcp/install?name=huntertech-vendor-insights&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vbWNwLmh1bnRlcnRlY2guaW8vbWNwIn0=
```

Or add to `.cursor/mcp.json` (project) or the user-level MCP config under `mcpServers`:

```json
{
  "mcpServers": {
    "huntertech-vendor-insights": {
      "type": "http",
      "url": "https://mcp.huntertech.io/mcp"
    }
  }
}
```

Restart Cursor or reload MCP after editing. OAuth triggers on first use when the user needs authenticated history.

### Claude (Claude Code / desktop MCP)

Add a remote HTTP MCP server in the user's Claude MCP config:

```json
{
  "mcpServers": {
    "huntertech-vendor-insights": {
      "type": "http",
      "url": "https://mcp.huntertech.io/mcp"
    }
  }
}
```

Prefer direct MCP in Claude Code over claude.ai chat connectors when possible.

### Grok (xAI)

1. Open `https://grok.com/connectors`
2. New Connector → Custom
3. Name: `Huntertech`
4. MCP Server URL: `https://mcp.huntertech.io/mcp`
5. Transport: Streamable HTTP
6. Authentication: None for `https://mcp.huntertech.io/mcp`. Use `https://mcp.huntertech.io/mcp/auth` when the user should sign in.

### Perplexity

1. Settings → Connectors → Custom connector → Remote
2. Name: `Huntertech`
3. MCP Server URL: `https://mcp.huntertech.io/mcp/sse`
4. Transport: SSE
5. Authentication: None (for public active incidents)

If Streamable HTTP is available, use `https://mcp.huntertech.io/mcp` instead.

### ChatGPT (custom MCP app)

1. Enable developer mode in ChatGPT Apps settings when required by the user's plan
2. Apps → Create → custom MCP app
3. MCP Server URL: `https://mcp.huntertech.io/mcp`
4. Scan tools, then create the app

Custom MCP apps are web-only on supported Business or Enterprise plans.

### Gemini CLI

Add to `~/.gemini/settings.json` under `mcpServers`:

```json
{
  "mcpServers": {
    "huntertech-vendor-insights": {
      "httpUrl": "https://mcp.huntertech.io/mcp"
    }
  }
}
```

Or run:

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

### Other MCP clients

Add a remote server:

- Name: `Huntertech` or `huntertech-vendor-insights`
- URL: `https://mcp.huntertech.io/mcp` (Streamable HTTP) or SSE URL above
- Authentication: None for anonymous public tools; OAuth when the user needs history beyond active incidents

---

## Verify the connection

After MCP reload, call a public tool, for example:

- `list_monitored_vendors`
- `get_vendor_incidents` with a vendor such as `cloudflare` or `zscaler`
- `get_all_vendor_incidents` for a cross-vendor active scan

Anonymous access includes active and monitoring incidents (plan limits apply). Resolved history, maintenance, advisories, analytics, probes, and watchlist edits require the user's Huntertech account via OAuth.

If a connector was added before the public tool list was narrowed, remove it and add it again. A restart can keep the old tool catalog.

OAuth discovery (when the client supports it):

- `GET https://mcp.huntertech.io/.well-known/oauth-authorization-server`
- `GET https://mcp.huntertech.io/.well-known/oauth-protected-resource/mcp`
- `GET https://mcp.huntertech.io/.well-known/oauth-protected-resource/mcp/auth`

---

## When finished

A useful confirmation:

```
Huntertech MCP setup complete
- Server: https://mcp.huntertech.io/mcp
- Try: "What active incidents does Cloudflare have right now?"
- Docs: https://www.huntertech.io/vendor-mcp
```

This page is published at `https://www.huntertech.io/agent-setup/prompt.md`.