---
title: Hosts everywhere: status pages, reports, search, API, MCP and A2A
description: Servers running the agent were only visible on the Hosts pages. Now a host can sit on a status-page component (pick it under Hosts in the component editor; it…
canonical: https://watchfor.io/changelog/2026-09-22-hosts-everywhere
---

[All updates](/changelog/page/2#2026-09-22-hosts-everywhere) ✨ New Sep 22, 2026 · v 8.1.6

# Hosts everywhere: status pages, reports, search, API, MCP and A2A

Servers running the agent were only visible on the Hosts pages. Now a host can sit on a status-page component (pick it under Hosts in the component editor; it shows online or down from its own alerts), reports carry a Hosts section with uptime, incidents and average CPU, memory and disk per server, and ⌘K finds hosts by name, address or tag. For agents and integrations there is GET /v1/hosts with liveness, current gauges and metric time series, the list_hosts, get_host and get_host_metrics MCP tools, the check-hosts A2A skill, and hosts in the TypeScript, Python and Ruby SDKs.

Press ⌘K or Ctrl K and type a host's name.

Reports get a Hosts section with each server's uptime, incidents and resource use.

Hosts sit next to your monitors when you build a status-page component.

## The problem

Servers running the agent lived on the Hosts pages and nowhere else. A status page couldn't include your database server, the weekly report left servers out, and ⌘K couldn't find one by name.

## Where hosts show up now

- Status pages. The component editor lists hosts under Hosts , next to your monitors. A host counts as down there when its own alerts open a confirmed incident, such as a silent agent.

- Reports. A Hosts section gives each server's uptime and incidents for the period, average CPU and memory, the fullest disk's peak, and whether the agent is online.

- Search. Press ⌘K (Ctrl K) and type a name, an address or a tag such as env=prod .

- API, MCP and A2A. GET /v1/hosts returns liveness, the current gauges and metric time series. MCP clients get list_hosts , get_host and get_host_metrics , A2A agents the check-hosts skill, and the TypeScript, Python and Ruby SDKs know hosts too.

## Example

Your public status page has a "Database" component. Add db-1 to it. If db-1's agent stops reporting at 03:12, the component shows the outage as soon as the incident is confirmed, and the next weekly report lists the incident in db-1's row, next to its CPU and memory averages.

See [Hosts elsewhere in WatchFor](/docs/hosts#hosts-elsewhere-in-watchfor) and the [Hosts API](/docs/api/hosts).

Share this update

---

Canonical page: https://watchfor.io/changelog/2026-09-22-hosts-everywhere · Site guide: https://watchfor.io/llms.txt