MCP Health Monitor

io.github.oaslanankaPublished by GitHub account oaslanankav1.0.2Updated Oct 24, 2026

Monitor MCP server health, uptime, response times, and Azure DevOps pipeline status

VerifiedSTDIODesktop onlySecurity & Monitoring

Server details

Identifier: io.github.oaslananka/mcp-health-monitor
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account oaslananka for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.oaslananka%2Fmcp-health-monitor.svg)](https://sourceweft.com/mcp/io.github.oaslananka%2Fmcp-health-monitor?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP server that lets an assistant monitor MCP server health, uptime, response times, and Azure DevOps pipeline status.

What you can do: Check the health, uptime and response times of monitored MCP servers and review the results over time. Look up Azure DevOps pipeline status alongside server health. Optionally run background scheduled checks and keep results in a local SQLite database.
When to use it: Useful when you run several MCP servers and want an assistant to report on their availability and latency, or to correlate that with Azure DevOps pipeline status in one place.
Requirements: Runs as a local stdio process installed from the npm package, so Node.js is needed. No authentication is declared. Optional environment variables: HEALTH_MONITOR_AUTO_CHECK set to 1 enables background scheduled checks, and HEALTH_MONITOR_DB sets a custom SQLite database path.

Before you install

Background scheduled checks are off unless HEALTH_MONITOR_AUTO_CHECK is set to 1; enabling them makes the server poll monitored endpoints on its own. Health data is stored in a local SQLite file whose location can be changed with HEALTH_MONITOR_DB. Azure DevOps access details are not described in the available information.

Installation

In SourceWeft

Open MCP Health Monitor in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.0.2LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.