Mcp Server Change Health Monitor

com.mambabuiltPublished by mambabuilt.comv1.0.0Updated Nov 7, 2026

Checks MCP servers for uptime and tool changes since the last run, breaking changes marked

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Checks a list of MCP servers for uptime, exposed tools, and changes since the last run, flagging breaking changes.

What you can do
  • Check MCP servers by HTTP endpoint, npm package, or official MCP Registry search and get one row per server
  • Report whether each server answered, how fast, and which tools it exposes now
  • Compare against a saved snapshot or a supplied earlier snapshot and mark changes as breaking, warning, or info
  • Optionally include resources and prompts in the comparison
  • Cap the number of servers per registry search term and the per-request timeout
When to use it
Useful when you maintain or depend on several MCP servers and want to know whether they are still up and whether their tools, resources, or prompts changed since a previous check, for example before upgrading a client configuration.
Requirements
Runs locally via npx, so Node.js 18 or newer is needed. Requires an Apify account and an Apify API token set as APIFY_TOKEN; the tool is listed without a token but calls need one. All checking work runs on Apify, so network access is required.
Before you install
Calls are billed per event to your Apify account (per server check, per npm package check, and per run start); max_charge_usd can cap a run. npm packages you list are installed and executed inside the run, so list only packages you trust. auth_headers may carry credentials for the servers being checked; they are sent only to their own site and are not saved in snapshots.

Installation

In SourceWeft

  1. Open Mcp Server Change Health Monitor in the dashboard and add it to a workspace.
  2. 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

MCP Server Change and Health Monitor MCP Server

[npm version] [license]

An MCP server for the Mamba Labs MCP Server Change and Health Monitor actor on Apify. Check any list of MCP servers and get one row per server: did it answer, what it exposes, and what changed.

What's Inside

What it does

Give it MCP server URLs, npm packages, or a search of the official MCP Registry. It speaks the MCP protocol to each server and returns whether the server answered, how fast, the tools it exposes now, and what changed since the last run. Changes are marked breaking, warning, or info.

All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config (claude_desktop_config.json), Cursor, or any MCP client:

json
{  "mcpServers": {    "mamba-mcp-server-change-health-monitor": {      "command": "npx",      "args": [        "-y",        "@mambalabsdev/mcp-server-change-health-monitor"      ],      "env": {        "APIFY_TOKEN": "your-apify-token"      }    }  }}

Restart the client. The check_mcp_servers tool appears.

Prerequisites

Example prompts

  • "Are these three MCP servers up, and did any of their tools change since last week?"
  • "Check every server in the official MCP Registry that matches github and list which ones answer."
  • "Did the tool descriptions on this MCP server change since my last check?"

Tool

check_mcp_servers. One tool. Example arguments:

json
{  "server_urls": [    "https://mcp.deepwiki.com/mcp"  ]}

Inputs

Every buyer facing input of the actor. Omitted inputs take the actor's own defaults.

InputTypeRequiredDescription
server_urlsarraynoHTTP endpoints of MCP servers. Streamable HTTP is tried first, then the older HTTP plus SSE transport.
npm_packagesarraynonpm package names, optionally with a version, such as @modelcontextprotocol/server-everything. Each is installed and started inside your run. The code in a package you list runs in your run, so list only packages you trust. No environment variables are passed to it.
registry_searcharraynoSearch terms for the official MCP Registry. The HTTP endpoints of matching servers are checked. Packages found this way are listed but never run, because running code picked by a keyword is not safe.
max_serversnumbernoMost servers to check per registry search term, up to 200. Default 25.
snapshot_keystringnoName of the memory that holds the last run's results, so a scheduled run finds changes on its own. Use a different name per list. Default default.
previous_snapshotstringnoOptional. The JSON of a SNAPSHOT record from an earlier run, or an https link to that record. It takes the place of the saved snapshot for this run.
timeout_secondsnumbernoHow long one request to a server may take before it counts as no answer, 3 to 60. Default 20. A package gets 60 more seconds to install.
include_resources_promptsbooleannoAlso list the server's resources and prompts and report what changed in them. Default true.
auth_headersstringnoOptional, for servers you are allowed to check. JSON keyed by site, for example {"https://mcp.example.com":{"Authorization":"Bearer abc"}}. Each header goes only to its own site. Encrypted by Apify, never logged, never saved in a snapshot.
max_charge_usdstringnoOptional. The run stops before a charge that would pass this amount. Free rows are always returned.

Pricing

Pay per event on Apify, billed to your Apify account. Prices in USD.

EventFree planBronzeSilverGold
server-check, one MCP server checked$0.005$0.00475$0.0045$0.00425
package-check, one npm package installed and checked$0.02$0.019$0.018$0.017
apify-actor-start, per run start$0.002$0.002$0.002$0.002

Servers that need credentials or refused the request, invalid entries, registry rows, and refused input are free. Mamba Labs pays the platform costs of the run, Apify proxy traffic included.

Full actor documentation

apify.com/mambalabs/mcp-server-change-health-monitor

License

MIT. See LICENSE.

Source: README.md at commit 8f279fd

Tools

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

Version history

1
  1. v1.0.0LatestNov 7, 2026

Score

50% 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
  • License10 pts