mcp server
Huntertech.io Vendor Insights
AI-ready vendor incident status with public active incidents and plan-scoped history.
Description as published by the maintainer. Source
- version 1.0.0
- slowing
slowing — Registry entry last updated 2026-05-07.
What this server can do
3 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
get_all_vendor_incidents(limit, timePeriod, includeResolved)- 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.
get_vendor_incidents(limit, vendor, timePeriod, includeResolved)- 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 resolved history within the user plan window. Required: vendor.
list_monitored_vendors- List monitored SaaS and infrastructure vendors with public incident status data, including SolarWinds, Zscaler, Cloudflare, and others.
Last successful function declaration observed on . Source: https://www.huntertech.io/api/v1/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://www.huntertech.io/api/v1/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-05-07 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-05-07 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 3 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | www.huntertech.io | |
| mcp endpoint status | ok | The server listed 3 functions when asked. | as of probe | www.huntertech.io |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json