The new preview card highlights the vendor favicon, logo-derived color palette, website, a concise vendor description, and the available capabilities for that vendor. The active route is emphasized in the badge row, so overview, incidents, maintenance, advisories, updates, press releases, and compliance links can each feel specific in previews.

This gives us a reusable standard for future page previews. Instead of creating static images by hand, the card is rendered from structured vendor data, cached, and served through the same preview pipeline used by the Updates page.

Highlights

• Share vendor overview, incident, maintenance, advisory, update, and compliance pages with preview cards tailored to that vendor.
• Give iMessage, X, Slack, and other social platforms clearer visual context when someone shares a Huntertech.io vendor link.
• Generate cards dynamically instead of maintaining separate static image files for every vendor and section.

Each update now has its own canonical URL, making launches easier to share, index, and reference over time. The archive still brings everything together in one place, while individual update pages give search engines and readers a cleaner destination for a specific announcement.

Updates also ship with feed support for teams that prefer to subscribe outside the site. JSON Feed, RSS, and Atom are generated from the same structured update data, so feed readers, automation workflows, and internal notification systems can track product changes without manual scraping.

Highlights

• Follow product launches and platform changes from one dedicated archive.
• Subscribe through JSON Feed, RSS, or Atom depending on the tools your team already uses.
• Share canonical URLs for individual updates instead of relying on page anchors.

The pulse chart groups reports into 15-minute intervals across a 24-hour window. That makes early spikes easier to see without waiting for an official vendor update. Vendor-level reports show the broad health signal, while incident-level reports provide local confirmation on specific incident cards.

Community reports are intentionally labeled as unofficial. They do not replace vendor status pages, but they add practical context during the early minutes of an outage when teams are trying to answer whether a problem is isolated or widespread.

Highlights

• Spot early outage patterns before every vendor status page has caught up.
• Compare broad vendor-level signal with incident-specific confirmation in one view.
• Add real-world symptoms and affected areas so other teams can triage faster.

The homepage now includes an Add to Cursor button for Vendor Insights, plus a copy-config fallback for teams that prefer to add the MCP server manually.

MCP gives connected assistants a cleaner path to the same operational context teams already use: vendor incidents, maintenance windows, advisories, product updates, and related signals. Instead of treating those details as static pages, teams can bring them into workflows where investigation, summarization, and follow-up work already happen.

This is an important foundation for the platform. As more teams use AI tools for incident response and vendor monitoring, structured context matters. MCP support fits into that workflow without turning vendor intelligence into another place people need to manually check and copy from.

Highlights

• Install the Vendor Insights MCP server directly from the homepage with the new Add to Cursor button.
• Bring vendor intelligence into AI workflows without manually copying status details between tools.
• Give assistants clearer context around incidents, advisories, maintenance, and product updates.

The update is most visible on vendor overview pages, tools, incident views, and announcement surfaces. Cards now share a more consistent frame, controls feel more deliberate, and dense operational content has more room to breathe.

The goal is simple: make high-volume vendor intelligence easier to scan. Teams should be able to move from signal to context quickly without each page feeling like a separate product.

Highlights

• Scan dense vendor and tool pages faster with clearer hierarchy and calmer surfaces.
• Move between overview, incident, and tool pages with more consistent navigation patterns.
• Read metrics, cards, and controls with less visual noise across light and dark themes.

We also improved what happens after sign-in. When someone starts from a specific page or workflow and needs to authenticate, the app can remember the intended destination and send them back after login completes.

This is especially important for OAuth sign-in, where intermediate redirects can strip query parameters. The improved flow preserves the intended destination across the handoff and clears it once sign-in completes.

Highlights

• Make the login page easier to scan with cleaner social, email, and account navigation options.
• Keep users anchored to the page or workflow they started from before sign-in.
• Support OAuth flows that can otherwise lose return destinations during handoff.