{ "SchemaVersion": "1", "Kind": "DirectoryEntry", "SubjectType": "mcp-server", "Slug": "netdata", "Name": "Netdata", "Title": "Netdata MCP Server | Pod", "Description": "Real-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection.", "CanonicalUrl": "https://askpod.ai/mcp/netdata", "MarkdownUrl": "https://askpod.ai/mcp/netdata.md", "JsonUrl": "https://askpod.ai/mcp/netdata.json", "DatePublished": "2026-08-31T23:50:54.202Z", "DateModified": "2026-08-31T23:50:54.202Z", "Publisher": "netdata.cloud", "RegistryName": "io.github.netdata/mcp-server", "WebsiteUrl": "https://www.netdata.cloud", "RepositoryUrl": "https://github.com/netdata/netdata", "VerificationStatus": "unverified", "Identities": [ { "Namespace": "mcp_endpoint", "Value": "https://app.netdata.cloud/api/v1/mcp" } ], "Sources": [ { "Source": "github_issues", "LastSeenAt": "2026-08-31T23:50:54.202Z" }, { "Source": "official_mcp_registry", "ExternalId": "io.github.netdata/mcp-server", "LastSeenAt": "2026-08-31T23:50:54.202Z" } ], "Categories": [], "FirstParty": true, "Deployments": [ { "Kind": "fixed_remote", "Transport": "streamable-http", "EndpointUrl": "https://app.netdata.cloud/api/v1/mcp", "ConfigSnippet": "{\n \"mcpServers\": {\n \"netdata\": {\n \"type\": \"http\",\n \"url\": \"https://app.netdata.cloud/api/v1/mcp\"\n }\n }\n}" } ], "Tools": { "Claimed": [], "ClaimedCount": 0, "Observed": null, "ObservedCount": null, "Verified": false, "Mismatch": null }, "Measured": null, "Usage": null, "Issues": [ { "Title": "[security] MCP dev-preview API key file I/O vulnerable to symlink following and blocking special-file opens", "Excerpt": "## Bug description\n\n`src/web/api/mcp_auth.c` handles the load, generation, and verification of the MCP developer-preview API key file (`mcp_dev_preview_api_key` under the netdata var-lib directory). The file I/O does not apply the regular-file / symlink / blocking-open protections that the rest of the codebase already enforces for comparable secret-bearing files (e.g. `src/web/api/v1/api_v1_manage.c`).\n\n### Vulnerable code\n\n**Load path** (`mcp_api_key_load`):\n```c\nint fd = open(path, O_RDONLY);\n", "SourceUrl": "https://github.com/netdata/netdata/issues/23161", "PublishedAt": "2026-07-17T00:56:25.000Z", "State": "open", "Comments": 0, "Reporter": "Contributor", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Netdata MCP v2.10.3 fails Codex Streamable HTTP handshake after initialize", "Excerpt": "### Bug description\n\nOpenAI Codex CLI fails to start the Netdata MCP server when using Codex's native Streamable HTTP MCP configuration.\n\nThis looks related to #21999 / #22000, but it does not appear to be the exact same missing `Mcp-Session-Id` issue. In my case, the Netdata server does return an `Mcp-Session-Id` for `initialize`, but Codex still fails while sending the `notifications/initialized` notification.\n\n### Codex configuration\n\n```toml\n[mcp_servers.netdata]\nurl = \"https:///netdat", "SourceUrl": "https://github.com/netdata/netdata/issues/22594", "PublishedAt": "2026-06-01T04:24:56.000Z", "State": "closed", "Comments": 0, "Reporter": "External", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Your MCP server earned an A security grade on Loaditout", "Excerpt": "Hi there,\n\nYour MCP server **netdata** passed all 7 criteria in our automated security grading system and earned an **A grade** on [Loaditout](https://loaditout.ai). Only 20.5% of the 20,000+ MCP servers we scanned earn this grade.\n\n## Add a security badge to your README\n\n```markdown\n[![Loaditout Security Grade](https://loaditout.ai/badge/netdata/netdata)](https://loaditout.ai/skills/netdata/netdata)\n```\n\nPreview: ![Loaditout Security Grade](https://loaditout.ai/badge/netdata/netdata)\n\n## Your l", "SourceUrl": "https://github.com/netdata/netdata/issues/22158", "PublishedAt": "2026-04-07T13:23:02.000Z", "State": "closed", "Comments": 0, "Reporter": "External", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Netdata MCP HTTP endpoint fails during initialization when used from Codex via Streamable HTTP", "Excerpt": "## Summary\n\nWe are using Codex with Netdata over MCP HTTP, and startup fails during initialization when the server is configured as a Streamable HTTP MCP endpoint.\n\nThe MCP server responds to `initialize`, but Codex then fails during or immediately after initialization with a transport-level error.\n\n## Environment\n\n- Netdata version: `v2.9.0`\n- Client: Codex\n- Transport: MCP over HTTP (`/mcp`)\n- Auth: `Authorization: Bearer `\n- Deployment: Netdata parent in Kubernetes behind ingress\n\n## A", "SourceUrl": "https://github.com/netdata/netdata/issues/21999", "PublishedAt": "2026-03-21T12:01:41.000Z", "State": "closed", "Comments": 0, "Reporter": "External", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "[Bug]: high CPU usage of the cgroups plugin", "Excerpt": "### Bug description\n\nI started observing around 17% CPU usage on my backup machine and 25% on my Raspberry Pi, though nothing changed on my main server.\r\n\r\nIt's quite a mystery to me as the two machines that exhibit the behavior have almost no containers running, whereas my main server does have many.\r\n\r\nIt seems to be the cgroups plugin's thread.\r\n\r\nI initially thought it was related to #16818 and tried to delete the cache, but it made no difference.\r\n\r\n\"Screenshot\r\n\r\n##### Feature idea summary\r\n\r\nFor the basic \"System Overview\" (i.e. the gauges)\r\n![image](https://user-images.githubusercontent.com/1153921/80827388-b9fee100-8b98-11ea-8f60-0d7824667cd3.gif)\r\n\r\nI would expect that they would be color coded ", "SourceUrl": "https://github.com/netdata/netdata/issues/10238", "PublishedAt": "2020-11-16T10:45:52.000Z", "State": "closed", "Comments": 3, "Reporter": "External", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Groom Inform Cloud about ACLK failure after claiming", "Excerpt": "#### Feature idea summary\r\nProduct Ask: \r\n - \"Claim for 1st time. If the claiming is successful but the ACLK is not established we should provide hints to the user and if possible send a hint to the Cloud so additional info can be presented to the Cloud users\"\r\n\r\n##### Expected behavior\r\nOn Cloud we should be able to show different messages for Unreachable agents:\r\n- ACLK dependencies are not installed\r\n- No connectivity to Cloud\r\n- Offline\r\n- Initiation phase", "SourceUrl": "https://github.com/netdata/netdata/issues/9401", "PublishedAt": "2020-06-23T10:02:14.000Z", "State": "closed", "Comments": 4, "Reporter": "Contributor", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "11", "Excerpt": "t", "SourceUrl": "https://github.com/netdata/netdata/issues/8268", "PublishedAt": "2020-03-03T03:01:12.000Z", "State": "closed", "Comments": 0, "Reporter": "External", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "demonstration of the agent locking problem and analysis", "Excerpt": "Add a document demonstrating the problem outlined in #8021 and the relevant analysis.", "SourceUrl": "https://github.com/netdata/netdata/issues/8113", "PublishedAt": "2020-02-17T16:56:03.000Z", "State": "closed", "Comments": 1, "Reporter": "Contributor", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Implement SOCKS5 support for the ACLK", "Excerpt": "#### Feature idea summary\r\n\r\nACLK connection to VerneMQ should be able to be proxied through SOCKS5 proxy.\r\nNetdata should accept the standard environmental variable for setting the proxy. This should be overwritten by a setting from the config file if found.\r\n\r\n* Define the config setting.\r\n* Testing will be via `ssh -D`.\r\n\r\nTesting configuration will be:\r\n* Fedora on the host where ssh -D is running.\r\n* A VM which is running the target sshd and VerneMQ - where VerneMQ is not accessible directl", "SourceUrl": "https://github.com/netdata/netdata/issues/8089", "PublishedAt": "2020-02-14T14:57:24.000Z", "State": "closed", "Comments": 0, "Reporter": "Contributor", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "How to install a plugin? (smartd_log)", "Excerpt": "Reading the [documentation](https://github.com/netdata/netdata/blob/master/docs/Add-more-charts-to-netdata.md) regarding adding more charts to netdata, it does not specifically mention how plugins can be installed and activated on Netdata.\r\n\r\nSpecifically I am interested on the [smartd_log](https://github.com/netdata/netdata/tree/master/collectors/python.d.plugin/smartd_log) plugin, but neither the [plugin readme](https://github.com/netdata/netdata/tree/master/collectors/python.d.plugin/smartd_", "SourceUrl": "https://github.com/netdata/netdata/issues/7415", "PublishedAt": "2019-12-03T19:48:19.000Z", "State": "closed", "Comments": 6, "Reporter": "External", "Rank": "top", "Extractor": "github_issue" }, { "Title": "Does not inform sufficiently of intent to report my data to Google Analytics", "Excerpt": "The netdata installer says the following:\r\n\r\n```\r\n The following changes will be made to your system:\r\n\r\n # USERS / GROUPS\r\n User 'netdata' and group 'netdata' will be added, if not present.\r\n\r\n # LOGROTATE\r\n This file will be installed if logrotate is present.\r\n\r\n - /etc/logrotate.d/netdata\r\n\r\n # SYSTEM INIT\r\n This file will be installed if this system runs with systemd:\r\n\r\n - /lib/systemd/system/netdata.service\r\n\r\n or, for older Centos, Debian/Ubuntu or OpenRC Gentoo:\r\n\r\n - /etc", "SourceUrl": "https://github.com/netdata/netdata/issues/7366", "PublishedAt": "2019-11-25T15:21:38.000Z", "State": "closed", "Comments": 38, "Reporter": "External", "Rank": "top", "Extractor": "github_issue" }, { "Title": "Tech refinement for agent claiming", "Excerpt": "There are some problems in implementing https://github.com/netdata/netdata/issues/7086 .\r\n\r\nThere is the problem of authenticating the netdata agent identification. MACHINE_GUID is not enough because:\r\n- MACHINE_GUID is not a secret, it can be visible in the network or known to other users. Thus it is not secure. Malicious netdata agents can copy the MACHINE_GUID and connect to netdata cloud hosts without authorization. Moreover, the original netdata agent will be locked out of netdata cloud whi", "SourceUrl": "https://github.com/netdata/netdata/issues/7286", "PublishedAt": "2019-11-07T16:17:00.000Z", "State": "closed", "Comments": 30, "Reporter": "Contributor", "Rank": "top", "Extractor": "github_issue" }, { "Title": "pattern for nginx error log", "Excerpt": "Hi all,\r\ncan anyone help me to find the pattern for this log:\r\n\r\n2019/04/15 07:40:34 [error] 23947#23947: *69867 connect() failed (111: Connection refused) while connecting to upstream,client: x.x.x.x,server: ,request: \"GET /favicon.ico HTTP/1.1\",upstream: \"https://x.x.x.x:6000/favicon.ico\",host: \"domain such as x-dev.cloud.com\",referrer: \"https://domain such as x-dev.cloud.com/\"\r\n\r\nI need the pattern to monitor nginx error.log\r\n\r\nThanks in advance.", "SourceUrl": "https://github.com/netdata/netdata/issues/5867", "PublishedAt": "2019-04-15T08:41:57.000Z", "State": "closed", "Comments": 10, "Reporter": "External", "Rank": "top", "Extractor": "github_issue" }, { "Title": "Use BabelJS to transpile dashboard.js and main.js to ES3", "Excerpt": "Some of our users run the Netdata Web GUI in older browsers (e.g. #4710). These browsers do not support modern (ES6+) JavaScript Features (e.g. for-of, const, etc.) A good solution would be to leverage a transpiler like [BabelJS](https://babeljs.io) to compile `dashboard.js` and `main.js` into ES3 (or ES5, as BabelJS seems to support only ES5). \r\n\r\nAn alternative would be to use TypeScript's compiler for this transpilation.\r\n\r\n\r\n