Datadog (kud) MCP Server

@kud/mcp-datadog npm v0.2.0

Published by @kud — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Datadog server covering monitoring, metrics, logs, and dashboards.

Trust grade
A
92/100
Last scanned get badge →
Trust
A · 92/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 92/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 8 = 92. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

high Sensitive-source and external-sink co-existMTC-FLOW-004

Tools that read sensitive data ([datadog_get_usage_logs, datadog_get_logs_archive, datadog_get_logs_pipeline, datadog_get_logs_index, datadog_get_logs_metric]) and tools that can send data out ([datadog_create_webhook, datadog_get_webhook, datadog_update_webhook, datadog_delete_webhook]) are exposed together. An agent can move private data to the sink.

Evidence: sources [datadog_get_usage_logs, datadog_get_logs_archive, datadog_get_logs_pipeline, datadog_get_logs_index, datadog_get_logs_metric] → sinks [datadog_create_w

Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.

Location: flow datadog_get_usage_logs → datadog_create_webhook

Tools 175

Each tool and what it can reach — statically extracted from the published source.

  • datadog_create_webhooknetwork egress
  • datadog_delete_webhooknetwork egress
  • datadog_get_logs_archivereads sensitive data
  • datadog_get_logs_indexreads sensitive data
  • datadog_get_logs_metricreads sensitive data
  • datadog_get_logs_pipelinereads sensitive data
  • datadog_get_usage_logsreads sensitive data
  • datadog_get_webhooknetwork egress
  • datadog_update_webhooknetwork egress
  • datadog_add_permission_to_roleno sensitive capability
Show 165 more tools ↓
  • datadog_aggregate_logsno sensitive capability
  • datadog_aggregate_rum_eventsno sensitive capability
  • datadog_aggregate_spansno sensitive capability
  • datadog_cancel_downtimeno sensitive capability
  • datadog_create_api_keyno sensitive capability
  • datadog_create_apm_retention_filterno sensitive capability
  • datadog_create_aws_accountno sensitive capability
  • datadog_create_azure_integrationno sensitive capability
  • datadog_create_dashboardno sensitive capability
  • datadog_create_dashboard_listno sensitive capability
  • datadog_create_downtimeno sensitive capability
  • datadog_create_eventno sensitive capability
  • datadog_create_gcp_integrationno sensitive capability
  • datadog_create_host_tagsno sensitive capability
  • datadog_create_incidentno sensitive capability
  • datadog_create_incident_serviceno sensitive capability
  • datadog_create_incident_teamno sensitive capability
  • datadog_create_logs_archiveno sensitive capability
  • datadog_create_logs_metricno sensitive capability
  • datadog_create_logs_pipelineno sensitive capability
  • datadog_create_monitorno sensitive capability
  • datadog_create_notebookno sensitive capability
  • datadog_create_or_update_service_definitionno sensitive capability
  • datadog_create_roleno sensitive capability
  • datadog_create_rum_applicationno sensitive capability
  • datadog_create_security_ruleno sensitive capability
  • datadog_create_slono sensitive capability
  • datadog_create_synthetic_testno sensitive capability
  • datadog_create_teamno sensitive capability
  • datadog_create_userno sensitive capability
  • datadog_delete_api_keyno sensitive capability
  • datadog_delete_apm_retention_filterno sensitive capability
  • datadog_delete_application_keyno sensitive capability
  • datadog_delete_aws_accountno sensitive capability
  • datadog_delete_azure_integrationno sensitive capability
  • datadog_delete_dashboardno sensitive capability
  • datadog_delete_dashboard_listno sensitive capability
  • datadog_delete_gcp_integrationno sensitive capability
  • datadog_delete_host_tagsno sensitive capability
  • datadog_delete_incidentno sensitive capability
  • datadog_delete_incident_serviceno sensitive capability
  • datadog_delete_incident_teamno sensitive capability
  • datadog_delete_logs_archiveno sensitive capability
  • datadog_delete_logs_metricno sensitive capability
  • datadog_delete_logs_pipelineno sensitive capability
  • datadog_delete_monitorno sensitive capability
  • datadog_delete_notebookno sensitive capability
  • datadog_delete_roleno sensitive capability
  • datadog_delete_rum_applicationno sensitive capability
  • datadog_delete_security_ruleno sensitive capability
  • datadog_delete_service_definitionno sensitive capability
  • datadog_delete_slono sensitive capability
  • datadog_delete_synthetic_testsno sensitive capability
  • datadog_delete_teamno sensitive capability
  • datadog_disable_userno sensitive capability
  • datadog_enable_aws_log_servicesno sensitive capability
  • datadog_get_api_keyno sensitive capability
  • datadog_get_apm_retention_filterno sensitive capability
  • datadog_get_application_keyno sensitive capability
  • datadog_get_dashboardno sensitive capability
  • datadog_get_dashboard_listno sensitive capability
  • datadog_get_downtimeno sensitive capability
  • datadog_get_eventno sensitive capability
  • datadog_get_host_tagsno sensitive capability
  • datadog_get_host_totalsno sensitive capability
  • datadog_get_incidentno sensitive capability
  • datadog_get_incident_serviceno sensitive capability
  • datadog_get_incident_teamno sensitive capability
  • datadog_get_metric_metadatano sensitive capability
  • datadog_get_monitorno sensitive capability
  • datadog_get_notebookno sensitive capability
  • datadog_get_organizationno sensitive capability
  • datadog_get_roleno sensitive capability
  • datadog_get_rum_applicationno sensitive capability
  • datadog_get_security_ruleno sensitive capability
  • datadog_get_serviceno sensitive capability
  • datadog_get_slono sensitive capability
  • datadog_get_slo_historyno sensitive capability
  • datadog_get_synthetic_testno sensitive capability
  • datadog_get_synthetic_test_resultsno sensitive capability
  • datadog_get_teamno sensitive capability
  • datadog_get_usage_hostsno sensitive capability
  • datadog_get_usage_summaryno sensitive capability
  • datadog_get_usage_timeseriesno sensitive capability
  • datadog_get_usage_top_avg_metricsno sensitive capability
  • datadog_get_userno sensitive capability
  • datadog_list_active_metricsno sensitive capability
  • datadog_list_api_keysno sensitive capability
  • datadog_list_apm_retention_filtersno sensitive capability
  • datadog_list_application_keysno sensitive capability
  • datadog_list_aws_accountsno sensitive capability
  • datadog_list_aws_log_servicesno sensitive capability
  • datadog_list_azure_integrationsno sensitive capability
  • datadog_list_dashboard_listsno sensitive capability
  • datadog_list_dashboardsno sensitive capability
  • datadog_list_downtimesno sensitive capability
  • datadog_list_eventsno sensitive capability
  • datadog_list_gcp_integrationsno sensitive capability
  • datadog_list_host_tagsno sensitive capability
  • datadog_list_hostsno sensitive capability
  • datadog_list_incident_servicesno sensitive capability
  • datadog_list_incident_teamsno sensitive capability
  • datadog_list_incidentsno sensitive capability
  • datadog_list_logsno sensitive capability
  • datadog_list_logs_archivesno sensitive capability
  • datadog_list_logs_indexesno sensitive capability
  • datadog_list_logs_metricsno sensitive capability
  • datadog_list_logs_pipelinesno sensitive capability
  • datadog_list_monitorsno sensitive capability
  • datadog_list_notebooksno sensitive capability
  • datadog_list_organizationsno sensitive capability
  • datadog_list_role_permissionsno sensitive capability
  • datadog_list_role_usersno sensitive capability
  • datadog_list_rolesno sensitive capability
  • datadog_list_rum_applicationsno sensitive capability
  • datadog_list_security_rulesno sensitive capability
  • datadog_list_security_signalsno sensitive capability
  • datadog_list_servicesno sensitive capability
  • datadog_list_slosno sensitive capability
  • datadog_list_spansno sensitive capability
  • datadog_list_spans_advancedno sensitive capability
  • datadog_list_synthetic_locationsno sensitive capability
  • datadog_list_synthetic_testsno sensitive capability
  • datadog_list_teamsno sensitive capability
  • datadog_list_usersno sensitive capability
  • datadog_mute_hostno sensitive capability
  • datadog_query_metricsno sensitive capability
  • datadog_remove_permission_from_roleno sensitive capability
  • datadog_search_incidentsno sensitive capability
  • datadog_search_monitorsno sensitive capability
  • datadog_search_rum_eventsno sensitive capability
  • datadog_search_slono sensitive capability
  • datadog_submit_metricsno sensitive capability
  • datadog_submit_service_checkno sensitive capability
  • datadog_trigger_synthetic_testsno sensitive capability
  • datadog_unmute_hostno sensitive capability
  • datadog_update_api_keyno sensitive capability
  • datadog_update_apm_retention_filterno sensitive capability
  • datadog_update_application_keyno sensitive capability
  • datadog_update_azure_host_filtersno sensitive capability
  • datadog_update_azure_integrationno sensitive capability
  • datadog_update_dashboardno sensitive capability
  • datadog_update_dashboard_listno sensitive capability
  • datadog_update_downtimeno sensitive capability
  • datadog_update_gcp_integrationno sensitive capability
  • datadog_update_host_tagsno sensitive capability
  • datadog_update_incidentno sensitive capability
  • datadog_update_incident_serviceno sensitive capability
  • datadog_update_incident_teamno sensitive capability
  • datadog_update_logs_archiveno sensitive capability
  • datadog_update_logs_indexno sensitive capability
  • datadog_update_logs_metricno sensitive capability
  • datadog_update_logs_pipelineno sensitive capability
  • datadog_update_metric_metadatano sensitive capability
  • datadog_update_monitorno sensitive capability
  • datadog_update_notebookno sensitive capability
  • datadog_update_organizationno sensitive capability
  • datadog_update_roleno sensitive capability
  • datadog_update_rum_applicationno sensitive capability
  • datadog_update_security_ruleno sensitive capability
  • datadog_update_slono sensitive capability
  • datadog_update_synthetic_testno sensitive capability
  • datadog_update_teamno sensitive capability
  • datadog_update_userno sensitive capability
  • datadog_validate_monitorno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.2.0 latest A 92/100 1 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 92/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/kud-mcp-datadog/badge.svg)](https://mcptrustchecker.com/registry/kud-mcp-datadog)
HTML
<a href="https://mcptrustchecker.com/registry/kud-mcp-datadog"><img src="https://mcptrustchecker.com/registry/kud-mcp-datadog/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/kud-mcp-datadog/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @kud/mcp-datadog --online

Use the free API → How scoring works

Other implementations of Datadog 12

Independent packages implementing the same tool, scanned with the same engine. Compare all 13 side by side →

More in Cloud & DevOps