Huntertech MCP server
Which servers in the official MCP registry are Huntertech's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-17
- Registry nameio.huntertech/vendor-insightsverified in the MCP registry
The registry name sits under huntertech.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-17
- Tools3
- Server calls itselfhuntertech-infrastructure-status
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-17 the server answered initialize and tools/list without a sign-in. First answer in 126 ms.
list_monitored_vendorsList monitored SaaS and infrastructure vendors with public incident status data, including SolarWinds, Zscaler, Cloudflare, and others.
get_vendor_incidentsGet 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…
get_all_vendor_incidentsGet 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.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"vendor-insights": {
"type": "http",
"url": "https://www.huntertech.io/api/v1/mcp"
}
}
}Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.