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 (13 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 →

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
establish_org_connection ~73

No description provided.

NameTypeReqDescription
connection_typesarrayyes–
typestringyes–

No output schema declared.

No examples provided.

estimate_cost_by_organization ~207

No description provided.

NameTypeReqDescription
end_datestring––
include_connected_accountsboolean––
start_datestring––
viewstring––

No output schema declared.

No examples provided.

estimate_metric_cardinality ~195

No description provided.

NameTypeReqDescription
filtergroupsstring––
filterhours_agostring––
filterpctboolean––
filtertimespan_hstring––
metric_namestringyes–

No output schema declared.

No examples provided.

evaluate_deployment_gates ~118

No description provided.

NameTypeReqDescription
envstringyes–
primary_tagstring––
servicestringyes–
typestringyes–

No output schema declared.

No examples provided.

execute_workflow ~68

No description provided.

NameTypeReqDescription
payloadobject––
workflow_idstringyes–

No output schema declared.

No examples provided.

export_security_monitoring_rules ~92

No description provided.

NameTypeReqDescription
ruleIdsarrayyes–
typestringyes–

No output schema declared.

No examples provided.

fetch_custom_costs_file ~53

No description provided.

NameTypeReqDescription
file_idstringyes–

No output schema declared.

No examples provided.

fetch_reference_table_rows ~86

No description provided.

NameTypeReqDescription
idstringyes–
row_idarrayyes–

No output schema declared.

No examples provided.

fetch_rulesets ~117

No description provided.

NameTypeReqDescription
include_testing_rulesboolean––
include_testsboolean––
rulesetsarray––
typestringyes–

No output schema declared.

No examples provided.

generate_aws_external_id ~38

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

generate_slo_report ~151

No description provided.

NameTypeReqDescription
from_tsstringyes–
intervalstring––
querystringyes–
to_tsstringyes–

No output schema declared.

No examples provided.

get_action_connection ~45

No description provided.

NameTypeReqDescription
connection_idstringyes–

No output schema declared.

No examples provided.

get_agent_info ~60

No description provided.

NameTypeReqDescription
agent_keystringyes–

No output schema declared.

No examples provided.

get_agent_rule ~57

No description provided.

NameTypeReqDescription
agent_rule_idstringyes–

No output schema declared.

No examples provided.

get_app ~53

No description provided.

NameTypeReqDescription
app_idstringyes–

No output schema declared.

No examples provided.

get_app_key_registration ~56

No description provided.

NameTypeReqDescription
app_key_idstringyes–

No output schema declared.

No examples provided.

get_application_key ~50

No description provided.

NameTypeReqDescription
app_key_idstringyes–

No output schema declared.

No examples provided.

get_application_key_current_user ~56

No description provided.

NameTypeReqDescription
app_key_idstringyes–

No output schema declared.

No examples provided.

get_application_key_service_account ~76

No description provided.

NameTypeReqDescription
app_key_idstringyes–
service_account_idstringyes–

No output schema declared.

No examples provided.

get_archive ~45

No description provided.

NameTypeReqDescription
archive_idstringyes–

No output schema declared.

No examples provided.

get_aws_account_integration ~72

No description provided.

NameTypeReqDescription
aws_account_config_idstringyes–

No output schema declared.

No examples provided.

get_aws_ccm_config ~82

No description provided.

NameTypeReqDescription
aws_account_config_idstringyes–

No output schema declared.

No examples provided.

get_aws_cur_config ~62

No description provided.

NameTypeReqDescription
cloud_account_idstringyes–

No output schema declared.

No examples provided.

get_aws_ondemand_task ~64

No description provided.

NameTypeReqDescription
task_idstringyes–

No output schema declared.

No examples provided.

get_aws_persona_mapping ~59

No description provided.

NameTypeReqDescription
persona_mapping_idstringyes–

No output schema declared.

No examples provided.

get_aws_scan_options ~54

No description provided.

NameTypeReqDescription
account_idstringyes–

No output schema declared.

No examples provided.

get_azure_scan_options_subscription ~67

No description provided.

NameTypeReqDescription
subscription_idstringyes–

No output schema declared.

No examples provided.

get_azure_uc_config ~64

No description provided.

NameTypeReqDescription
cloud_account_idstringyes–

No output schema declared.

No examples provided.

get_branch_coverage_summary ~101

No description provided.

NameTypeReqDescription
branchstringyes–
repository_idstringyes–
typestringyes–

No output schema declared.

No examples provided.

get_budget ~48

No description provided.

NameTypeReqDescription
budget_idstringyes–

No output schema declared.

No examples provided.

get_case ~52

No description provided.

NameTypeReqDescription
case_idstringyes–

No output schema declared.

No examples provided.

get_change_request ~59

No description provided.

NameTypeReqDescription
change_request_idstringyes–

No output schema declared.

No examples provided.

get_cloudflare_account ~48

No description provided.

NameTypeReqDescription
account_idstringyes–

No output schema declared.

No examples provided.

get_commit_coverage_summary ~95

No description provided.

NameTypeReqDescription
commit_shastringyes–
repository_idstringyes–
typestringyes–

No output schema declared.

No examples provided.

get_component ~66

No description provided.

NameTypeReqDescription
component_idstringyes–
page_idstringyes–

No output schema declared.

No examples provided.

get_confluent_account ~55

No description provided.

NameTypeReqDescription
account_idstringyes–

No output schema declared.

No examples provided.

get_confluent_resource ~89

No description provided.

NameTypeReqDescription
account_idstringyes–
resource_idstringyes–

No output schema declared.

No examples provided.

get_critical_asset ~58

No description provided.

NameTypeReqDescription
critical_asset_idstringyes–

No output schema declared.

No examples provided.

get_custom_destination ~51

No description provided.

NameTypeReqDescription
custom_destination_idstringyes–

No output schema declared.

No examples provided.

get_custom_framework ~92

No description provided.

NameTypeReqDescription
handlestringyes–
versionstringyes–

No output schema declared.

No examples provided.

get_custom_rule ~92

No description provided.

NameTypeReqDescription
rule_namestringyes–
ruleset_namestringyes–

No output schema declared.

No examples provided.

get_custom_rule_revision ~91

No description provided.

NameTypeReqDescription
idstringyes–
rule_namestringyes–
ruleset_namestringyes–

No output schema declared.

No examples provided.

get_custom_ruleset ~67

No description provided.

NameTypeReqDescription
ruleset_namestringyes–

No output schema declared.

No examples provided.

get_dataset ~48

No description provided.

NameTypeReqDescription
dataset_idstringyes–

No output schema declared.

No examples provided.

get_datastore ~50

No description provided.

NameTypeReqDescription
datastore_idstringyes–

No output schema declared.

No examples provided.

get_degradation ~68

No description provided.

NameTypeReqDescription
degradation_idstringyes–
page_idstringyes–

No output schema declared.

No examples provided.

get_deployment ~100

No description provided.

NameTypeReqDescription
deployment_idstringyes–
limitstring––
pagestring––

No output schema declared.

No examples provided.

get_deployment_event ~53

No description provided.

NameTypeReqDescription
deployment_idstringyes–

No output schema declared.

No examples provided.

get_deployment_gate ~46

No description provided.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_deployment_gate_evaluation ~72

No description provided.

NameTypeReqDescription
idstringyes–

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.