Atlas / MCP servers / winor30 / Datadog

DatadogSAFE

mcp/winor30/datadog
Verdict
SAFE
Grade
B
Trust score
89 /100
Exposed tools
1 1r · 0w · 0d
Transport
stdio
License
Apache-2.0
Stars
143
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

DISCLAIMER: This is a community-maintained project and is not officially affiliated with, endorsed by, or supported by Datadog, Inc. This MCP server utilizes the Datadog API but is developed independently as part of the Model Context Protocol ecosystem.

[](https://codecov.io/gh/winor30/mcp-server-datadog)[](https://smithery.ai/server/@winor30/mcp-server-datadog)

MCP server for the Datadog API, enabling incident management and more.

Features

  • Observability Tools: Provides a mechanism to leverage key Datadog monitoring features, such as incidents, monitors, logs, dashboards, and metrics, through the MCP server.
  • Extensible Design: Designed to easily integrate with additional Datadog APIs, allowing for seamless future feature expansion.

Tools

  1. list_incidents
  • Retrieve a list of incidents from Datadog.
  • Inputs:
  • filter (optional string): Filter parameters for incidents (e.g., status, priority).
  • pagination (optional object): Pagination details like page size/offset.
  • Returns: Array of Datadog incidents and associated metadata.
  1. get_incident
  • Retrieve detailed information about a specific Datadog incident.
  • Inputs:
  • incident_id (string): Incident ID to fetch details for.
  • Returns: Detailed incident information (title, status, timestamps, etc.).
  1. get_monitors
  • Fetch the status of
Read from source at commit 5e24862606cbOBSERVED · 2026-10-07
02

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.

claude-code
claude mcp add mcp-server-datadog --env DATADOG_API_KEY=${DATADOG_API_KEY} --env DATADOG_APP_KEY=${DATADOG_APP_KEY} -- npx -y @winor30/[email protected]
claude-desktop
{
  "mcpServers": {
    "mcp-server-datadog": {
      "command": "npx",
      "args": [
        "-y",
        "@winor30/[email protected]"
      ],
      "env": {
        "DATADOG_API_KEY": "${DATADOG_API_KEY}",
        "DATADOG_APP_KEY": "${DATADOG_APP_KEY}"
      }
    }
  }
}
03

Exposed tools (1)

1 read · 0 write · 0 destructive.

ToolRiskDescription
testreaddummy test description
04

Trust audit

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codePASS
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
declared (5 observation(s))
Network
none-observed
Shell
none-observed
Dependencies
not all pinned
Secrets in source
none-found

Findings (7)

LOWInventory / provenance · inv.hidden_file · CWE-1104
.prettierignore
.prettierignore
Why it matters. hidden member outside the usual dotfiles
Fix. review its purpose
LOWFilesystem / path · fs.traversal · CWE-22, CWE-59
src/tools/dashboards/tool.ts:1
import { ExtendedTool, ToolHandlers } from '../../utils/types'
LOWFilesystem / path · fs.traversal · CWE-22, CWE-59
src/tools/dashboards/tool.ts:3
import { createToolSchema } from '../../utils/tool'
LOWFilesystem / path · fs.traversal · CWE-22, CWE-59
src/tools/downtimes/tool.ts:1
import { ExtendedTool, ToolHandlers } from '../../utils/types'
LOWFilesystem / path · fs.traversal · CWE-22, CWE-59
src/tools/downtimes/tool.ts:3
import { createToolSchema } from '../../utils/tool'
LOWFilesystem / path · fs.traversal · CWE-22, CWE-59
src/tools/hosts/tool.ts:1
import { ExtendedTool, ToolHandlers } from '../../utils/types'
LOWSupply chain · supply.unpinned · CWE-829, CWE-1357
package.json
@datadog/datadog-api-client, zod, zod-to-json-schema, @eslint/eslintrc, @eslint/js, @types/jest, @types/node, eslint
Why it matters. 19 dependency range(s) float
Fix. pin exact versions or ship a lockfile

Gates applied: no_behavioural_pass.

Audited 2026-10-07 · audit v0.4.1 · source sha 5e24862606cbfull audit observations/trust-audit/mcp-server/winor30__datadog.json · Report an issue / request a re-scan
05

Audit history

Every audit this server has had. A grade with a past is a grade somebody is still checking.

DateSourceVerdictGradeScoreChange
2026-10-075e24862606cbSAFEB89first audit
06

Questions

What tools does Datadog expose?

1 in total: 1 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.

Is Datadog safe to connect to an agent?

The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.

What credentials does Datadog need?

It reads DATADOG_API_KEY and DATADOG_APP_KEY from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.

How does Datadog run?

It speaks stdio, so it runs as a local process your client starts. It is published on npm as @winor30/mcp-server-datadog at 1.8.0.

How current is this page?

The grade is for one exact copy of the source (5e24862606cb), read on 2026-10-07. The repository is watched and re-audited when it changes.

Advertisement