Live vendor incidents in your AI assistant. Hundreds of status pages, one feed. Free active-outage checks with no signup; sign in for history, watchlists, and monitoring tools. Setup: https://www.huntertech.io/vendor-mcp
Scored across 4 tools
get_pricing and list_monitored_vendors are clearly distinct from incident retrieval, but get_all_vendor_incidents and get_vendor_incidents share nearly identical names, filters, and tier limits, so an agent could pick the cross-vendor snapshot when it wanted a single vendor. The descriptions do disambiguate (cross-vendor vs. one monitored vendor, id required), which keeps it from being a real collision.
All four tools follow a consistent snake_case verb_noun pattern (get_*, list_*), with get_all_vendor_incidents being a natural variant of get_vendor_incidents rather than a style break. No camelCase or vague single-word names.
Four tools is slightly lean but each one is purposeful: list vendors, list incidents per vendor, snapshot all incidents, and pricing. The surface is deliberately minimal for guests, with documented expansion after sign-in, so the low count is by design rather than bloat or filler.
The public surface covers vendor discovery and incident listing but has notable gaps: no single-incident detail lookup, no incident history (gated behind Standard), and no maintenance or probe/analytics operations without sign-in. Agents can partially work around this by filtering the vendor incident list, but they hit a hard wall on detail and history.
Read-only cross-vendor incident snapshot (newest start first). Guest and Free: ongoing plus monitoring only, max 5. Optional status filters ongoing, monitoring, or resolved; resolved requires Standard or higher (includeResolved, timePeriod, or status=resolved). Signed-in callers get additional tools via tools/list, including get_incident per vendor.
Inputs: limit, status, timePeriod, includeResolved. Returns: total, success, vendorId, checkedAt, +7 more
Public plan matrix from /pricing (USD tiers and MCP entitlements). Separate from incident monitoring: use list_monitored_vendors and get_vendor_incidents for outages. Guest tools/list includes this for discovery; Standard+ sign-in (API key or OAuth at https://mcp.huntertech.io/mcp/auth) reveals history, get_incident, maintenance, probes, and watchlists.
Inputs: no named parameters.
Read-only incidents for one monitored vendor. Guest and Free: ongoing plus monitoring only, max 5 (default when status is omitted). Optional status narrows to ongoing, monitoring, or resolved; resolved history requires Standard or higher (use includeResolved, timePeriod, or status=resolved). After sign-in, tools/list also exposes get_incident for a single record by id.
Inputs: vendor (required), limit, status, timePeriod, +1 more. Returns: total, success, vendorId, checkedAt, +7 more
Guest-safe index of vendors with public incident feeds (id, name, category, website). Pass id to get_vendor_incidents. Sign in with Huntertech MCP OAuth or an API key to expand tools/list with history (includeResolved, timePeriod), get_incident, maintenance, and analytics.
Inputs: no named parameters. Returns: total, success, vendors, accessLevel
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.
