Claude MarketplacesSubmit
huntertech avatar

Huntertech

io.huntertech/vendor-insights

This connects to HunterTech's vendor incident tracking system, giving Claude direct access to current service outages and historical incident data across third-party vendors. You get public active incidents out of the box, with deeper history access based on your HunterTech plan tier. Reach for this when you need Claude to check vendor status during incident response, correlate outages across your stack, or pull historical incident patterns without context switching to a status dashboard. The streamable HTTP transport means it works through Claude's remote MCP capabilities without local setup.

tools
4
transport
HTTP, SSE
last updated
Oct 24, 2026
Open website

Install

From registry metadata
$ npx add-mcp https://mcp.huntertech.io/mcp --name vendor-insights

Run in your terminal. add-mcp asks which agents to add it to (Claude Code, Codex, Cursor and more). Add -g to install it for every project.

Review the command, arguments and environment values before installing. MCP servers run with your local permissions.

Other ways

Claude Code

$ claude mcp add --transport http vendor-insights https://mcp.huntertech.io/mcp

Run in your terminal. Add --scope user to make it available in every project.

Tools

Verified live · 4 tools

Verified live against the running server on Nov 6, 2026.

list_monitored_vendorsGuest-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.

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.

No parameters. Call it with no arguments.

get_vendor_incidentsRead-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 st...5 params

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 st...

Parameters* required
includeResolvedboolean
Include resolved incidents in the fetch. Requires Standard or higher.default: false
limitinteger
Maximum incidents to return. Guest and Free maximum is 5. Standard and above maximum is 50.
statusstring
Lifecycle bucket: ongoing (active impact), monitoring (watching or fix-pending), resolved (closed). investigating is an alias for ongoing. resolved requires Standard or higher.one of ongoing · monitoring · resolved · investigating
timePeriodstring
History window such as 7d, 30d, 90d, or all when allowed by plan. Requires Standard or higher.
vendor*string
Vendor ID, for example zscaler, cloudflare, github, openai.
get_all_vendor_incidentsRead-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 calle...4 params

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 calle...

Parameters* required
includeResolvedboolean
Include resolved incidents in the fetch. Requires Standard or higher.default: false
limitinteger
Maximum incidents to return. Guest and Free maximum is 5. Standard and above maximum is 50.
statusstring
Lifecycle bucket: ongoing (active impact), monitoring (watching or fix-pending), resolved (closed). investigating is an alias for ongoing. resolved requires Standard or higher.one of ongoing · monitoring · resolved · investigating
timePeriodstring
History window such as 7d, 30d, 90d, or all when allowed by plan. Requires Standard or higher.
get_pricingPublic 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...

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...

No parameters. Call it with no arguments.

Sponsors

Promote your product hereReach 125k+ visitors monthlyPromote your product hereReach 125k+ visitors monthlyAgent CaffeineSponsoredClose your lid, come back to finished workSnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthlyWaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthlyknobsSponsoredSee your site on any phone, any day, in any language

Details

Website
www.huntertech.io/vendor-mcp
Transport
HTTP, SSE
Registry
MCP registry, active
Tools verified
Nov 6, 2026