# io.github.CloudCorpRecords/metricwatch (npm · @reneturcios/metricwatch)

Datadog metrics, dashboards, logs, incidents, and monitors from your MCP client.

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@reneturcios/metricwatch`: 66/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-metricwatch/reneturcios-metricwatch.md), [page](https://verifymcp.io/servers/cloudcorprecords-metricwatch/reneturcios-metricwatch)
- oci · `ghcr.io/cloudcorprecords/metricwatch`: 42/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-metricwatch/ghcr-io-cloudcorprecords-metricwatch.md), [page](https://verifymcp.io/servers/cloudcorprecords-metricwatch/ghcr-io-cloudcorprecords-metricwatch)

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/metricwatch`
- Version: `0.1.0`
- 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-05.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 93 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 (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 524 tokens (~47/item across 11 items; 11 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 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 io.github.CloudCorpRecords/metricwatch MCP server?

io.github.CloudCorpRecords/metricwatch runs locally as an npm package, launched with npx -y @reneturcios/metricwatch. 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 cloudcorprecords-metricwatch -- npx -y @reneturcios/metricwatch
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-metricwatch": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/metricwatch"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-metricwatch": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/metricwatch"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-metricwatch -- npx -y @reneturcios/metricwatch
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add cloudcorprecords-metricwatch --command npx --arg -y --arg @reneturcios/metricwatch
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-metricwatch:
    command: "npx"
    args: ["-y", "@reneturcios/metricwatch"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-metricwatch": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@reneturcios/metricwatch"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloudcorprecords-metricwatch -t stdio -c npx -a -y @reneturcios/metricwatch
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-metricwatch": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/metricwatch"
      ]
    }
  }
}
```

## 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-04 (score 66, +1)

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

### 2026-11-02 (score 65, +1)

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

### 2026-11-01 (score 64)

First indexed and scored.

## MCP tools (11)

### `query_timeseries` (~90 tokens)

Query a Datadog metric timeseries over a time range using the metrics query language.

Input parameters:

- `from` (number, required): Start of the time range as a Unix epoch timestamp in seconds.
- `query` (string, required): Datadog metrics query expression, such as an aggregation over a metric with optional tag filters.
- `to` (number, required): End of the time range as a Unix epoch timestamp in seconds.

### `list_metrics` (~54 tokens)

List metric names available in the Datadog account.

Input parameters:

- `from` (number): Only return metrics that have been active since this Unix epoch timestamp in seconds.
- `limit` (number): Maximum number of metric names to return.

### `get_metric_metadata` (~39 tokens)

Get metadata for one metric: its type, unit, and description.

Input parameters:

- `metric_name` (string, required): Name of the metric to retrieve metadata for.

### `list_dashboards` (~31 tokens)

List dashboards in the Datadog account.

Input parameters:

- `limit` (number): Maximum number of dashboards to return.

### `get_dashboard` (~34 tokens)

Get one dashboard by id, including its widgets and layout.

Input parameters:

- `dashboard_id` (string, required): ID of the dashboard to retrieve.

### `search_logs` (~102 tokens)

Search Datadog log events with a log query over an optional time range.

Input parameters:

- `from` (number): Start of the search time range as a Unix epoch timestamp in seconds.
- `limit` (number): Maximum number of log events to return.
- `query` (string, required): Datadog log search query using log search syntax, such as service and status filters.
- `to` (number): End of the search time range as a Unix epoch timestamp in seconds.

### `list_incidents` (~30 tokens)

List Datadog incidents.

Input parameters:

- `limit` (number): Maximum number of incidents to return per page.

### `get_incident` (~29 tokens)

Get one incident by id.

Input parameters:

- `incident_id` (string, required): ID of the incident to retrieve.

### `list_monitors` (~43 tokens)

List monitors, optionally filtered by name.

Input parameters:

- `limit` (number): Maximum number of monitors to return per page.
- `name` (string): Filter monitors by name.

### `get_monitor` (~31 tokens)

Get one monitor by its integer id.

Input parameters:

- `monitor_id` (number, required): Integer ID of the monitor to retrieve.

### `list_downtimes` (~41 tokens)

List downtimes (scheduled monitor silences).

Input parameters:

- `current_only` (boolean): When true, return only downtimes that are currently active.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-metricwatch/reneturcios-metricwatch#diagnostics

## Score history

- 2026-11-05: 66
- 2026-11-04: 66
- 2026-11-03: 65
- 2026-11-02: 65
- 2026-11-01: 64

## Common questions

### What is the io.github.CloudCorpRecords/metricwatch MCP server?

io.github.CloudCorpRecords/metricwatch is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/metricwatch. Datadog metrics, dashboards, logs, incidents, and monitors from your MCP client. This page covers its npm package (@reneturcios/metricwatch).

### Is the io.github.CloudCorpRecords/metricwatch MCP server safe to use?

io.github.CloudCorpRecords/metricwatch scores 66 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 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 io.github.CloudCorpRecords/metricwatch MCP server expose?

io.github.CloudCorpRecords/metricwatch exposes 11 tools: query_timeseries, list_metrics, get_metric_metadata, list_dashboards, get_dashboard, and 6 more. Their descriptions and schemas cost roughly 524 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/metricwatch MCP server still maintained?

io.github.CloudCorpRecords/metricwatch is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.CloudCorpRecords/metricwatch MCP server under?

io.github.CloudCorpRecords/metricwatch declares the MIT 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/@reneturcios/metricwatch
- Socket report: https://socket.dev/npm/package/@reneturcios/metricwatch
- Repository: https://github.com/CloudCorpRecords/metricwatch
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-metricwatch/reneturcios-metricwatch.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-metricwatch/reneturcios-metricwatch.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-metricwatch/reneturcios-metricwatch