# mulewatch (npm · mulewatch)

Read-only MCP server for MuleSoft Anypoint: app logs, archive search, Runtime Manager, Exchange.

- Trust score: 77/100 (medium)
- Change this week: +14
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- npm · `mulewatch`: 77/100 (this document), [markdown](https://verifymcp.io/servers/brbousnguar-mulewatch/mulewatch.md), [page](https://verifymcp.io/servers/brbousnguar-mulewatch/mulewatch)

## Channel facts

- Registry: `npm`
- Package: `mulewatch`
- Version: `0.1.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-09-25.

- **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.
  - 31 of 95 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1650 tokens (~183/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 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 mulewatch MCP server?

mulewatch runs locally as an npm package, launched with npx -y mulewatch. 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 brbousnguar-mulewatch -- npx -y mulewatch
```

### Cursor

```json
{
  "mcpServers": {
    "brbousnguar-mulewatch": {
      "command": "npx",
      "args": [
        "-y",
        "mulewatch"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "brbousnguar-mulewatch": {
      "command": "npx",
      "args": [
        "-y",
        "mulewatch"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add brbousnguar-mulewatch -- npx -y mulewatch
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "brbousnguar-mulewatch": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mulewatch"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add brbousnguar-mulewatch --command npx --arg -y --arg mulewatch
```

### Hermes

```yaml
mcp_servers:
  brbousnguar-mulewatch:
    command: "npx"
    args: ["-y", "mulewatch"]
```

### Netclaw

```json
{
  "McpServers": {
    "brbousnguar-mulewatch": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mulewatch"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add brbousnguar-mulewatch -t stdio -c npx -a -y mulewatch
```

### Other

```json
{
  "mcpServers": {
    "brbousnguar-mulewatch": {
      "command": "npx",
      "args": [
        "-y",
        "mulewatch"
      ]
    }
  }
}
```

## 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-09-25 (score 77, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (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-09-21 (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-09-19 (score 74, +11)

- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.85

### 2026-09-18 (score 63, −10)

- [security regression] Known CVEs: pass → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.30 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Dependency health: 0.85 → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.1.1 → 0.1.2

### 2026-09-17 (score 73, +1)

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

### 2026-09-15 (score 72, +3)

- [functional improvement] Stability: unverified → 0.23

### 2026-09-09 (score 69, +15)

- [security improvement] Malware scan: unverified → pass

## MCP tools (9)

### `anypoint_whoami` (~43 tokens)

Check Anypoint connection

Verify the configured Anypoint credentials and show which business group, host and environment allowlist this server is operating with. Use this first when a call fails.

### `anypoint_list_business_groups` (~70 tokens)

List business groups

List the business groups under the credentials' organization, with their ids. Environments live on business groups, not on the root organization — call this first if anypoint_list_environments returns nothing.

Input parameters:

- `rootOrgId` (string): Root organization id. Defaults to the credentials' own organization.

### `anypoint_list_environments` (~87 tokens)

List environments

List the Anypoint environments in a business group. If this returns nothing, the orgId is probably the root organization — call anypoint_list_business_groups to find the right id. Restricted to ANYPOINT_ALLOWED_ENVIRONMENTS when that is set.

Input parameters:

- `orgId` (string): Business group id. Defaults to ANYPOINT_ORG_ID, or the credentials' own organization.

### `anypoint_list_deployed_apps` (~185 tokens)

List deployed applications

List deployed Mule applications in an environment, across Application Manager (CloudHub 2.0 / Runtime Fabric), legacy CloudHub, and hybrid on-prem targets.

Input parameters:

- `environmentId` (string): Environment id. Use instead of environmentName.
- `environmentName` (string): Environment name, e.g. 'Production'. Resolved to an id, must match exactly one.
- `includeErrors` (boolean): Include per-target errors when a target endpoint is unavailable or not permitted.
- `includeRaw` (boolean): Include the raw Anypoint API objects alongside the normalized fields.
- `limit` (integer): Maximum records to return, default 100.
- `orgId` (string): Business group id. Defaults to ANYPOINT_ORG_ID, or the credentials' own organization.
- `target` (string): Deployment target to query. Defaults to application_manager.

### `anypoint_list_app_logs` (~304 tokens)

List application logs

List the latest Runtime Manager logs for a Mule application. This reads the live tail only — a small rolling buffer. For anything older than the buffer, use anypoint_search_archived_logs.

Input parameters:

- `appName` (string, required): Deployment/application name as shown in Runtime Manager.
- `deploymentId` (string): Use when the app name is ambiguous or already known.
- `descending` (boolean): Return latest first, default true.
- `endTime` (string): Application Manager time filter, ISO 8601.
- `environmentId` (string): Environment id. Use instead of environmentName.
- `environmentName` (string): Environment name, e.g. 'Production'. Resolved to an id, must match exactly one.
- `includeErrors` (boolean): Include failed target errors when target is auto.
- `includeRaw` (boolean): Include the raw Anypoint API objects alongside the normalized fields.
- `limit` (integer): Maximum log entries, default 100, max 500.
- `offset` (integer): Application Manager log offset, default 0.
- `orgId` (string): Business group id. Defaults to ANYPOINT_ORG_ID, or the credentials' own organization.
- `specId` (string): Specific Application Manager deployment spec/config id.
- `startTime` (string): Application Manager time filter, ISO 8601.
- `target` (string): Log source. Defaults to auto, which tries Application Manager then CloudHub.

### `anypoint_get_app_logs_for_analysis` (~347 tokens)

Analyze application logs

Fetch live-tail logs for a Mule application and return an analysis-ready payload: normalized lines plus counts by priority, logger and instance. Prefer this over anypoint_list_app_logs when diagnosing a problem.

Input parameters:

- `appName` (string, required): Deployment/application name as shown in Runtime Manager.
- `deploymentId` (string): Use when the app name is ambiguous or already known.
- `descending` (boolean): Return latest first, default true.
- `endTime` (string): Application Manager time filter, ISO 8601.
- `environmentId` (string): Environment id. Use instead of environmentName.
- `environmentName` (string): Environment name, e.g. 'Production'. Resolved to an id, must match exactly one.
- `errorOnly` (boolean): Only return ERROR and FATAL lines.
- `includeErrors` (boolean): Include failed target errors when target is auto.
- `includeRaw` (boolean): Include the raw Anypoint API objects alongside the normalized fields.
- `limit` (integer): Maximum log entries, default 100, max 500.
- `offset` (integer): Application Manager log offset, default 0.
- `orgId` (string): Business group id. Defaults to ANYPOINT_ORG_ID, or the credentials' own organization.
- `searchTerms` (array): Case-insensitive filters matched against timestamp, priority, message, logger, thread or instance.
- `specId` (string): Specific Application Manager deployment spec/config id.
- `startTime` (string): Application Manager time filter, ISO 8601.
- `target` (string): Log source. Defaults to auto, which tries Application Manager then CloudHub.

### `anypoint_search_archived_logs` (~291 tokens)

Search archived logs

Search historical Mule application logs via the Anypoint Monitoring Archive API, for dates beyond the live tail's rolling buffer. Requires Anypoint Monitoring to be enabled for the organization. Use this for any past-date incident investigation.

Input parameters:

- `appName` (string, required): Deployment name, must match the Runtime Manager name exactly.
- `date` (string, required): Required date to search, YYYY-MM-DD (UTC).
- `endDate` (string): Inclusive range end, YYYY-MM-DD (UTC). Max 7 days total.
- `environmentId` (string): Environment id. Use instead of environmentName.
- `environmentName` (string): Environment name, e.g. 'Production'. Resolved to an id, must match exactly one.
- `errorOnly` (boolean): Only return ERROR and FATAL lines.
- `includeRaw` (boolean): Include the raw Anypoint API objects alongside the normalized fields.
- `limit` (integer): Cap on matched lines returned, default 500.
- `maxEntities` (integer): Cap on replica entities probed during a full-scan fallback, default 150.
- `maxFiles` (integer): Cap on archive files downloaded and parsed, default 100.
- `orgId` (string): Business group id. Defaults to ANYPOINT_ORG_ID, or the credentials' own organization.
- `searchTerms` (array): Case-insensitive text filters.

### `anypoint_list_api_manager_instances` (~181 tokens)

List API Manager instances

List API instances managed by Anypoint API Manager in an environment, with their assets, endpoints and technology.

Input parameters:

- `assetId` (string): Filter by Exchange asset id.
- `environmentId` (string): Environment id. Use instead of environmentName.
- `environmentName` (string): Environment name, e.g. 'Production'. Resolved to an id, must match exactly one.
- `includeRaw` (boolean): Include the raw Anypoint API objects alongside the normalized fields.
- `limit` (integer): Maximum records, default 100.
- `offset` (integer): Pagination offset, default 0.
- `orgId` (string): Business group id. Defaults to ANYPOINT_ORG_ID, or the credentials' own organization.
- `technology` (string): Filter by technology, e.g. mule4, flexGateway.

### `anypoint_search_exchange_assets` (~142 tokens)

Search Exchange assets

Search Anypoint Exchange for assets in the organization — APIs, connectors, templates, examples and fragments.

Input parameters:

- `includeRaw` (boolean): Include the raw Anypoint API objects alongside the normalized fields.
- `limit` (integer): Maximum records, default 50.
- `offset` (integer): Pagination offset, default 0.
- `orgId` (string): Business group id. Defaults to ANYPOINT_ORG_ID, or the credentials' own organization.
- `search` (string): Free-text search over asset names and descriptions.
- `types` (array): Filter by asset type, e.g. rest-api, connector, template, example.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/brbousnguar-mulewatch/mulewatch#diagnostics

## Score history

- 2026-09-25: 77
- 2026-09-24: 76
- 2026-09-23: 76
- 2026-09-22: 75
- 2026-09-21: 75
- 2026-09-20: 74
- 2026-09-19: 74
- 2026-09-18: 63
- 2026-09-17: 73
- 2026-09-16: 72
- 2026-09-15: 72
- 2026-09-14: 69
- 2026-09-13: 69
- 2026-09-12: 69
- 2026-09-11: 69
- 2026-09-10: 69
- 2026-09-09: 69
- 2026-09-08: 54

## Common questions

### What is the mulewatch MCP server?

mulewatch is an MCP server listed in the public MCP registry as io.github.brbousnguar/mulewatch. Read-only MCP server for MuleSoft Anypoint: app logs, archive search, Runtime Manager, Exchange. This page covers its npm package (mulewatch).

### Is the mulewatch MCP server safe to use?

mulewatch scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 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 mulewatch MCP server expose?

mulewatch exposes 9 tools: anypoint_whoami, anypoint_list_business_groups, anypoint_list_environments, anypoint_list_deployed_apps, anypoint_list_app_logs, and 4 more. Their descriptions and schemas cost roughly 1,650 tokens of context every time the server is loaded.

### Is the mulewatch MCP server still maintained?

mulewatch is still listed as active in the MCP registry. We last reached this channel on 25 September 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 mulewatch MCP server under?

mulewatch declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/mulewatch
- Socket report: https://socket.dev/npm/package/mulewatch
- Repository: https://github.com/brbousnguar/mulewatch
- Website: https://heybrahim.com/
- Changelog RSS feed: https://verifymcp.io/servers/brbousnguar-mulewatch/mulewatch.xml
- Changelog JSON feed: https://verifymcp.io/servers/brbousnguar-mulewatch/mulewatch.json
- HTML version of this page: https://verifymcp.io/servers/brbousnguar-mulewatch/mulewatch