io.github.CloudCorpRecords/metricwatch
NPM · @RENETURCIOS/METRICWATCH · 2 COMPONENTS
Datadog metrics, dashboards, logs, incidents, and monitors from your MCP client.
Available components
Last scanned (19 hours ago)
Scores higher than 34% of npm servers
Category Monitoring and Observability
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 524 tokens (~47/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
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.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 1 Nov 26 64
First indexed and scored.
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 4 Nov 2026 · Analysed npm/@reneturcios/metricwatch@0.1.0
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_dashboard ~34
Get one dashboard by id, including its widgets and layout.
| Name | Type | Req | Description |
|---|---|---|---|
| dashboard_id | string | yes | ID of the dashboard to retrieve. |
No output schema declared.
No examples provided.
get_incident ~29
Get one incident by id.
| Name | Type | Req | Description |
|---|---|---|---|
| incident_id | string | yes | ID of the incident to retrieve. |
No output schema declared.
No examples provided.
get_metric_metadata ~39
Get metadata for one metric: its type, unit, and description.
| Name | Type | Req | Description |
|---|---|---|---|
| metric_name | string | yes | Name of the metric to retrieve metadata for. |
No output schema declared.
No examples provided.
get_monitor ~31
Get one monitor by its integer id.
| Name | Type | Req | Description |
|---|---|---|---|
| monitor_id | number | yes | Integer ID of the monitor to retrieve. |
No output schema declared.
No examples provided.
list_dashboards ~31
List dashboards in the Datadog account.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of dashboards to return. |
No output schema declared.
No examples provided.
list_downtimes ~41
List downtimes (scheduled monitor silences).
| Name | Type | Req | Description |
|---|---|---|---|
| current_only | boolean | – | When true, return only downtimes that are currently active. |
No output schema declared.
No examples provided.
list_incidents ~30
List Datadog incidents.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of incidents to return per page. |
No output schema declared.
No examples provided.
list_metrics ~54
List metric names available in the Datadog account.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
list_monitors ~43
List monitors, optionally filtered by name.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of monitors to return per page. |
| name | string | – | Filter monitors by name. |
No output schema declared.
No examples provided.
query_timeseries ~90
Query a Datadog metric timeseries over a time range using the metrics query language.
| Name | Type | Req | Description |
|---|---|---|---|
| from | number | yes | Start of the time range as a Unix epoch timestamp in seconds. |
| query | string | yes | Datadog metrics query expression, such as an aggregation over a metric with optional tag filters. |
| to | number | yes | End of the time range as a Unix epoch timestamp in seconds. |
No output schema declared.
No examples provided.
search_logs ~102
Search Datadog log events with a log query over an optional time range.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
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.
npm · @reneturcios/metricwatch
claude mcp add cloudcorprecords-metricwatch -- npx -y @reneturcios/metricwatch
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 4 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 4 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.