Vendor Insights MCP

Ask your assistant about vendor incidents

Connect Huntertech to Claude, Perplexity, Grok, or Cursor so your assistant can pull live vendor context while you investigate, instead of copying from status pages.

How to connect your assistant

Pick your client, follow the steps, and paste the Huntertech MCP server URL. No API keys required for active incidents.

Add Huntertech in Claude

1Open Settings → MCP (or edit your Claude MCP config file)
2Add a new remote MCP server

Name: Huntertech
MCP Server URL: https://mcp.huntertech.io/mcp
Transport: Streamable HTTP
Authentication: None (for public active incidents); sign in via OAuth for history

Prefer Claude Code direct MCP config over claude.ai chat connectors.

Manual config snippet

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

Example prompts

“What active incidents does Cloudflare have right now?”
“List monitored vendors with ongoing outages.”
“Summarize recent Zscaler incidents for my incident bridge.”

Tools exposed to assistants

list_monitored_vendors
Browse supported vendor slugs.
get_vendor_incidents
Pull incidents for one vendor.
get_all_vendor_incidents
Scan active outages across vendors.

Public access returns active incidents only (up to 5 per call). Sign in through MCP OAuth to unlock resolved history within your plan window.

Ask your assistant about vendor incidents

AI workflows with vendor context

How to connect your assistant

Add Huntertech in Claude

Example prompts

Tools exposed to assistants

Ask your assistant about vendor incidents

AI workflows with vendor context

How to connect your assistant

Add Huntertech in Claude

Example prompts

Tools exposed to assistants