com.mcparmory/datadog
OCI · GHCR.IO/MCPARMORY/DATADOG:1.0.3 · 2 COMPONENTS · SCANNED SEP 20
Monitor infrastructure, manage agents and deployments, track metrics, logs, and events
Available components
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 Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency32
- 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
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 130 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: the captured schema was too large for us to store in full, so we will not judge it on a partial copy.Unverified
Stability & Change Management0
- Stability not yet verified: the captured schema was too large for us to store in full, and comparing a partial copy would report our own trimming as a change.Unverified
Tool Coverage0
- Tool coverage not yet verified: the captured tool definitions were too large for us to store in full, so we will not judge them on a partial copy.Unverified
Tool Safety0
- Tool safety not yet verified: the captured tool definitions were too large for us to store in full, and the trim removes the very descriptions this category reads.Unverified
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 5 categories
Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the com.mcparmory/datadog MCP server?
com.mcparmory/datadog runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/datadog:1.0.3. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/mcparmory/datadog:1.0.3
claude mcp add com-mcparmory-datadog -- docker run --rm -i ghcr.io/mcparmory/datadog:1.0.3
{
"mcpServers": {
"com-mcparmory-datadog": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/datadog:1.0.3"
]
}
}
} {
"servers": {
"com-mcparmory-datadog": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/datadog:1.0.3"
]
}
}
} codex mcp add com-mcparmory-datadog -- docker run --rm -i ghcr.io/mcparmory/datadog:1.0.3
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-datadog": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/datadog:1.0.3"
],
"enabled": true
}
}
} mcp_servers:
com-mcparmory-datadog:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/mcparmory/datadog:1.0.3"] {
"McpServers": {
"com-mcparmory-datadog": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/datadog:1.0.3"
]
}
}
} {
"mcpServers": {
"com-mcparmory-datadog": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/datadog:1.0.3"
]
}
}
} 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.
- 26 Aug 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 6 Aug 26 0
- Stability: Stability not yet verified: the captured schema was too large for us to store in full, and comparing a partial copy would report our own trimming as a change. security
- MCP protocol: unverified → pass ▲ functional
- Schema quality: Schema quality not yet verified: the captured schema was too large for us to store in full, so we will not judge it on a partial copy. functional
- Tool coverage: Tool coverage not yet verified: the captured tool definitions were too large for us to store in full, so we will not judge them on a partial copy. functional
- 1 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 0
- Provenance: unverified → fail ▼ security
- License: unverified → fail ▼ functional
- Maintenance: unverified → pass ▲ functional
- 27 Jul 26 0
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 20 Sept 2026 · Analysed oci/ghcr.io/mcparmory/datadog:1.0.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
delete_aws_scan_options ~51
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | yes | – |
No output schema declared.
No examples provided.
delete_azure_scan_options ~52
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| subscription_id | string | yes | – |
No output schema declared.
No examples provided.
delete_azure_uc_config ~63
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| cloud_account_id | string | yes | – |
No output schema declared.
No examples provided.
delete_budget ~39
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| budget_id | string | yes | – |
No output schema declared.
No examples provided.
delete_case_type ~55
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| case_type_id | string | yes | – |
No output schema declared.
No examples provided.
delete_catalog_entity ~53
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | yes | – |
No output schema declared.
No examples provided.
delete_cloudflare_account ~49
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | yes | – |
No output schema declared.
No examples provided.
delete_component ~60
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| component_id | string | yes | – |
| page_id | string | yes | – |
No output schema declared.
No examples provided.
delete_confluent_account ~55
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | yes | – |
No output schema declared.
No examples provided.
delete_confluent_resource ~78
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | yes | – |
| resource_id | string | yes | – |
No output schema declared.
No examples provided.
delete_critical_asset ~51
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| critical_asset_id | string | yes | – |
No output schema declared.
No examples provided.
delete_custom_attribute ~78
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| case_type_id | string | yes | – |
| custom_attribute_id | string | yes | – |
No output schema declared.
No examples provided.
delete_custom_costs_file ~46
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| file_id | string | yes | – |
No output schema declared.
No examples provided.
delete_custom_destination ~48
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_destination_id | string | yes | – |
No output schema declared.
No examples provided.
delete_custom_framework ~81
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | – |
| version | string | yes | – |
No output schema declared.
No examples provided.
delete_custom_rule ~71
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| rule_name | string | yes | – |
| ruleset_name | string | yes | – |
No output schema declared.
No examples provided.
delete_data_connection ~79
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | yes | – |
| id | string | yes | – |
No output schema declared.
No examples provided.
delete_dataset ~40
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | – |
No output schema declared.
No examples provided.
delete_dataset_records ~119
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | – |
| project_id | string | yes | – |
| record_ids | array | yes | – |
| type | string | yes | – |
No output schema declared.
No examples provided.
delete_datasets ~100
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_ids | array | yes | – |
| project_id | string | yes | – |
| type | string | yes | – |
No output schema declared.
No examples provided.
delete_datastore ~45
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| datastore_id | string | yes | – |
No output schema declared.
No examples provided.
delete_datastore_item ~93
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| datastore_id | string | yes | – |
| item_key | string | yes | – |
| type | string | yes | – |
No output schema declared.
No examples provided.
delete_datastore_items ~99
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| datastore_id | string | yes | – |
| item_keys | array | – | – |
| type | string | yes | – |
No output schema declared.
No examples provided.
delete_degradation ~62
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| degradation_id | string | yes | – |
| page_id | string | yes | – |
No output schema declared.
No examples provided.
delete_deployment ~44
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| deployment_id | string | yes | – |
No output schema declared.
No examples provided.
delete_deployment_gate ~46
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
delete_deployment_rule ~68
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| gate_id | string | yes | – |
| id | string | yes | – |
No output schema declared.
No examples provided.
delete_environment ~44
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| environment_id | string | yes | – |
No output schema declared.
No examples provided.
delete_escalation_policy ~53
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| policy_id | string | yes | – |
No output schema declared.
No examples provided.
delete_event_bridge_source ~100
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | yes | – |
| event_generator_name | string | yes | – |
| region | string | yes | – |
| type | string | yes | – |
No output schema declared.
No examples provided.
delete_experiments ~81
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| experiment_ids | array | yes | – |
| type | string | yes | – |
No output schema declared.
No examples provided.
delete_fastly_account ~51
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | yes | – |
No output schema declared.
No examples provided.
delete_fastly_service ~70
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | yes | – |
| service_id | string | yes | – |
No output schema declared.
No examples provided.
delete_gcp_scan_options ~50
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | – |
No output schema declared.
No examples provided.
delete_gcp_sts_account ~60
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | yes | – |
No output schema declared.
No examples provided.
delete_heatmap_snapshot ~50
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| snapshot_id | string | yes | – |
No output schema declared.
No examples provided.
delete_incident ~43
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| incident_id | string | yes | – |
No output schema declared.
No examples provided.
delete_incident_event ~48
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| failure_id | string | yes | – |
No output schema declared.
No examples provided.
delete_issue_template ~49
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_template_id | string | yes | – |
No output schema declared.
No examples provided.
delete_jira_account ~57
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | yes | – |
No output schema declared.
No examples provided.
delete_kind ~47
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| kind_id | string | yes | – |
No output schema declared.
No examples provided.
delete_llm_observability_projects ~91
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| project_ids | array | yes | – |
| type | string | yes | – |
No output schema declared.
No examples provided.
delete_logs_metric ~50
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| metric_id | string | yes | – |
No output schema declared.
No examples provided.
delete_monitor_policy ~48
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| policy_id | string | yes | – |
No output schema declared.
No examples provided.
delete_monitor_template ~48
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| template_id | string | yes | – |
No output schema declared.
No examples provided.
delete_notification_rule ~77
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| notification_rule_id | string | yes | – |
| project_id | string | yes | – |
No output schema declared.
No examples provided.
delete_notification_rule_monitor ~50
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| rule_id | string | yes | – |
No output schema declared.
No examples provided.
delete_notification_template ~42
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
delete_okta_account ~51
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | yes | – |
No output schema declared.
No examples provided.
delete_opsgenie_service ~56
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| integration_service_id | string | yes | – |
No output schema declared.
No examples provided.
What is the com.mcparmory/datadog MCP server?
com.mcparmory/datadog is an MCP server listed in the public MCP registry as com.mcparmory/datadog. Monitor infrastructure, manage agents and deployments, track metrics, logs, and events. This page covers its container image (ghcr.io/mcparmory/datadog:1.0.3).
Is the com.mcparmory/datadog MCP server safe to use?
com.mcparmory/datadog scores 10 out of 100 on VerifyMCP. 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.
Is the com.mcparmory/datadog MCP server still maintained?
com.mcparmory/datadog is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.