# com.mambabuilt/mcp-server-change-health-monitor (npm · @mambalabsdev/mcp-server-change-health-monitor)

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

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@mambalabsdev/mcp-server-change-health-monitor`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-mambabuilt-mcp-server-change-health-monitor/mambalabsdev-mcp-server-change-health-monitor.md), [page](https://verifymcp.io/servers/com-mambabuilt-mcp-server-change-health-monitor/mambalabsdev-mcp-server-change-health-monitor)

## Channel facts

- Registry: `npm`
- Package: `@mambalabsdev/mcp-server-change-health-monitor`
- Version: `1.0.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 10 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 467 tokens (~467/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the com.mambabuilt/mcp-server-change-health-monitor server?

com.mambabuilt/mcp-server-change-health-monitor runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-server-change-health-monitor. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add com-mambabuilt-mcp-server-change-health-monitor -- npx -y @mambalabsdev/mcp-server-change-health-monitor
```

### Cursor

```json
{
  "mcpServers": {
    "com-mambabuilt-mcp-server-change-health-monitor": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-server-change-health-monitor"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-mambabuilt-mcp-server-change-health-monitor": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-server-change-health-monitor"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-mambabuilt-mcp-server-change-health-monitor -- npx -y @mambalabsdev/mcp-server-change-health-monitor
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mambabuilt-mcp-server-change-health-monitor": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@mambalabsdev/mcp-server-change-health-monitor"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-mambabuilt-mcp-server-change-health-monitor --command npx --arg -y --arg @mambalabsdev/mcp-server-change-health-monitor
```

### Hermes

```yaml
mcp_servers:
  com-mambabuilt-mcp-server-change-health-monitor:
    command: "npx"
    args: ["-y", "@mambalabsdev/mcp-server-change-health-monitor"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-mambabuilt-mcp-server-change-health-monitor": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@mambalabsdev/mcp-server-change-health-monitor"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-mambabuilt-mcp-server-change-health-monitor -t stdio -c npx -a -y @mambalabsdev/mcp-server-change-health-monitor
```

### Other

```json
{
  "mcpServers": {
    "com-mambabuilt-mcp-server-change-health-monitor": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-server-change-health-monitor"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 71, 0)

- [functional] Package version: 1.0.1 → 1.0.2

### 2026-11-10 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-09 (score 70, +1)

- [security regression] Tool safety: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.10
- [functional] First check of Schema quality: unverified
- [functional] Package version: 1.0.0 → 1.0.1

## MCP tools (1)

### `check_mcp_servers` (~467 tokens)

Check MCP servers for changes and health

Check MCP servers by URL, npm package, or official registry search. Returns one row per server: whether it answered, how fast, the tools it exposes now, and what changed since the last run, with breaking changes marked. Runs on Apify, pay per event.

Input parameters:

- `auth_headers` (string): Optional, 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,…
- `include_resources_prompts` (boolean): Also list the server's resources and prompts and report what changed in them. Default true.
- `max_charge_usd` (string): Optional. The run stops before a charge that would pass this amount. Free rows are always returned.
- `max_servers` (number): Most servers to check per registry search term, up to 200. Default 25.
- `npm_packages` (array): npm 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…
- `previous_snapshot` (string): Optional. 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.
- `registry_search` (array): Search 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.
- `server_urls` (array): HTTP endpoints of MCP servers. Streamable HTTP is tried first, then the older HTTP plus SSE transport.
- `snapshot_key` (string): Name 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.
- `timeout_seconds` (number): How 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.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-mambabuilt-mcp-server-change-health-monitor/mambalabsdev-mcp-server-change-health-monitor#diagnostics

## Score history

- 2026-11-21: 76
- 2026-11-20: 75
- 2026-11-19: 75
- 2026-11-18: 74
- 2026-11-17: 74
- 2026-11-16: 74
- 2026-11-15: 73
- 2026-11-14: 73
- 2026-11-13: 72
- 2026-11-12: 72
- 2026-11-11: 71
- 2026-11-10: 71
- 2026-11-09: 70
- 2026-11-08: 69
- 2026-11-07: 69
- 2026-11-06: 54

## Common questions

### What is the com.mambabuilt/mcp-server-change-health-monitor server?

com.mambabuilt/mcp-server-change-health-monitor is listed in the public MCP registry as com.mambabuilt/mcp-server-change-health-monitor. Checks MCP servers for uptime and tool changes since the last run, breaking changes marked. This page covers its npm package (@mambalabsdev/mcp-server-change-health-monitor).

### Is the com.mambabuilt/mcp-server-change-health-monitor server safe to use?

com.mambabuilt/mcp-server-change-health-monitor scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the com.mambabuilt/mcp-server-change-health-monitor server expose?

com.mambabuilt/mcp-server-change-health-monitor exposes 1 tool: check_mcp_servers. Their descriptions and schemas cost roughly 467 tokens of context every time the server is loaded.

### Is the com.mambabuilt/mcp-server-change-health-monitor server still maintained?

com.mambabuilt/mcp-server-change-health-monitor is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the com.mambabuilt/mcp-server-change-health-monitor server under?

com.mambabuilt/mcp-server-change-health-monitor declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the com.mambabuilt/mcp-server-change-health-monitor server?

VerifyMCP ran 16 checks on com.mambabuilt/mcp-server-change-health-monitor, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@mambalabsdev/mcp-server-change-health-monitor
- Socket report: https://socket.dev/npm/package/@mambalabsdev/mcp-server-change-health-monitor
- Repository: https://github.com/mambalabsdev/mcp-server-change-health-monitor
- Changelog RSS feed: https://verifymcp.io/servers/com-mambabuilt-mcp-server-change-health-monitor/mambalabsdev-mcp-server-change-health-monitor.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-mambabuilt-mcp-server-change-health-monitor/mambalabsdev-mcp-server-change-health-monitor/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-mambabuilt-mcp-server-change-health-monitor/mambalabsdev-mcp-server-change-health-monitor.json
- HTML version of this page: https://verifymcp.io/servers/com-mambabuilt-mcp-server-change-health-monitor/mambalabsdev-mcp-server-change-health-monitor
