Verfy

MCP servers / @winor30/mcp-server-datadog

MCP tool changes

@winor30/mcp-server-datadog

2 of its last 5 updates changed what the agent reads: 0 tool descriptions rewritten, up to 1.8.0.

npm package · last recorded on 13 November 2026 on a clean machine with placeholder settings; only tools/list was sent. A changed description is not a vulnerability. npm page · Method and limits · this data as JSON.

Release by release

1.7.0 → 1.8.0

minor release, 22 June 2026

No tool definition changed.

1.6.0 → 1.7.0

minor release, 19 October 2025

No tool definition changed.

1.5.0 → 1.6.0

minor release, 8 June 2025

No tool definition changed.

1.4.0 → 1.5.0

minor release, 20 April 2025

Added: get_rum_applications, get_rum_events, get_rum_grouped_event_count, get_rum_page_performance, get_rum_page_waterfall

1.3.0 → 1.4.0

minor release, 6 April 2025

Added: get_all_services, query_metrics

Removed: get_metrics

Releases tried: 1.3.0 (2025-03-26); 1.4.0 (2025-04-06); 1.5.0 (2025-04-20); 1.6.0 (2025-06-08); 1.7.0 (2025-10-19); 1.8.0 (2026-06-22).

Tools in 1.8.0

The pin is the SHA-256 of the tool's name, description and input schema, as verfy.lock records it. The same pin in your lock means your agent reads this exact definition. Verfy 0.16.0 and later also pin a tool's title, annotations and output schema when the server sends them, so such a tool shows a different pin in your lock.

Tools in 1.8.0
ToolDescriptionPin
list_incidentsGet incidents from Datadogb087df5ca832
get_incidentGet an incident from Datadog7c4d76daaabd
query_metricsQuery timeseries points of metrics from Datadogb71447e516f7
get_logsSearch and retrieve logs from Datadogf1043823b309
get_all_servicesExtract all unique service names from logs231416bfa8fe
get_monitorsGet monitors status from Datadog768053e20a1d
list_dashboardsGet list of dashboards from Datadog21cd4aa508c4
get_dashboardGet a dashboard from Datadog79074e485b9f
list_tracesGet APM traces from Datadogef352defdfe5
mute_hostMute a host in Datadoged3a891bd938
unmute_hostUnmute a host in Datadoge06a64b4dbe1
list_hostsGet list of hosts from Datadog0d3ae2312021
get_active_hosts_countGet the total number of active hosts in Datadog (defaults to last 5 minutes)594fb8c8b374
list_downtimesList scheduled downtimes from Datadog211d55ecfe7d
schedule_downtimeSchedule a downtime in Datadog23812cd64d29
cancel_downtimeCancel a scheduled downtime in Datadog0c3e4a134e8f
get_rum_applicationsGet all RUM applications in the organization0accb043c2fe
get_rum_eventsSearch and retrieve RUM events from Datadogdba89e149936
get_rum_grouped_event_countSearch, group and count RUM events by a specified dimension53cb09ae1036
get_rum_page_performanceGet page (view) performance metrics from RUM datafdacf7c8f2ee
get_rum_page_waterfallRetrieve RUM page (view) waterfall data filtered by application name and session ID2fc09d98e774

Lock these tools

Pin what @winor30/mcp-server-datadog serves you today, commit the lock, and a pull request fails when a tool changes, with the text before and after. Pin the package version in your MCP config as well.

$ pip install verfy
$ verfy lock check --update   # shows each tool, then writes verfy.lock
$ git add verfy.lock
# .github/workflows/verfy.yml, after actions/checkout
- uses: verfy-dev/verfy-action@v1

Maintain this server? Run the same check on your releases and add the Locked by Verfy badge to your README.