mcpField
M
mcp-server-change-health-monitor

mcp-server-change-health-monitor

Local
github.com/mambalabsdevDeveloper Tools0Updated 2d ago

About mcp-server-change-health-monitor

An MCP server that checks MCP endpoints, npm packages, or official registry search results and reports availability, response speed, and changes. It is intended for operators tracking server health and tool updates, with changes classified by severity.

Key features

  1. 01Check MCP server availability
  2. 02Measure response speed
  3. 03List exposed tools, resources, and prompts
  4. 04Compare changes with saved snapshots
  5. 05Classify changes by severity

Use cases

  1. 01Check a list of servers for uptime
  2. 02Track tool description changes
  3. 03Review registry matches for availability

MCP support

Exposes the `check_mcp_servers` tool to MCP clients. It checks targets using the MCP protocol and returns current capabilities and changes since a prior snapshot.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"com-mambabuilt-mcp-server-change-health-monitor": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-server-change-health-monitor"
],
"env": {
"APIFY_TOKEN": "<APIFY_TOKEN>"
}
}
}
}
Run commandnpx -y @mambalabsdev/mcp-server-change-health-monitor
Environment variables to set
APIFY_TOKENSecretApify API token from https://console.apify.com/account/integrations

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@mambalabsdev/mcp-server-change-health-monitor1.0.2

Tools

1

Saved tool list · updated 2d ago

ParameterTypeRequiredDescription
max_serversnumberNoMost servers to check per registry search term, up to 200. Default 25.
server_urlsarrayNoHTTP endpoints of MCP servers. Streamable HTTP is tried first, then the older HTTP plus SSE transport.
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.
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.
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.
max_charge_usdstringNoOptional. The run stops before a charge that would pass this amount. Free rows are always returned.
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.
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.
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.
include_resources_promptsbooleanNoAlso list the server's resources and prompts and report what changed in them. Default true.

Details

From the project README

MCP Server Change and Health Monitor MCP Server

Glama score MCP Registry npm version npm downloads license mcpservers.org

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:

{
  "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:

{
  "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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.