The MCP Fleet page is your single view of every Model Context Protocol (MCP) server known to your HostAtlas organisation — the ones you registered by hand, the ones auto-detected on your servers by the HostAtlas agent, and the ones bridged in through the MCP Tailnet Manager on operator laptops.

Open it at /mcp or via Compliance → MCP Fleet.

What you see

Four counters at the top: total MCP servers, up, degraded, down, and how many were auto-detected (versus manually registered).

Below the counters, a table of every MCP server with:

• Name — display name (link to the detail page).
• Server — the HostAtlas server it runs on, if any.
• Transport — stdio, SSE, HTTP or streamable-HTTP.
• Auth — none, bearer, API key, or OAuth.
• Tools — how many MCP tools this server exposes.
• Status — up / degraded / down badge.
• Last check — how long since the last successful health probe.

Rows are sorted so the “up” servers appear first, then by name.

If the list is empty, the empty state points you at two ways to populate it: registering one manually, or updating the HostAtlas agent to a version that auto-detects MCP servers running on the host.

What you can do

• Register an MCP server — the Add MCP Server button opens a modal to enter a name, endpoint URL, transport, auth type, optional credentials, description, and whether the server should be listed in the internal MCP Registry.
• Open the detail page — click a server name to see its full tool list, health-check history (up to the last 100 probes) and metadata.
• Check now — from the detail page, trigger a fresh health probe on demand.
• Delete a server — remove a manually registered entry from the fleet.

How it works

Every registered MCP server is probed by HostAtlas on a schedule. Each probe records reachability, response time and any tool-list changes; the last 100 probes are kept per server for the sparkline on the detail page.

Auto-detected servers show up when the HostAtlas agent recognises an MCP process on the host and reports it in. Those entries are still probed like manual ones, so you get uniform status regardless of origin.

The MCP Tailnet Manager desktop app opens a local MCP bridge to servers over SSH so tools like Claude Code and Cursor can talk to them with no cloud roundtrip. Servers exposed through the tailnet manager can also be registered here so the fleet view reflects everything an operator can reach.

Transports and auth

Transport	Typical use
stdio	Local processes launched by an editor (Claude Desktop, Cursor, Windsurf).
SSE	Long-lived server-sent-events streams.
HTTP	Plain request/response MCP endpoints.
streamable-HTTP	Streaming responses over HTTP.

Auth options: none, bearer token, API key, or OAuth. Credentials are encrypted at rest.

Related

• MCP Registry — the shareable catalog of servers your team can plug into their editors.
• MCP Server tool — the standalone HostAtlas MCP bridge for CLI-style access.
• MCP Tailnet Manager tool — desktop app that opens local MCP bridges to your servers over SSH.