Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.mcparmory/datadog

PYPI · MCPARMORY-DATADOG · 2 COMPONENTS

Monitor infrastructure, manage agents and deployments, track metrics, logs, and events

−5 this week 52 Trust /100

Last scanned (19 hours ago)

Scores higher than 55% of PyPI servers

Category Monitoring and Observability

Trust breakdown (7 categories)

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 2 of 45 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability0
  • Schema quality not yet verified: the captured schema was too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge it on a partial copy.Unverified
Stability & Change Management63
  • Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage0
  • Tool coverage not yet verified: the captured tool definitions were too large for us to store in full, or the server stopped listing its tools part-way, 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 (the trim removes the very descriptions this category reads), or the server stopped listing its tools part-way.Unverified
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 3 categories

Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

What we tested

Checks we ran (11)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Stability
  • MCP protocol

Checks we could not complete (3)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: the captured schema was too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge it on a partial copy.
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: the captured tool definitions were too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge them on a partial copy.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: the captured tool definitions were too large for us to store in full (the trim removes the very descriptions this category reads), or the server stopped listing its tools part-way.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Nov 26 −6
    • Stability: pass → 0.60 functional
  • 29 Oct 26 0
    • Stability: 0.97 → pass security
  • 28 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
  • 27 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
Diagnostics

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 5 Nov 2026 · Analysed pypi/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 pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Dependencies 45 packages
Packages resolved 45
Stale 1
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 770 exposed · ~89,127 tokens partial

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 →

Tool Tokens
list_device_tags ~61

No description provided.

NameTypeReqDescription
device_idstringyes–

No output schema declared.

No examples provided.

list_devices ~117

No description provided.

NameTypeReqDescription
filtertagstring––
pagenumberstring––
pagesizestring––

No output schema declared.

No examples provided.

list_downtimes ~107

No description provided.

NameTypeReqDescription
current_onlyboolean––
pagelimitstring––
pageoffsetstring––

No output schema declared.

No examples provided.

list_entity_risk_scores ~257

No description provided.

NameTypeReqDescription
entityTypearray––
filter_custom_attributestring––
filter_risk_score_maxnumber––
filter_risk_score_minnumber––
filter_severitystring––
fromstring––
pagenumberinteger––
pagesizeinteger––
tostring––

No output schema declared.

No examples provided.

list_environments ~83

No description provided.

NameTypeReqDescription
keystring––
limitinteger––
offsetinteger––

No output schema declared.

No examples provided.

list_event_bridge_sources ~38

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_events ~151

No description provided.

NameTypeReqDescription
filterfromstring––
filterquerystring––
filtertostring––
pagelimitstring––

No output schema declared.

No examples provided.

list_experiments ~109

No description provided.

NameTypeReqDescription
filterdataset_idstring––
filterproject_idstring––
pagelimitstring––

No output schema declared.

No examples provided.

list_fastly_accounts ~35

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_feature_flags ~109

No description provided.

NameTypeReqDescription
is_archivedboolean––
keystring––
limitinteger––
offsetinteger––

No output schema declared.

No examples provided.

list_findings ~424

No description provided.

NameTypeReqDescription
detailed_findingsboolean––
filterevaluationstring––
filterevaluation_changed_atstring––
filtermutedboolean––
filterresource_idstring––
filterresource_typestring––
filterrule_idstring––
filterrule_namestring––
filterstatusstring––
filtertagsstring––
filtervulnerability_typearray––
pagelimitstring––
snapshot_timestampstring––

No output schema declared.

No examples provided.

list_flaky_tests ~98

No description provided.

NameTypeReqDescription
include_historyboolean––
limitstring––

No output schema declared.

No examples provided.

list_gcp_scan_options ~41

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_gcp_sts_accounts ~41

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_gcp_sts_delegates ~48

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_gcp_usage_cost_configs ~32

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_heatmap_snapshots ~134

No description provided.

NameTypeReqDescription
filterapplication_idstring––
filterdevice_typestring––
filterview_namestringyes–
pagelimitinteger––

No output schema declared.

No examples provided.

list_historical_costs ~162

No description provided.

NameTypeReqDescription
include_connected_accountsboolean––
start_monthstringyes–
viewstring––

No output schema declared.

No examples provided.

list_hourly_usage ~312

No description provided.

NameTypeReqDescription
filterinclude_breakdownboolean––
filterinclude_connected_accountsboolean––
filterinclude_descendantsboolean––
filterproduct_familiesstringyes–
filtertimestampendstring––
filtertimestampstartstringyes–
pagelimitstring––
pagenext_record_idstring––

No output schema declared.

No examples provided.

list_incident_attachments ~88

No description provided.

