Huntertech.io Vendor Insights MCP Server
io.huntertech/vendor-insights
answering
Huntertech.io Vendor Insights is answering right now. Last checked 8 min ago. It exposes 3 tools.
AI-ready vendor incident status with public active incidents and plan-scoped history.
Uptime history
43 hours of history · worst hour 50%
43 hours agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
428 ms
Response time
average over 24h
open, no key
Access
streamable-http
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.
run in your terminal
claude mcp add vendor-insights --transport http https://www.huntertech.io/api/v1/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"vendor-insights": {
"url": "https://www.huntertech.io/api/v1/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.vendor-insights]
url = "https://www.huntertech.io/api/v1/mcp".cursor/mcp.json
{
"mcpServers": {
"vendor-insights": {
"url": "https://www.huntertech.io/api/v1/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"vendor-insights": {
"url": "https://www.huntertech.io/api/v1/mcp"
}
}
}Available tools 3
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
all
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.
monitored
list_monitored_vendors
List monitored SaaS and infrastructure vendors with public incident status data, including SolarWinds, Zscaler, Cloudflare, and others.
vendor
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 resolved history within the user plan window.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://www.huntertech.io/api/v1/mcp | streamable-http | answering | 433 ms | 8 min ago |
Huntertech.io Vendor Insights — questions
Answers built from our own checks of this server.
What can Huntertech.io Vendor Insights do?
It exposes 3 tools, read directly from the server on our last check. Among them: get_all_vendor_incidents, get_vendor_incidents, list_monitored_vendors. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is Huntertech.io Vendor Insights working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 428 ms. The bar chart above shows every period we have measured.
How do I connect Huntertech.io Vendor Insights?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Huntertech.io Vendor Insights need an API key?
No. Huntertech.io Vendor Insights completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Huntertech.io Vendor Insights?
It answers our handshake in 428 ms on average, which is faster than 30% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.