Connect Huntertech and your agent gets 3 tools, among them get_all_vendor_incidents, get_vendor_incidents, list_monitored_vendors. It answers at https://mcp.huntertech.io/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 24 October 2026, succeeded.
AI-ready vendor incident status with public active incidents and plan-scoped history.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
get_all_vendor_incidents | Get the most recent ongoing vendor incidents across all monitored vendors (newest start first). Anonymous maximum is 5. Does not include monitoring-phase incidents unless authenticated history is requested. Inputs: limit, includeResolved, timePeriod |
get_vendor_incidents | Get vendor incident and outage status for one monitored vendor (for example solarwinds, zscaler, cloudflare). Anonymous and active-only calls return the most recent ongoing incidents (not monitoring). Authenticated calls can request resolve Inputs: vendor, limit, includeResolved, timePeriod |
list_monitored_vendors | List monitored SaaS and infrastructure vendors with public incident status data, including SolarWinds, Zscaler, Cloudflare, and others. |
Every block below points at https://mcp.huntertech.io/mcp. Pick your client and copy.
claude mcp add --transport http huntertech https://mcp.huntertech.io/mcp
{
"mcpServers": {
"huntertech": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.huntertech.io/mcp"]
}
}
}{
"mcpServers": {
"huntertech": {
"url": "https://mcp.huntertech.io/mcp"
}
}
}{
"servers": {
"huntertech": {
"type": "http",
"url": "https://mcp.huntertech.io/mcp"
}
}
}{
"context_servers": {
"huntertech": {
"url": "https://mcp.huntertech.io/mcp"
}
}
}{
"mcpServers": {
"huntertech": {
"serverUrl": "https://mcp.huntertech.io/mcp"
}
}
}{
"mcpServers": {
"huntertech": {
"url": "https://mcp.huntertech.io/mcp"
}
}
}name: Huntertech
version: 0.0.1
schema: v1
mcpServers:
- name: Huntertech
type: streamable-http
url: https://mcp.huntertech.io/mcp{
"mcpServers": {
"huntertech": {
"httpUrl": "https://mcp.huntertech.io/mcp"
}
}
}{
"mcpServers": {
"huntertech": {
"type": "http",
"url": "https://mcp.huntertech.io/mcp"
}
}
}{
"mcpServers": {
"huntertech": {
"url": "https://mcp.huntertech.io/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.huntertech.io%2Fmcp&type=streamable_http&id=huntertech&name=Huntertech
It answered our last check on 24 October 2026 in 369 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by huntertech.io and served from mcp.huntertech.io, the vendor's own domain: https://mcp.huntertech.io/mcp.
3, as returned by the server's own tools/list on 22 September 2026: get_all_vendor_incidents, get_vendor_incidents, list_monitored_vendors.
It answered our last check on 24 October 2026 in 369 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.huntertech.io/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.huntertech. Endpoint host: mcp.huntertech.io. ARD identifier: urn:air:io.huntertech:mcp:vendor-insights.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.