Healthie.NET.Mcp
4.1.2
Prefix Reserved
See the version list below for details.
dotnet add package Healthie.NET.Mcp --version 4.1.2
NuGet\Install-Package Healthie.NET.Mcp -Version 4.1.2
<PackageReference Include="Healthie.NET.Mcp" Version="4.1.2" />
<PackageVersion Include="Healthie.NET.Mcp" Version="4.1.2" />
<PackageReference Include="Healthie.NET.Mcp" />
paket add Healthie.NET.Mcp --version 4.1.2
#r "nuget: Healthie.NET.Mcp, 4.1.2"
#:package Healthie.NET.Mcp@4.1.2
#addin nuget:?package=Healthie.NET.Mcp&version=4.1.2
#tool nuget:?package=Healthie.NET.Mcp&version=4.1.2
Healthie.NET.Mcp
▶ Live demo — board.healthie-dotnet.dev — a read-only Healthie.NET dashboard watching real status pages (Anthropic, OpenAI, GitHub, Cloudflare, and more), built from these packages. Full documentation at healthie-dotnet.dev.
A Model Context Protocol server for Healthie.NET, so an AI agent such as Claude, Copilot, or Cursor can read your service health and act on it in plain language. Read-only until you say otherwise.
Installation
dotnet add package Healthie.NET.Mcp
Usage
using Healthie.Mcp;
builder.Services.AddHealthie(typeof(Program).Assembly);
builder.Services.AddHealthieMcp();
var app = builder.Build();
app.MapHealthieMcp(); // /healthie/mcp
app.Run();
Point an MCP client at http://localhost:5000/healthie/mcp and ask it what is unhealthy.
Tools
| Tool | Kind | Description |
|---|---|---|
get_health_states |
read | The current health of every monitored component. |
get_unhealthy_checkers |
read | Only the components that are unhealthy or suspicious. |
get_checker |
read | One component's health and configuration. |
get_check_history |
read | A component's recent run history, newest first, paged. |
run_check |
action | Runs a check now and returns the fresh result. |
reset_checker |
action | Clears a component's failure streak. |
Mutations Are Opt-In
The server exposes only the read tools by default. The two action tools appear when you ask for them, and anything that can reach the endpoint can then trigger checks -- so require authorization when you do:
builder.Services.AddHealthieMcp(options => options.AllowMutations = true);
app.MapHealthieMcp().RequireAuthorization();
Options
| Option | Type | Default | Description |
|---|---|---|---|
AllowMutations |
bool |
false |
Whether run_check and reset_checker are exposed. |
MaxHistoryPageSize |
int |
50 |
Caps how many history entries one get_check_history call returns. |
Transport
Served over Streamable HTTP, statelessly, so it scales out like any other endpoint in your app. The MCP C# SDK also supports a stdio host if you want an agent to run the server locally.
See Also
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Healthie.NET.Abstractions (>= 4.1.2)
- Microsoft.Extensions.AI.Abstractions (>= 10.8.3)
- ModelContextProtocol (>= 2.2.0)
- ModelContextProtocol.AspNetCore (>= 2.2.0)
-
net8.0
- Healthie.NET.Abstractions (>= 4.1.2)
- Microsoft.Extensions.AI.Abstractions (>= 10.8.3)
- ModelContextProtocol (>= 2.2.0)
- ModelContextProtocol.AspNetCore (>= 2.2.0)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
### Fixed
- The dashboard event-log and about dialogs now move focus inside, keep keyboard focus contained,
close with Escape, and restore focus to the control that opened them.
- Dashboard checker rows now expose selection as a real button alongside their action buttons,
removing nested interactive controls while preserving whole-row pointer selection.
- A dashboard state-provider failure now shows a recoverable unavailable state with a retry action
instead of looking like an empty installation with no registered checkers.
- The Blazor sample now keeps the dashboard stylesheet in its static host head, preventing an
unstyled flash while the interactive head reconnects on a slow network.
- HTTP checker display names and result messages now omit URI user information, query strings, and
fragments, server-controlled reason phrases, and transport exception details, preventing embedded
credentials and tokens from reaching stored history, alerts, logs, or the dashboard while requests
still use the complete configured URI.
- Alert-history persistence now loads durable history before its first post-restart write and
coalesces changes raised during a slow state-provider write into one latest-state follow-up. This
preserves earlier alerts without duplicating the new one and avoids an unbounded queue of tasks
and redundant full-history writes during alert bursts.
- The Web API sample maps its unauthenticated management API and mutation-enabled MCP endpoint only
in Development, so deploying the sample with a production environment no longer exposes those
local demonstration surfaces. Liveness and readiness probes remain available.
- History clearing and startup trimming now use optimistic concurrency, so they no longer overwrite
a check result or setting changed by another replica between the read and write.
- Leader election now serializes schedule changes with leadership transitions and reconciles every
registered checker's persisted active state and schedule through a bulk read on lease renewal. A
pause or cadence change made through another replica now reaches the leader, a fresh leader
removes inactive durable jobs left by the previous process, and reconciliation runs with bounded
concurrency while an independent lease heartbeat prevents slow scheduler calls from expiring an
otherwise healthy leader. Partial and cancelled transitions remain tracked until cleanup succeeds,
and shutdown does not release the lease over work it could not stop.
- CosmosDB multi-state reads now use `ReadManyItemsAsync`, avoiding one sequential network round
trip per checker during dashboard loads and leader renewal.
- The in-memory lease provider now returns exactly one winner when replicas contend concurrently.
- Coravel, Hangfire, Temporal, and the leader-election decorator now validate schedules before they
are persisted. Cronos expressions requiring an absent jitter seed are reported as validation
failures instead of escaping as server errors. The built-in timer also rejects periods outside
`PeriodicTimer`'s supported range before replacing a working schedule.
- Temporal now preserves Healthie.NET's six-field, leading-seconds cron meaning by translating it
to Temporal's seven-field seconds form. It rejects Cronos-only relative-day and descending-range
expressions whose Temporal meaning differs, and fixed periods outside Temporal's supported range,
before an existing schedule is removed.
- Uptime recording now starts a new observation segment on the first fresh result after a process
restart, even when its health matches persisted state. Time while no process was observing the
checker remains unknown, and a transition that finds the bounded queue full is retried by the next
fresh result.
Full changelog: https://github.com/ivanvyd/Healthie.NET/blob/v4.1.2/CHANGELOG.md