Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

mulewatch

NPM · MULEWATCH · SCANNED SEP 25

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

Available components

+14 this week 77 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
  • Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

npm · mulewatch

# add to Claude Code
claude mcp add brbousnguar-mulewatch -- npx -y mulewatch
// .cursor/mcp.json
{
  "mcpServers": {
    "brbousnguar-mulewatch": {
      "command": "npx",
      "args": [
        "-y",
        "mulewatch"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "brbousnguar-mulewatch": {
      "command": "npx",
      "args": [
        "-y",
        "mulewatch"
      ]
    }
  }
}
# add to Codex CLI
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
    }
  }
}
# add to OpenClaw
openclaw mcp add brbousnguar-mulewatch --command npx --arg -y --arg mulewatch
# ~/.hermes/config.yaml
mcp_servers:
  brbousnguar-mulewatch:
    command: "npx"
    args: ["-y", "mulewatch"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "brbousnguar-mulewatch": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mulewatch"
      ]
    }
  }
}
# add to Vellum
assistant mcp add brbousnguar-mulewatch -t stdio -c npx -a -y mulewatch
// mcp.json
{
  "mcpServers": {
    "brbousnguar-mulewatch": {
      "command": "npx",
      "args": [
        "-y",
        "mulewatch"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 +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.

  • 21 Sept 26 +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.

  • 19 Sept 26 +11
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.85 ▲ functional
  • 18 Sept 26 −10
    • Known CVEs: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.30 → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Dependency health: 0.85 → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.1.1 → 0.1.2 functional
  • 17 Sept 26 +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.

  • 15 Sept 26 +3
    • Stability: unverified → 0.23 ▲ functional
  • 9 Sept 26 +15
    • Malware scan: unverified → pass ▲ security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 25 Sept 2026 · Analysed npm/mulewatch@0.1.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~1,650 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
anypoint_get_app_logs_for_analysis ~347

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.

NameTypeReqDescription
appNamestringyesDeployment/application name as shown in Runtime Manager.
deploymentIdstring–Use when the app name is ambiguous or already known.
descendingboolean–Return latest first, default true.
endTimestring–Application Manager time filter, ISO 8601.
environmentIdstring–Environment id. Use instead of environmentName.
environmentNamestring–Environment name, e.g. 'Production'. Resolved to an id, must match exactly one.
errorOnlyboolean–Only return ERROR and FATAL lines.
includeErrorsboolean–Include failed target errors when target is auto.
includeRawboolean–Include the raw Anypoint API objects alongside the normalized fields.
limitinteger–Maximum log entries, default 100, max 500.
offsetinteger–Application Manager log offset, default 0.
orgIdstring–Business group id. Defaults to ANYPOINT_ORG_ID, or the credentials' own organization.
searchTermsarray–Case-insensitive filters matched against timestamp, priority, message, logger, thread or instance.
specIdstring–Specific Application Manager deployment spec/config id.
startTimestring–Application Manager time filter, ISO 8601.
targetstring–Log source. Defaults to auto, which tries Application Manager then CloudHub.

No output schema declared.

No examples provided.

anypoint_list_api_manager_instances ~181

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

NameTypeReqDescription
assetIdstring–Filter by Exchange asset id.
environmentIdstring–Environment id. Use instead of environmentName.
environmentNamestring–Environment name, e.g. 'Production'. Resolved to an id, must match exactly one.
includeRawboolean–Include the raw Anypoint API objects alongside the normalized fields.
limitinteger–Maximum records, default 100.
offsetinteger–Pagination offset, default 0.
orgIdstring–Business group id. Defaults to ANYPOINT_ORG_ID, or the credentials' own organization.
technologystring–Filter by technology, e.g. mule4, flexGateway.

No output schema declared.

No examples provided.

anypoint_list_app_logs ~304

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.

NameTypeReqDescription
appNamestringyesDeployment/application name as shown in Runtime Manager.
deploymentIdstring–Use when the app name is ambiguous or already known.
descendingboolean–Return latest first, default true.
endTimestring–Application Manager time filter, ISO 8601.
environmentIdstring–Environment id. Use instead of environmentName.
environmentNamestring–Environment name, e.g. 'Production'. Resolved to an id, must match exactly one.
includeErrorsboolean–Include failed target errors when target is auto.
includeRawboolean–Include the raw Anypoint API objects alongside the normalized fields.
limitinteger–Maximum log entries, default 100, max 500.
offsetinteger–Application Manager log offset, default 0.
orgIdstring–Business group id. Defaults to ANYPOINT_ORG_ID, or the credentials' own organization.
specIdstring–Specific Application Manager deployment spec/config id.
startTimestring–Application Manager time filter, ISO 8601.
targetstring–Log source. Defaults to auto, which tries Application Manager then CloudHub.

No output schema declared.

No examples provided.

anypoint_list_business_groups ~70

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.

NameTypeReqDescription
rootOrgIdstring–Root organization id. Defaults to the credentials' own organization.

No output schema declared.

No examples provided.

anypoint_list_deployed_apps ~185

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

NameTypeReqDescription
environmentIdstring–Environment id. Use instead of environmentName.
environmentNamestring–Environment name, e.g. 'Production'. Resolved to an id, must match exactly one.
includeErrorsboolean–Include per-target errors when a target endpoint is unavailable or not permitted.
includeRawboolean–Include the raw Anypoint API objects alongside the normalized fields.
limitinteger–Maximum records to return, default 100.
orgIdstring–Business group id. Defaults to ANYPOINT_ORG_ID, or the credentials' own organization.
targetstring–Deployment target to query. Defaults to application_manager.

No output schema declared.

No examples provided.

anypoint_list_environments ~87

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.

NameTypeReqDescription
orgIdstring–Business group id. Defaults to ANYPOINT_ORG_ID, or the credentials' own organization.

No output schema declared.

No examples provided.

anypoint_search_archived_logs ~291

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.

NameTypeReqDescription
appNamestringyesDeployment name, must match the Runtime Manager name exactly.
datestringyesRequired date to search, YYYY-MM-DD (UTC).
endDatestring–Inclusive range end, YYYY-MM-DD (UTC). Max 7 days total.
environmentIdstring–Environment id. Use instead of environmentName.
environmentNamestring–Environment name, e.g. 'Production'. Resolved to an id, must match exactly one.
errorOnlyboolean–Only return ERROR and FATAL lines.
includeRawboolean–Include the raw Anypoint API objects alongside the normalized fields.
limitinteger–Cap on matched lines returned, default 500.
maxEntitiesinteger–Cap on replica entities probed during a full-scan fallback, default 150.
maxFilesinteger–Cap on archive files downloaded and parsed, default 100.
orgIdstring–Business group id. Defaults to ANYPOINT_ORG_ID, or the credentials' own organization.
searchTermsarray–Case-insensitive text filters.

No output schema declared.

No examples provided.

anypoint_search_exchange_assets ~142

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

NameTypeReqDescription
includeRawboolean–Include the raw Anypoint API objects alongside the normalized fields.
limitinteger–Maximum records, default 50.
offsetinteger–Pagination offset, default 0.
orgIdstring–Business group id. Defaults to ANYPOINT_ORG_ID, or the credentials' own organization.
searchstring–Free-text search over asset names and descriptions.
typesarray–Filter by asset type, e.g. rest-api, connector, template, example.

No output schema declared.

No examples provided.

anypoint_whoami ~43

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

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.