Log inSubmit server

Agent Check vs Netdata#Netdata

A side-by-side look at the Agent Check and Netdata#Netdata MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

A
Agent CheckMonitoringProcess monitoring for AI agents: start runs, submit per-task evidence, complete runs.37FairAuth: not declaredNetdata#Netdata logoNetdata#NetdataMonitoring · Local subprocess (stdio)Discovery, exploration, reporting and root cause analysis using all observability data, including metrics, logs, systems, containers, processes, and network connections57GoodAuth: api key required

Verdict: choose Agent Check for monitoring work; choose Netdata#Netdata for monitoring as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

A
Choose Agent Check when

  • You need dedicated capabilities in the Monitoring domain.
Explore Agent Check

Netdata#Netdata logoChoose Netdata#Netdata when

  • You need dedicated capabilities in the Monitoring domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
Explore Netdata#Netdata

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
A
Agent Check		Netdata#Netdata logoNetdata#Netdata
CategoryMonitoringMonitoring
Quality signal37/100 · Fair57/100 · Good
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—81,104
Directory activity 1 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
ToolsNot listedNot listed
Full listingView Agent Check View Netdata#Netdata

Tools & capabilities

Agent Check tools

No tool names declared yet. Check the project README from the listing page.

Netdata#Netdata tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Agent Check

No confirmed install command for Agent Check yet — follow the setup steps linked from its listing page rather than a guessed package name.

Netdata#Netdata

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "netdata-netdata-netdata": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/remote-mcp"
      ]
    }
  }
}

Frequently asked questions

Agent Check is categorized under Monitoring and uses an install path we have not confirmed yet. Netdata#Netdata belongs to Monitoring and uses a local stdio subprocess. Pick Agent Check for monitoring work and Netdata#Netdata for monitoring.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Agent Check has no confirmed install command yet — follow its own setup instructions.

Agent Check has no declared pricing — check the project's own site. Netdata#Netdata is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add agent-check and netdata-netdata-netdata as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Agent Check has a quality signal of 37/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Netdata#Netdata has 57/100 (Good) with 3 views, 0 installs and 81,104 GitHub stars.

Popular comparisons with Agent Check

Popular comparisons with Netdata#Netdata