com.mcparmory/datadog
PYPI · MCPARMORY-DATADOG · 2 COMPONENTS
Monitor infrastructure, manage agents and deployments, track metrics, logs, and events
Available components
Last scanned (17 hours ago)
Scores higher than 55% of PyPI servers
Category Monitoring and Observability
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
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 176 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, 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 →
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 →
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
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 →
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 →
get_retention_filter_apm ~56
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| filter_id | string | yes | – |
No output schema declared.
No examples provided.
get_role ~45
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| role_id | string | yes | – |
No output schema declared.
No examples provided.
get_rum_application ~59
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_rum_metric ~58
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| metric_id | string | yes | – |
No output schema declared.
No examples provided.
get_sbom ~141
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_type | string | yes | – |
| extformat | string | – | – |
| filterasset_name | string | yes | – |
| filterrepo_digest | string | – | – |
No output schema declared.
No examples provided.
get_schedule ~53
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_schedule_oncall ~45
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| schedule_id | string | yes | – |
No output schema declared.
No examples provided.
get_security_filter ~53
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| security_filter_id | string | yes | – |
No output schema declared.
No examples provided.
get_security_monitoring_rule ~54
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| rule_id | string | yes | – |
No output schema declared.
No examples provided.
get_service_definition ~77
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| schema_version | string | – | – |
| service_name | string | yes | – |
No output schema declared.
No examples provided.
get_signal ~39
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| signal_id | string | yes | – |
No output schema declared.
No examples provided.
get_slo_report_status ~62
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| report_id | string | yes | – |
No output schema declared.
No examples provided.
get_slo_status ~137
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| disable_corrections | boolean | – | – |
| from_ts | string | yes | – |
| slo_id | string | yes | – |
| to_ts | string | yes | – |
No output schema declared.
No examples provided.
get_span_metric ~57
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| metric_id | string | yes | – |
No output schema declared.
No examples provided.
get_status_page ~58
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| page_id | string | yes | – |
No output schema declared.
No examples provided.
get_suppression ~41
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| suppression_id | string | yes | – |
No output schema declared.
No examples provided.
get_suppressions_affecting_rule ~388
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| calculatedFields | array | – | – |
| cases | array | yes | – |
| complianceSignalOptions | object | – | – |
| filters | array | – | – |
| groupSignalsBy | array | – | – |
| hasExtendedTitle | boolean | – | – |
| isEnabled | boolean | yes | – |
| message | string | yes | – |
| name | string | yes | – |
| options | object | yes | – |
| queries | array | – | – |
| referenceTables | array | – | – |
| schedulingOptions | object | – | – |
| tags | array | – | – |
| thirdPartyCases | array | – | – |
No output schema declared.
No examples provided.
get_synthetics_suite ~54
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| public_id | string | yes | – |
No output schema declared.
No examples provided.
get_tag_pipeline_ruleset ~58
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| ruleset_id | string | yes | – |
No output schema declared.
No examples provided.
get_team ~44
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| team_id | string | yes | – |
No output schema declared.
No examples provided.
get_team_hierarchy_link ~54
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| link_id | string | yes | – |
No output schema declared.
No examples provided.
get_team_link ~66
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| link_id | string | yes | – |
| team_id | string | yes | – |
No output schema declared.
No examples provided.
get_teams_channel ~81
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_name | string | yes | – |
| team_name | string | yes | – |
| tenant_name | string | yes | – |
No output schema declared.
No examples provided.
get_tenancy_config ~63
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| tenancy_ocid | string | yes | – |
No output schema declared.
No examples provided.
get_threat_hunting_job ~49
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
No output schema declared.
No examples provided.
get_threat_hunting_signal ~60
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| histsignal_id | string | yes | – |
No output schema declared.
No examples provided.
get_user ~40
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | – |
No output schema declared.
No examples provided.
get_waf_custom_rule ~60
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_rule_id | string | yes | – |
No output schema declared.
No examples provided.
get_waf_exclusion_filter ~57
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| exclusion_filter_id | string | yes | – |
No output schema declared.
No examples provided.
get_workflow ~47
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| workflow_id | string | yes | – |
No output schema declared.
No examples provided.
get_workflow_instance ~77
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| instance_id | string | yes | – |
| workflow_id | string | yes | – |
No output schema declared.
No examples provided.
get_workflows_webhook_handle ~64
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| handle_id | string | yes | – |
No output schema declared.
No examples provided.
get_workload_protection_policy ~60
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| policy_id | string | yes | – |
No output schema declared.
No examples provided.
get_workload_security_agent_rule ~58
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_rule_id | string | yes | – |
No output schema declared.
No examples provided.
grant_role_to_restriction_query ~72
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| restriction_query_id | string | yes | – |
No output schema declared.
No examples provided.
import_incident ~197
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| declared | string | – | – |
| detected | string | – | – |
| fields | object | – | – |
| incident_type_uuid | string | – | – |
| resolved | string | – | – |
| title | string | yes | – |
| type | string | yes | – |
| visibility | string | – | – |
No output schema declared.
No examples provided.
initiate_reference_table_upload ~186
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| headers | array | yes | – |
| part_count | string | yes | – |
| part_size | string | yes | – |
| table_name | string | yes | – |
| type | string | yes | – |
No output schema declared.
No examples provided.
link_incident_to_case ~98
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | string | yes | – |
| id | string | yes | – |
| type | string | yes | – |
No output schema declared.
No examples provided.
link_jira_issue ~100
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | string | yes | – |
| jira_issue_url | string | yes | – |
| type | string | yes | – |
No output schema declared.
No examples provided.
list_account_facet_values ~93
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| facet_id | string | yes | – |
| limit | string | yes | – |
| type | string | yes | – |
No output schema declared.
No examples provided.
list_active_billing_dimensions ~43
No description provided.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_agent_rules ~36
No description provided.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_agent_versions ~38
No description provided.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_agents ~111
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| page_number | string | – | – |
| page_size | string | – | – |
| tags | string | – | – |
No output schema declared.
No examples provided.
list_aggregated_connections ~213
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | – |
| group_by | string | – | – |
| limit | string | – | – |
| tags | string | – | – |
| to | string | – | – |
No output schema declared.
No examples provided.
list_aggregated_dns_traffic ~254
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | – |
| group_by | string | – | – |
| limit | string | – | – |
| tags | string | – | – |
| to | string | – | – |
No output schema declared.
No examples provided.
list_allocation_rules ~32
No description provided.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_apm_retention_filters ~38
No description provided.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_app_key_registrations ~92
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| pagenumber | string | – | – |
| pagesize | string | – | – |
No output schema declared.
No examples provided.
list_application_keys ~131
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| filtercreated_atend | string | – | – |
| filtercreated_atstart | string | – | – |
| pagenumber | string | – | – |
| pagesize | string | – | – |
No output schema declared.
No examples provided.
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
claude mcp add com-mcparmory-datadog -- uvx mcparmory-datadog
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.