NameTypeReqDescription
filterattachment_typestring––
incident_idstringyes–

No output schema declared.

No examples provided.

list_incident_failures ~104

No description provided.

NameTypeReqDescription
limitstring––
time_rangestring––

No output schema declared.

No examples provided.

list_incident_handles ~26

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_incident_impacts ~59

No description provided.

NameTypeReqDescription
incident_idstringyes–

No output schema declared.

No examples provided.

list_incident_integrations ~57

No description provided.

NameTypeReqDescription
incident_idstringyes–

No output schema declared.

No examples provided.

list_incident_todos ~63

No description provided.

NameTypeReqDescription
incident_idstringyes–

No output schema declared.

No examples provided.

list_incident_types ~52

No description provided.

NameTypeReqDescription
include_deletedboolean––

No output schema declared.

No examples provided.

list_incidents ~78

No description provided.

NameTypeReqDescription
pageoffsetstring––
pagesizestring––

No output schema declared.

No examples provided.

list_integrations ~29

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_interface_tags ~52

No description provided.

NameTypeReqDescription
interface_idstringyes–

No output schema declared.

No examples provided.

list_jira_accounts ~31

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_jira_issue_templates ~38

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_llm_observability_projects ~65

No description provided.

NameTypeReqDescription
pagelimitstring––

No output schema declared.

No examples provided.

list_log_archives ~22

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_log_metrics ~22

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_maintenances ~115

No description provided.

NameTypeReqDescription
filterpage_idstring––
filterstatusstring––
pagelimitinteger––
pageoffsetinteger––

No output schema declared.

No examples provided.

list_metric_configurations ~88

No description provided.

NameTypeReqDescription
metric_namestringyes–
windowsecondsstring––

No output schema declared.

No examples provided.

list_metric_tags ~195

No description provided.

NameTypeReqDescription
filterallow_partialboolean––
filterinclude_tag_valuesboolean––
filtermatchstring––
filtertagsstring––
metric_namestringyes–
pagelimitstring––
windowsecondsstring––

No output schema declared.

No examples provided.

list_metric_volumes ~54

No description provided.

NameTypeReqDescription
metric_namestringyes–

No output schema declared.

No examples provided.

list_metrics ~362

No description provided.

NameTypeReqDescription
filterconfiguredboolean––
filterinclude_percentilesboolean––
filtermetric_typestring––
filterqueriedboolean––
filterrelated_assetsboolean––
filtertags_configuredstring––
pagesizestring––
tag_filter_logicstring––
tag_filtersarray––
tag_wildcards_enabledboolean––
windowsecondsstring––

No output schema declared.

No examples provided.

list_monitor_downtimes ~104

No description provided.

NameTypeReqDescription
monitor_idstringyes–
pagelimitstring––
pageoffsetstring––

No output schema declared.

No examples provided.

list_monitor_policies ~28

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_monitor_templates ~33

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_monthly_cost_attribution ~277

No description provided.

NameTypeReqDescription
fieldsstringyes–
include_descendantsboolean––
next_record_idstring––
sort_directionstring––
sort_namestring––
start_monthstringyes–
tag_breakdown_keysstring––

No output schema declared.

No examples provided.

list_ms_teams_tenant_handles ~66

No description provided.

NameTypeReqDescription
tenant_idstring––

No output schema declared.

No examples provided.

list_ms_teams_webhook_handles ~45

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_notification_channels ~57

No description provided.

NameTypeReqDescription
user_idstringyes–

No output schema declared.

No examples provided.

list_notification_templates ~53

No description provided.

NameTypeReqDescription
filterincident-typestring––

No output schema declared.

No examples provided.

list_oci_products ~82

No description provided.

NameTypeReqDescription
productKeysstringyes–

No output schema declared.

No examples provided.

list_okta_accounts ~34

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_opsgenie_services ~40

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the com.mcparmory/datadog MCP server?

com.mcparmory/datadog runs locally as a PyPI package, launched with uvx mcparmory-datadog. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mcparmory-datadog

# add to Claude Code
claude mcp add com-mcparmory-datadog -- uvx mcparmory-datadog
Common questions

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 PyPI package (mcparmory-datadog).

Is the com.mcparmory/datadog MCP server safe to use?

com.mcparmory/datadog scores 52 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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.

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 5 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 com.mcparmory/datadog MCP server under?

com.mcparmory/datadog declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the com.mcparmory/datadog MCP server?

VerifyMCP ran 11 checks on com.mcparmory/datadog, covering Malware scan, Known CVEs, Install scripts, Dependency health and 7 more. 3 items could not be completed, a gap on our side rather than a finding about com.mcparmory/datadog: Schema quality, Tool coverage and Tool safety. 3 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.