{
  "data": {
    "a": {
      "slug": "datadog-mcp",
      "name": "Datadog MCP Server",
      "vendor": "Datadog",
      "vendorUrl": "https://docs.datadoghq.com/mcp_server/",
      "company": "datadoghq.com",
      "kind": "mcp",
      "category": "observability",
      "summary": "Datadog's hosted MCP server for querying monitors, logs, metrics, traces, dashboards, incidents and more, with 30-plus toolsets, a sandboxed code-execution toolset, OAuth 2.0 or key auth, and per-call permission checks on writes.",
      "url": "https://www.anchorterminal.com/tools/datadog-mcp",
      "markdownUrl": "https://www.anchorterminal.com/tools/datadog-mcp.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/datadog-mcp.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/datadog-mcp.json",
      "dns": "datadog-mcp.grade.anchorterminal.com",
      "repo": "https://github.com/datadog-labs/mcp-server",
      "license": "MIT",
      "transports": [
        "streamable-http",
        "stdio"
      ],
      "remoteUrl": "https://mcp.datadoghq.com/v1/mcp",
      "packages": [],
      "auth": "mixed",
      "authNotes": "OAuth 2.0 (recommended, with an optional read-only grant that hides write tools), personal or service access tokens as a Bearer header, or `DD-API-KEY` plus `DD-APPLICATION-KEY` headers. A local `datadog_mcp_cli` binary gives you stdio where remote auth isn't possible. EU endpoint at mcp.datadoghq.eu. Users need the `mcp_read` and `mcp_write` permissions, and an organisation setting can block MCP writes.",
      "pricing": "byo-plan",
      "pricingNotes": "No separate charge stated. Datadog plan prices are public and a free plan exists. MCP use is capped by a default quota of 100,000 tool calls a month per organisation (raised from 50,000 on 2026-08-28) and a burst limit of 50 calls per 10 seconds. Whether the free plan includes MCP isn't stated (https://github.com/datadog-labs/mcp-server/blob/main/CHANGELOG.md).",
      "priceSummary": "Your plan",
      "where": "both",
      "x402": {
        "level": "no",
        "evidence": "No payments. Access follows the Datadog account.",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": 43,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-09-26"
      },
      "docsUrl": "https://docs.datadoghq.com/mcp_server/",
      "capabilities": [
        "observability.metrics",
        "observability.logs",
        "observability.traces",
        "observability.incidents"
      ],
      "tags": [
        "official",
        "hosted",
        "oauth",
        "toolsets",
        "enterprise",
        "preview-parts"
      ],
      "lastRelease": "2026-10-16",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 52.1,
        "grade": "D",
        "agentReady": false,
        "rank": 1096,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 10,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 78,
          "maintenance": 68,
          "payments": 30,
          "reliability": 33,
          "schema": 60,
          "security": 76,
          "transparency": 69
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-04"
        },
        "negative": -6,
        "negativeNotes": [
          "-3: published tool behaviour changed for existing callers with no notice, each posted in the changelog on or after the day it took effect. Detection-rule tools replaced and removed on 2026-06-17, `service` and `family` removed from `explore_profiling_call_graph` on 2026-06-26, `start_at` removed from `search_datadog_spans` on 2026-08-20, the `traces` extension removed from `execute_code` on 2026-09-24, `start_at` replaced by `cursor` on `search_datadog_rum_events` on 2026-10-08 and `lookback` removed from three RUM operation tools on 2026-10-09. Repeats of one kind fold into one term (https://github.com/datadog-labs/mcp-server/blob/main/CHANGELOG.md).",
          "-3: until 2026-09-22, `ddsql_upsert_saved_query` created or updated saved queries even when an organisation had disabled MCP writes. The fix in the hosted server is described only in the changelog, with no security advisory, which this run reads as an unadvised fix of the product's own flaw (https://github.com/datadog-labs/mcp-server/blob/main/CHANGELOG.md)."
        ],
        "verdict": "OAuth read-only grants, `mcp_read` and `mcp_write` permissions and an organisation-level block on MCP writes. Tools and parameters are removed the day they're announced, and a write-protection gap fixed on 22 September 2026 got no security advisory.",
        "bestFor": "Agents that triage production issues across metrics, logs, traces and monitors in a Datadog org. sentry-mcp is narrower and deeper on errors, pagerduty-mcp covers on-call.",
        "strengths": [
          "OAuth read-only grants, `mcp_read` and `mcp_write` permissions and an organisation-level block on MCP writes",
          "Toolsets, a sandboxed `execute_code` toolset and `whoami` and `toolsets` resources keep the schema in proportion",
          "Dated public changelog with 35 entries from 6 August to 16 October 2026",
          "Published burst limit and monthly quota",
          "SOC 2 Type 2, ISO 27001 and FedRAMP High, with a private HackerOne bounty"
        ],
        "weaknesses": [
          "Tools and parameters are removed the day they're announced, most recently `lookback` on three RUM tools on 9 October 2026",
          "Not in the official MCP registry, and Datadog's status host refuses our reader, so the incident record is unread",
          "Tool schemas and descriptions aren't readable without an account",
          "No security.txt, and the write-protection setting missed one tool until 22 September 2026, with no advisory",
          "Whether the free plan includes MCP isn't stated"
        ],
        "agentNotes": [
          "Use https://mcp.datadoghq.com/v1/mcp. The /api/unstable/ path in older configs is no longer the documented one",
          "Set `toolsets` to the two or three you need, for example core plus logs, and read the `toolsets` resource first",
          "Pass `limit` and `custom_attributes` on span searches and page with `cursor`. `start_at` is gone from spans and RUM events",
          "Pass `from` and `to` to the RUM operation tools. `lookback` was removed on 9 October 2026",
          "Budget calls. The org shares 100,000 a month and 50 per 10 seconds"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 2,
        "avgRating": 2.5,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "D",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 52.1
          }
        ],
        "editorialScores": {
          "ergonomics": 78,
          "maintenance": 68,
          "payments": 30,
          "reliability": 33,
          "schema": 60,
          "security": 76,
          "transparency": 56
        },
        "provenanceScore": 81,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-04",
            "maintenance": "2026-11-04",
            "payments": "2026-11-04",
            "reliability": "2026-11-04",
            "schema": "2026-11-04",
            "security": "2026-11-04",
            "transparency": "2026-11-04"
          },
          "last": "2026-11-04",
          "lastMoved": "2026-11-13",
          "oldest": "2026-11-04",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "claudeCode": "claude mcp add --transport http datadog https://mcp.datadoghq.com/v1/mcp",
        "config": {
          "mcpServers": {
            "datadog": {
              "type": "http",
              "url": "https://mcp.datadoghq.com/v1/mcp"
            }
          }
        },
        "headless": {
          "mcpServers": {
            "datadog": {
              "headers": {
                "DD-API-KEY": "${DD_API_KEY}",
                "DD-APPLICATION-KEY": "${DD_APPLICATION_KEY}"
              },
              "type": "http",
              "url": "https://mcp.datadoghq.com/v1/mcp"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/observability.metrics",
        "tool": "https://letme.dev/datadog-mcp"
      },
      "area": "developer",
      "provenance": {
        "legalEntity": "Datadog, Inc.",
        "domain": "datadoghq.com",
        "domainRegistered": "2010-07-09",
        "endpointOnVendorDomain": true,
        "terms": "https://datadoghq.com/legal/terms/",
        "privacy": "https://datadoghq.com/legal/privacy/",
        "statusPage": "https://status.datadoghq.com",
        "changelog": "",
        "securityTxt": "none",
        "checked": "2026-09-26",
        "score": 81
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/datadog-mcp.json",
      "live": {
        "slug": "datadog-mcp",
        "probe": {
          "target": "https://mcp.datadoghq.com/v1/mcp",
          "method": "mcp-initialize",
          "lastAt": "2026-11-18T23:13:17.534057558Z",
          "lastOk": true,
          "lastStatus": 401,
          "lastMs": 374,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 273,
          "p95ms24h": 445,
          "samples24h": 241,
          "samples30d": 7842,
          "days": [
            {
              "date": "2026-10-18",
              "probes": 256,
              "ok": 256
            },
            {
              "date": "2026-10-19",
              "probes": 255,
              "ok": 255
            },
            {
              "date": "2026-10-20",
              "probes": 252,
              "ok": 252
            },
            {
              "date": "2026-10-21",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-22",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-23",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-24",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-10-25",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-10-26",
              "probes": 252,
              "ok": 252
            },
            {
              "date": "2026-10-27",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-28",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-10-29",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-30",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-31",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-11-01",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-11-02",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-11-03",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-11-04",
              "probes": 246,
              "ok": 246
            },
            {
              "date": "2026-11-05",
              "probes": 185,
              "ok": 185
            },
            {
              "date": "2026-11-06",
              "probes": 241,
              "ok": 241
            },
            {
              "date": "2026-11-07",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-08",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-09",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-10",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-11",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-12",
              "probes": 245,
              "ok": 245
            },
            {
              "date": "2026-11-13",
              "probes": 238,
              "ok": 238
            },
            {
              "date": "2026-11-14",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-15",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-16",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-17",
              "probes": 242,
              "ok": 242
            },
            {
              "date": "2026-11-18",
              "probes": 233,
              "ok": 233
            }
          ],
          "since": "2026-10-08T00:00:00Z"
        },
        "vendorStatus": {
          "page": "https://status.datadoghq.com",
          "indicator": "unknown",
          "summary": "no machine-readable status found",
          "checkedAt": "2026-11-18T18:52:21.232624173Z"
        },
        "githubStars": 48,
        "securityTxt": {
          "url": "https://datadoghq.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-18T16:31:00.360214961Z"
        },
        "domain": {
          "domain": "datadoghq.com",
          "registered": "2010-07-09",
          "source": "https://rdap.verisign.com/com/v1/domain/datadoghq.com",
          "checkedAt": "2026-11-15T15:33:24.496957247Z"
        },
        "pages": [
          {
            "url": "https://raw.githubusercontent.com/datadog-labs/mcp-server/main/CHANGELOG.md",
            "kind": "deprecations",
            "status": 304,
            "checkedAt": "2026-11-18T21:54:44.604205059Z",
            "changedAt": "2026-11-16T20:34:02.737516625Z",
            "fingerprint": "700ee920d4b8"
          },
          {
            "url": "https://datadoghq.com/legal/privacy/",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-11-18T21:36:19.073755844Z",
            "changedAt": "2026-11-14T18:56:07.465017135Z",
            "fingerprint": "676c287835de"
          },
          {
            "url": "https://datadoghq.com/legal/terms/",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-11-18T21:36:21.660387695Z",
            "changedAt": "2026-11-14T18:56:09.988592339Z",
            "fingerprint": "587db62d847d"
          }
        ],
        "mcpTools": {
          "url": "https://mcp.datadoghq.com/v1/mcp",
          "checkedAt": "2026-11-18T04:23:02.217226665Z",
          "status": "auth",
          "note": "asks for credentials before listing its tools",
          "changedAt": "2026-09-28T21:55:38.616526541Z"
        },
        "github": {
          "repo": "datadog-labs/mcp-server",
          "checkedAt": "2026-11-16T11:55:02.001338229Z",
          "stars": 48,
          "archived": false,
          "issuesEnabled": false,
          "pushedAt": "2026-11-06T20:32:15Z",
          "openIssues": 0,
          "openPRs": 1,
          "issuesOpened90d": 0,
          "issuesClosed90d": 0,
          "prsMerged90d": 2
        },
        "updatedAt": "2026-11-18T23:13:17.534057558Z"
      },
      "streak": {
        "days": 34,
        "from": "2026-10-15",
        "last": {
          "kind": "shutdown",
          "date": "2026-10-15",
          "what": "`get_datadog_spreadsheet_table_data` removed from the `sheets` toolset. Use `get_datadog_spreadsheet_tab_data`",
          "source": "https://raw.githubusercontent.com/datadog-labs/mcp-server/main/CHANGELOG.md"
        },
        "best": 34
      }
    },
    "answer": "Datadog MCP Server scores 52.1 (D) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 5 of 7 scored categories.",
    "b": {
      "slug": "neat-pulse-mcp",
      "name": "Neat Pulse MCP",
      "vendor": "Neat",
      "vendorUrl": "https://neat.no",
      "company": "neat.no",
      "kind": "mcp",
      "category": "observability",
      "summary": "Neat Pulse MCP is Neat's local MCP server for Neat Pulse, the cloud service that manages Neat's meeting-room video devices. Agents list devices and rooms, read sensor data, reboot devices and change room set-up, for paid Pulse customers.",
      "url": "https://www.anchorterminal.com/tools/neat-pulse-mcp",
      "markdownUrl": "https://www.anchorterminal.com/tools/neat-pulse-mcp.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/neat-pulse-mcp.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/neat-pulse-mcp.json",
      "dns": "neat-pulse-mcp.grade.anchorterminal.com",
      "transports": [
        "stdio"
      ],
      "packages": [
        {
          "registry": "npm",
          "name": "@neat-no/pulse-mcp"
        }
      ],
      "auth": "api-key",
      "authNotes": "A Neat Pulse API token in `PULSE_API_TOKEN`, with the organisation ID in `PULSE_ORG_ID`. Only an Owner of the Pulse organisation can create tokens, in the portal under Settings \u003e API Keys. A token takes either the Read scope or all scopes, is shown once, can be revoked, and the Pulse API has a key-rotation endpoint. The token's name appears in Pulse's audit logs.",
      "pricing": "byo-plan",
      "pricingNotes": "Included at no extra cost with a paid Neat Pulse Plus or Pro plan, and every device in the organisation must be on a paid plan. Plus and Pro are sold through resellers, with no public price. The free Pulse Starter plan doesn't include MCP or API access.",
      "priceSummary": "Your plan",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 on neat.no, support.neat.no or the Pulse API reference, read on 2026-11-18. Pulse plans are bought through resellers.",
        "endpoints": []
      },
      "toolCount": 30,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-18"
      },
      "docsUrl": "https://support.neat.no/article/neat-pulse-mcp-server/",
      "capabilities": [
        "observability.metrics"
      ],
      "tags": [
        "mcp",
        "stdio",
        "npm",
        "node",
        "api-key",
        "audit-log",
        "read-only-mode",
        "hardware",
        "meeting-rooms",
        "paid-plan",
        "iso-27001"
      ],
      "lastRelease": "2026-11-17",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 45.8,
        "grade": "E",
        "agentReady": false,
        "rank": 1268,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 11,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 43,
          "maintenance": 59,
          "payments": 0,
          "reliability": 35,
          "schema": 49,
          "security": 79,
          "transparency": 56
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-18"
        },
        "negative": 0,
        "verdict": "Agents get 30 documented tools for a Neat device fleet, behind a revocable Pulse API token that can be read-only, with every action written to Pulse's audit log. It needs a paid Pulse plan bought through a reseller, prices aren't public, and there is no public source, changelog or status page.",
        "bestFor": "IT administrators running Neat meeting-room devices on Pulse who want an agent to check fleet health, sensor readings and room set-up.",
        "strengths": [
          "A Pulse API token can be limited to the Read scope, which the docs say stops the server rebooting, deleting, creating or updating anything",
          "Every action taken through the MCP server is recorded in Pulse's audit logs under the token's name, and `list_audit_logs` reads them",
          "security.txt, a vulnerability reporting policy, public security advisories through 2026 and an ISO 27001 statement on Neat's support site",
          "Version 1.1.0 on 17 November 2026, four releases since 17 September 2026, and setup steps for seven MCP clients",
          "A data model guide served as an MCP resource and a tool, with IDs, hierarchy and which actions can't be undone"
        ],
        "weaknesses": [
          "Needs a paid Pulse Plus or Pro plan bought through a reseller, with no public price, no trial for MCP and no self-serve route for an agent",
          "No public source repository, licence, changelog or status page found",
          "Irreversible tools (delete room, delete device, reboot, reset enrolment code) rely on the assistant asking first. No server-side confirmation was found",
          "No rate limits or 429 handling documented for the server or the Pulse API",
          "Runs only in clients that can start local programs, and needs Node.js 20 or later"
        ],
        "agentNotes": [
          "Ask the person to confirm before `delete_room`, `delete_device`, `reboot_device` or `reset_enrolment_code`. Deleting a room unenrols all its devices",
          "Ask the person before `send_message_to_device` or `send_message_to_room`, because the message shows on screens in the room",
          "Call `get_domain_guide` first if the client doesn't read MCP resources, to learn the region, location, room and device hierarchy",
          "If `move_device` returns `profile_confirmation_needed`, ask whether to apply the room's profile, then repeat the call with `assign_room_profile`",
          "If a call returns 401, ask the person for a new Pulse token. If it returns 404, check `PULSE_ORG_ID`"
        ],
        "metrics": {
          "kind": "local",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "E",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 45.8
          }
        ],
        "editorialScores": {
          "ergonomics": 43,
          "maintenance": 59,
          "payments": 0,
          "reliability": 35,
          "schema": 49,
          "security": 79,
          "transparency": 47
        },
        "provenanceScore": 65,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-18",
            "maintenance": "2026-11-18",
            "payments": "2026-11-18",
            "reliability": "2026-11-18",
            "schema": "2026-11-18",
            "security": "2026-11-18",
            "transparency": "2026-11-18"
          },
          "last": "2026-11-18",
          "oldest": "2026-11-18",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "install": "npx -y @neat-no/pulse-mcp@latest   # needs PULSE_API_TOKEN and PULSE_ORG_ID in the environment",
        "claudeCode": "claude mcp add neat-pulse -s user -e PULSE_API_TOKEN=YOUR_PULSE_TOKEN -e PULSE_ORG_ID=YOUR_ORG_ID -- npx -y @neat-no/pulse-mcp@latest",
        "config": {
          "mcpServers": {
            "neat-pulse": {
              "args": [
                "-y",
                "@neat-no/pulse-mcp@latest"
              ],
              "command": "npx",
              "env": {
                "PULSE_API_TOKEN": "YOUR_PULSE_TOKEN",
                "PULSE_ORG_ID": "YOUR_ORG_ID"
              }
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/observability.metrics",
        "tool": "https://letme.dev/neat-pulse-mcp"
      },
      "area": "developer",
      "provenance": {
        "legalEntity": "Neatframe Limited",
        "domain": "neat.no",
        "domainRegistered": "",
        "endpointOnVendorDomain": true,
        "terms": "https://neat.no/neat-pulse-terms-and-conditions/",
        "privacy": "https://neat.no/privacy-policy/",
        "statusPage": "",
        "changelog": "",
        "securityTxt": "valid",
        "checked": "2026-11-18",
        "notes": [
          "The Neat Pulse Agreement (last updated 26 March 2025) is between Neatframe Ltd. and the customer, and the privacy notice (13 July 2026) is Neatframe Limited's. The company page says Neat is based in Oslo.",
          "neat.no/robots.txt allows ClaudeBot and anthropic-ai outside account, cart, checkout and admin paths, with a crawl delay of 10 seconds. support.neat.no, api.pulse.neat.no and registry.npmjs.org allow all agents.",
          "neat.no/.well-known/security.txt gives security@neat.no, expires 7 August 2027 and links the vulnerability reporting policy on support.neat.no.",
          "No status page for Neat Pulse was linked from any page read. The MCP server calls the Pulse API at api.pulse.neat.no."
        ],
        "score": 65
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/neat-pulse-mcp.json"
    },
    "edges": [
      {
        "by": 35,
        "category": "ergonomics",
        "leads": "datadog-mcp",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "More than 30 toolsets chosen with the `toolsets` parameter, `omit_tools` per the 30 September check, `whoami` and `toolsets` resources, and a core set trimmed by about 15 per cent in March. An `execute_code` toolset runs sandboxed TypeScript against the APIs instead of one tool per call. We couldn't count the default tools (20). `limit`, cursors, `custom_attributes`, token budgets and flattening on aggregates, and `exclude_fields` on Kubernetes manifests (19). The changelog shows a steady effort on actionable errors (15). OAuth read-only grants omit write tools, an org setting blocks MCP writes, and read-only calls retry automatically. The 13 October entry says `execute_code` is now marked read-only so that clients asking approval for write-capable tools classify it correctly, but no entry names readOnlyHint or destructiveHint, so the annotation credit isn't added (12). Official Datadog API clients in several languages and Python agent examples in the repository (12).",
          "b": "30 tools, in the 11 to 30 band, with no toolsets or read-only subset that hides write tools that we found (15). `list_audit_logs` pages between dates, but `list_devices` and `list_rooms` return everything in the organisation (6). Documented 401 and 404 causes, and `move_device` returns a status asking for confirmation instead of failing (10). Annotations couldn't be read. The docs ask the assistant to confirm reboots and messages, and no idempotency is described (5). Two environment variables to start. The Pulse API reference shows generated client snippets, but no official SDK package was found (7). 15 + 6 + 10 + 5 + 7 = 43."
        },
        "scores": {
          "a": 78,
          "b": 43
        }
      },
      {
        "by": 30,
        "category": "payments",
        "leads": "datadog-mcp",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "No x402, MPP or L402 (0). Datadog plan prices are public and the MCP quota of 100,000 calls a month per organisation is published, but there's no MCP price or per-call rate (10). A free Datadog plan exists per the 30 September check, and nothing we read says whether it includes MCP, so half (10). A person signs up and authorises OAuth or creates keys (0). Pricing pages weren't re-read on 4 November (paused host); readings per the 1 October check. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.",
          "b": "No payment protocol (0). Pulse Plus and Pro are sold through resellers and the Pulse Agreement says the price is on the reseller's invoice, so no price is public (0). The free Starter plan excludes MCP and API access (0). A person must buy a plan and an Owner must create the token in the portal (0). 0 + 0 + 0 + 0 = 0."
        },
        "scores": {
          "a": 30,
          "b": 0
        }
      },
      {
        "by": 13,
        "category": "transparency",
        "leads": "datadog-mcp",
        "name": "Transparency \u0026 trust",
        "reasons": {
          "a": "The hosted server is closed with published terms, and the examples repository is MIT (18). Privacy policy, DPA and a trust centre exist, but we found nothing MCP-specific on what the server logs or keeps (18). The changelog labels breaking changes and deprecations, for example `get_datadog_spreadsheet_table_data` deprecated on 20 July, but removals ship the day they're announced, and nothing says whether the old /api/unstable/ URL still works (8). Since 1 October one removal had notice. `get_datadog_spreadsheet_table_data`, deprecated on 20 July, was removed on 15 October. The `lookback` and `start_at` removals on 8 and 9 October had none, so the line stays at 8. Datadog sites per region are documented. The subprocessor list sits behind the trust centre's request form (12).",
          "b": "Closed source, and the npm package carries no licence field. The Pulse Agreement covers the service clearly (12). A privacy notice of 13 July 2026, a DPA, a GDPR page and a data residency article, with retention described only as long as necessary (18). The Pulse Agreement supports the current and prior major release, and nothing covers the MCP server's deprecation (3). Pulse data stays in one Azure region per chosen zone, mapped by name. No subprocessor list was read (14). 12 + 18 + 3 + 14 = 47."
        },
        "scores": {
          "a": 69,
          "b": 56
        }
      },
      {
        "by": 11,
        "category": "schema",
        "leads": "datadog-mcp",
        "name": "Schema \u0026 documentation",
        "reasons": {
          "a": "Tool schemas are only visible through tools/list with an account. The changelog shows typed parameters, for example `limit` 1 to 1,000 and percentile enums, so we gave partial credit for a contract we couldn't read (15). We couldn't check docs.datadoghq.com/llms.txt because our fetch proxy refused it, and the listing doesn't record one (0). Changelog entries show descriptions being corrected, such as `search_pr_insights` now explaining that `expected` means pending (10). Ranges, cursors, enums and attribute selectors per the changelog (11). Errors are being made actionable, with reversed time windows rejected up front and an explicit `result_too_large` failure (9). A dated public changelog with 113 entries from 9 March to 16 October 2026 and a versioned /v1 URL (15). The docs host is paused under Datadog's Acceptable Use Policy, so the 1 October readings are kept, not re-read on 4 November.",
          "b": "The npm metadata lists zod and the MCP SDK, but the tool schemas themselves weren't read, since the source isn't public and the package wasn't installed. Partial credit for a contract that exists but isn't published, as for Causely (12). No llms.txt found. The README points agents to an `llms-install.md` in the package, which wasn't read (5). The support reference describes every tool, what it returns and which changes can't be undone, and the domain guide explains the data model (14). Inputs are described only in passing, such as `assign_room_profile` (5). Example prompts, a troubleshooting table for 401, 404 and npx errors, and the `profile_confirmation_needed` status (8). Semver versions on npm and dated support articles, but no changelog (5). 12 + 5 + 14 + 5 + 8 + 5 = 49."
        },
        "scores": {
          "a": 60,
          "b": 49
        }
      },
      {
        "by": 9,
        "category": "maintenance",
        "leads": "datadog-mcp",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "Latest changelog entry 16 October 2026, 19 days before this check (30). 35 dated entries from 6 August to 16 October (20). Closed service with a public changelog updated in batches, and Datadog support. Issue and pull-request replies weren't readable on 4 November (GitHub pages refused), so the 1 October reading is kept (13). Not in the official MCP registry per the 1 October check, not re-read (0). Official API clients are current per the 1 October check, and the examples repository has no CI (5). 30+20+13+0+5 = 68.",
          "b": "1.1.0 on 17 November 2026 (30). 0.2.2, 0.2.3, 1.0.0 and 1.1.0 since 17 September 2026 (20). Closed source with no public changelog. Paid plans include priority email support with an SLA per the Pulse Agreement, and the setup guide was updated on 17 November (5). Not in the official MCP registry, by a search for Neat (0). Current MCP SDK and zod versions in the npm metadata, with no visible CI (4). 30 + 20 + 5 + 0 + 4 = 59."
        },
        "scores": {
          "a": 68,
          "b": 59
        }
      }
    ],
    "facts": [
      {
        "a": "MCP server",
        "b": "MCP server",
        "name": "Kind"
      },
      {
        "a": "Datadog",
        "b": "Neat",
        "name": "Vendor"
      },
      {
        "a": "https://mcp.datadoghq.com/v1/mcp",
        "b": "no (local only)",
        "name": "Hosted endpoint"
      },
      {
        "a": "Streamable HTTP, stdio",
        "b": "stdio",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "API key",
        "name": "Auth"
      },
      {
        "a": "Your plan",
        "b": "Your plan",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "MIT",
        "b": "none",
        "name": "Licence"
      },
      {
        "a": "none",
        "b": "30",
        "name": "Tools exposed"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "Read-only variant documented"
      },
      {
        "a": "no",
        "b": "no",
        "name": "llms.txt"
      },
      {
        "a": "2026-10-16",
        "b": "2026-11-17",
        "name": "Last release"
      },
      {
        "a": "no date given",
        "b": "2025-03-26",
        "name": "Terms last updated"
      },
      {
        "a": "no date given",
        "b": "2026-07-13",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not found in the text",
        "b": "yes",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "43 stars",
        "b": "none",
        "name": "Popularity"
      },
      {
        "a": "2.5/5 (2)",
        "b": "none",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "Datadog MCP Server scores 52.1 (D) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 5 of 7 scored categories.",
        "question": "Which is better for AI agents, Datadog MCP Server or Neat Pulse MCP?"
      },
      {
        "answer": "Datadog MCP Server takes an API key or an OAuth sign-in. Neat Pulse MCP needs an API key.",
        "question": "Do Datadog MCP Server and Neat Pulse MCP need an API key?"
      },
      {
        "answer": "Datadog MCP Server has a hosted endpoint at https://mcp.datadoghq.com/v1/mcp. Neat Pulse MCP runs on your own machine, with no hosted endpoint listed.",
        "question": "Can an agent call Datadog MCP Server and Neat Pulse MCP without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Schema \u0026 documentation, 60 against 49",
          "Agent ergonomics, 78 against 43",
          "Payments \u0026 pricing, 30 against 0",
          "Maintenance \u0026 community, 68 against 59",
          "Transparency \u0026 trust, 69 against 56"
        ],
        "also": [
          "A hosted endpoint, with nothing to install"
        ],
        "goodFor": "Agents that triage production issues across metrics, logs, traces and monitors in a Datadog org. sentry-mcp is narrower and deeper on errors, pagerduty-mcp covers on-call.",
        "slug": "datadog-mcp",
        "watchFor": "Tools and parameters are removed the day they're announced, most recently `lookback` on three RUM tools on 9 October 2026"
      },
      {
        "aheadOn": null,
        "also": [
          "No incidents deducted, where Datadog MCP Server loses 6 points for them"
        ],
        "goodFor": "IT administrators running Neat meeting-room devices on Pulse who want an agent to check fleet health, sensor readings and room set-up.",
        "slug": "neat-pulse-mcp",
        "watchFor": "Needs a paid Pulse Plus or Pro plan bought through a reseller, with no public price, no trial for MCP and no self-serve route for an agent"
      }
    ],
    "history": {
      "datadog-mcp": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 1.3,
          "from": 50.8,
          "fromGrade": "D",
          "to": 52.1,
          "toGrade": "D"
        },
        {
          "causes": [
            "evidence",
            "correction"
          ],
          "date": "2026-11-04",
          "delta": -6,
          "from": 56.8,
          "fromGrade": "C",
          "to": 50.8,
          "toGrade": "D"
        },
        {
          "causes": [
            "evidence"
          ],
          "date": "2026-10-28",
          "delta": 0.1,
          "from": 56.7,
          "fromGrade": "C",
          "to": 56.8,
          "toGrade": "C"
        }
      ],
      "neat-pulse-mcp": null
    },
    "job": {
      "capability": "observability.metrics",
      "name": "Metrics and monitoring"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/causely-vs-datadog-mcp.json",
        "title": "Causely MCP server vs Datadog MCP Server",
        "url": "https://www.anchorterminal.com/compare/causely-vs-datadog-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-datadog-mcp.json",
        "title": "Cronitor MCP server vs Datadog MCP Server",
        "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-datadog-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/datadog-mcp-vs-incident-io.json",
        "title": "Datadog MCP Server vs incident.io API",
        "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-incident-io"
      },
      {
        "json": "https://www.anchorterminal.com/compare/datadog-mcp-vs-pagerduty-mcp.json",
        "title": "Datadog MCP Server vs PagerDuty MCP Server",
        "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-pagerduty-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/datadog-mcp-vs-rootly-mcp.json",
        "title": "Datadog MCP Server vs Rootly MCP Server",
        "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-rootly-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/axiom-vs-neat-pulse-mcp.json",
        "title": "Axiom MCP Server vs Neat Pulse MCP",
        "url": "https://www.anchorterminal.com/compare/axiom-vs-neat-pulse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/better-stack-vs-neat-pulse-mcp.json",
        "title": "Better Stack vs Neat Pulse MCP",
        "url": "https://www.anchorterminal.com/compare/better-stack-vs-neat-pulse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/causely-vs-neat-pulse-mcp.json",
        "title": "Causely MCP server vs Neat Pulse MCP",
        "url": "https://www.anchorterminal.com/compare/causely-vs-neat-pulse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-neat-pulse-mcp.json",
        "title": "Cronitor MCP server vs Neat Pulse MCP",
        "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-neat-pulse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/datadog-mcp-vs-grafana-mcp-server.json",
        "title": "Datadog MCP Server vs Grafana MCP Server",
        "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-grafana-mcp-server"
      },
      {
        "json": "https://www.anchorterminal.com/compare/datadog-mcp-vs-honeycomb-mcp.json",
        "title": "Datadog MCP Server vs Honeycomb MCP",
        "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-honeycomb-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/datadog-mcp-vs-new-relic.json",
        "title": "Datadog MCP Server vs New Relic MCP Server",
        "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-new-relic"
      },
      {
        "json": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-neat-pulse-mcp.json",
        "title": "Grafana MCP Server vs Neat Pulse MCP",
        "url": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-neat-pulse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/honeycomb-mcp-vs-neat-pulse-mcp.json",
        "title": "Honeycomb MCP vs Neat Pulse MCP",
        "url": "https://www.anchorterminal.com/compare/honeycomb-mcp-vs-neat-pulse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-new-relic.json",
        "title": "Neat Pulse MCP vs New Relic MCP Server",
        "url": "https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-new-relic"
      },
      {
        "json": "https://www.anchorterminal.com/compare/axiom-vs-datadog-mcp.json",
        "title": "Axiom MCP Server vs Datadog MCP Server",
        "url": "https://www.anchorterminal.com/compare/axiom-vs-datadog-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/better-stack-vs-datadog-mcp.json",
        "title": "Better Stack vs Datadog MCP Server",
        "url": "https://www.anchorterminal.com/compare/better-stack-vs-datadog-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/datadog-mcp-vs-sentry-mcp.json",
        "title": "Datadog MCP Server vs Sentry MCP",
        "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-sentry-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-sentry-mcp.json",
        "title": "Neat Pulse MCP vs Sentry MCP",
        "url": "https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-sentry-mcp"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 2,
        "datadog-mcp": 33,
        "edge": "neat-pulse-mcp",
        "key": "reliability",
        "name": "Reliability",
        "neat-pulse-mcp": 35,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 11,
        "datadog-mcp": 60,
        "edge": "datadog-mcp",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "neat-pulse-mcp": 49,
        "weight": 13
      },
      {
        "by": 35,
        "datadog-mcp": 78,
        "edge": "datadog-mcp",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "neat-pulse-mcp": 43,
        "weight": 13
      },
      {
        "by": 3,
        "datadog-mcp": 76,
        "edge": "neat-pulse-mcp",
        "key": "security",
        "name": "Security \u0026 auth",
        "neat-pulse-mcp": 79,
        "weight": 14
      },
      {
        "by": 30,
        "datadog-mcp": 30,
        "edge": "datadog-mcp",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "neat-pulse-mcp": 0,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 9,
        "datadog-mcp": 68,
        "edge": "datadog-mcp",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "neat-pulse-mcp": 59,
        "weight": 7
      },
      {
        "by": 13,
        "datadog-mcp": 69,
        "edge": "datadog-mcp",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "neat-pulse-mcp": 56,
        "weight": 7
      }
    ],
    "summary": "Datadog MCP Server scores 52.1 (D) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 5 of 7 scored categories. Both do metrics and monitoring.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "datadog-mcp": "OAuth read-only grants, `mcp_read` and `mcp_write` permissions and an organisation-level block on MCP writes. Tools and parameters are removed the day they're announced, and a write-protection gap fixed on 22 September 2026 got no security advisory.",
      "neat-pulse-mcp": "Agents get 30 documented tools for a Neat device fleet, behind a revocable Pulse API token that can be read-only, with every action written to Pulse's audit log. It needs a paid Pulse plan bought through a reseller, prices aren't public, and there is no public source, changelog or status page."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/datadog-mcp-vs-neat-pulse-mcp",
    "json": "https://www.anchorterminal.com/compare/datadog-mcp-vs-neat-pulse-mcp.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/datadog-mcp-vs-neat-pulse-mcp.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/datadog-mcp-vs-neat-pulse-mcp.min.md"
  },
  "markdown": "Datadog MCP Server scores 52.1 (D) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 5 of 7 scored categories. Both do metrics and monitoring.\n\n- Datadog MCP Server: grade D, 52.1/100, rank #1096 of 1557. Markdown https://www.anchorterminal.com/tools/datadog-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/datadog-mcp.json\n- Neat Pulse MCP: grade E, 45.8/100, rank #1268 of 1557. Markdown https://www.anchorterminal.com/tools/neat-pulse-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/neat-pulse-mcp.json\n- Best observability and incident tools for AI agents: https://www.anchorterminal.com/best/observability/index.md\n- All 68 observability comparisons: https://www.anchorterminal.com/compare/observability/index.md\n\n## Which one, for what\n\n### Datadog MCP Server (D)\n\nGood for: Agents that triage production issues across metrics, logs, traces and monitors in a Datadog org. sentry-mcp is narrower and deeper on errors, pagerduty-mcp covers on-call.\n\nAhead on:\n- Schema \u0026 documentation, 60 against 49\n- Agent ergonomics, 78 against 43\n- Payments \u0026 pricing, 30 against 0\n- Maintenance \u0026 community, 68 against 59\n- Transparency \u0026 trust, 69 against 56\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: Tools and parameters are removed the day they're announced, most recently `lookback` on three RUM tools on 9 October 2026\n\n### Neat Pulse MCP (E)\n\nGood for: IT administrators running Neat meeting-room devices on Pulse who want an agent to check fleet health, sensor readings and room set-up.\n\nAlso in its favour:\n- No incidents deducted, where Datadog MCP Server loses 6 points for them\n\nWatch for: Needs a paid Pulse Plus or Pro plan bought through a reseller, with no public price, no trial for MCP and no self-serve route for an agent\n\n\n## Why the edge\n\n### Agent ergonomics: Datadog MCP Server +35\n\n- Datadog MCP Server (78): More than 30 toolsets chosen with the `toolsets` parameter, `omit_tools` per the 30 September check, `whoami` and `toolsets` resources, and a core set trimmed by about 15 per cent in March. An `execute_code` toolset runs sandboxed TypeScript against the APIs instead of one tool per call. We couldn't count the default tools (20). `limit`, cursors, `custom_attributes`, token budgets and flattening on aggregates, and `exclude_fields` on Kubernetes manifests (19). The changelog shows a steady effort on actionable errors (15). OAuth read-only grants omit write tools, an org setting blocks MCP writes, and read-only calls retry automatically. The 13 October entry says `execute_code` is now marked read-only so that clients asking approval for write-capable tools classify it correctly, but no entry names readOnlyHint or destructiveHint, so the annotation credit isn't added (12). Official Datadog API clients in several languages and Python agent examples in the repository (12).\n- Neat Pulse MCP (43): 30 tools, in the 11 to 30 band, with no toolsets or read-only subset that hides write tools that we found (15). `list_audit_logs` pages between dates, but `list_devices` and `list_rooms` return everything in the organisation (6). Documented 401 and 404 causes, and `move_device` returns a status asking for confirmation instead of failing (10). Annotations couldn't be read. The docs ask the assistant to confirm reboots and messages, and no idempotency is described (5). Two environment variables to start. The Pulse API reference shows generated client snippets, but no official SDK package was found (7). 15 + 6 + 10 + 5 + 7 = 43.\n\n### Payments \u0026 pricing: Datadog MCP Server +30\n\n- Datadog MCP Server (30): No x402, MPP or L402 (0). Datadog plan prices are public and the MCP quota of 100,000 calls a month per organisation is published, but there's no MCP price or per-call rate (10). A free Datadog plan exists per the 30 September check, and nothing we read says whether it includes MCP, so half (10). A person signs up and authorises OAuth or creates keys (0). Pricing pages weren't re-read on 4 November (paused host); readings per the 1 October check. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.\n- Neat Pulse MCP (0): No payment protocol (0). Pulse Plus and Pro are sold through resellers and the Pulse Agreement says the price is on the reseller's invoice, so no price is public (0). The free Starter plan excludes MCP and API access (0). A person must buy a plan and an Owner must create the token in the portal (0). 0 + 0 + 0 + 0 = 0.\n\n### Transparency \u0026 trust: Datadog MCP Server +13\n\n- Datadog MCP Server (69): The hosted server is closed with published terms, and the examples repository is MIT (18). Privacy policy, DPA and a trust centre exist, but we found nothing MCP-specific on what the server logs or keeps (18). The changelog labels breaking changes and deprecations, for example `get_datadog_spreadsheet_table_data` deprecated on 20 July, but removals ship the day they're announced, and nothing says whether the old /api/unstable/ URL still works (8). Since 1 October one removal had notice. `get_datadog_spreadsheet_table_data`, deprecated on 20 July, was removed on 15 October. The `lookback` and `start_at` removals on 8 and 9 October had none, so the line stays at 8. Datadog sites per region are documented. The subprocessor list sits behind the trust centre's request form (12).\n- Neat Pulse MCP (56): Closed source, and the npm package carries no licence field. The Pulse Agreement covers the service clearly (12). A privacy notice of 13 July 2026, a DPA, a GDPR page and a data residency article, with retention described only as long as necessary (18). The Pulse Agreement supports the current and prior major release, and nothing covers the MCP server's deprecation (3). Pulse data stays in one Azure region per chosen zone, mapped by name. No subprocessor list was read (14). 12 + 18 + 3 + 14 = 47.\n\n### Schema \u0026 documentation: Datadog MCP Server +11\n\n- Datadog MCP Server (60): Tool schemas are only visible through tools/list with an account. The changelog shows typed parameters, for example `limit` 1 to 1,000 and percentile enums, so we gave partial credit for a contract we couldn't read (15). We couldn't check docs.datadoghq.com/llms.txt because our fetch proxy refused it, and the listing doesn't record one (0). Changelog entries show descriptions being corrected, such as `search_pr_insights` now explaining that `expected` means pending (10). Ranges, cursors, enums and attribute selectors per the changelog (11). Errors are being made actionable, with reversed time windows rejected up front and an explicit `result_too_large` failure (9). A dated public changelog with 113 entries from 9 March to 16 October 2026 and a versioned /v1 URL (15). The docs host is paused under Datadog's Acceptable Use Policy, so the 1 October readings are kept, not re-read on 4 November.\n- Neat Pulse MCP (49): The npm metadata lists zod and the MCP SDK, but the tool schemas themselves weren't read, since the source isn't public and the package wasn't installed. Partial credit for a contract that exists but isn't published, as for Causely (12). No llms.txt found. The README points agents to an `llms-install.md` in the package, which wasn't read (5). The support reference describes every tool, what it returns and which changes can't be undone, and the domain guide explains the data model (14). Inputs are described only in passing, such as `assign_room_profile` (5). Example prompts, a troubleshooting table for 401, 404 and npx errors, and the `profile_confirmation_needed` status (8). Semver versions on npm and dated support articles, but no changelog (5). 12 + 5 + 14 + 5 + 8 + 5 = 49.\n\n### Maintenance \u0026 community: Datadog MCP Server +9\n\n- Datadog MCP Server (68): Latest changelog entry 16 October 2026, 19 days before this check (30). 35 dated entries from 6 August to 16 October (20). Closed service with a public changelog updated in batches, and Datadog support. Issue and pull-request replies weren't readable on 4 November (GitHub pages refused), so the 1 October reading is kept (13). Not in the official MCP registry per the 1 October check, not re-read (0). Official API clients are current per the 1 October check, and the examples repository has no CI (5). 30+20+13+0+5 = 68.\n- Neat Pulse MCP (59): 1.1.0 on 17 November 2026 (30). 0.2.2, 0.2.3, 1.0.0 and 1.1.0 since 17 September 2026 (20). Closed source with no public changelog. Paid plans include priority email support with an SLA per the Pulse Agreement, and the setup guide was updated on 17 November (5). Not in the official MCP registry, by a search for Neat (0). Current MCP SDK and zod versions in the npm metadata, with no visible CI (4). 30 + 20 + 5 + 0 + 4 = 59.\n\n## Score by category\n\n| Category | Weight | Datadog MCP Server | Neat Pulse MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 33 | 35 | Neat Pulse MCP +2 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 60 | 49 | Datadog MCP Server +11 |\n| Agent ergonomics | 13% | 78 | 43 | Datadog MCP Server +35 |\n| Security \u0026 auth | 14% | 76 | 79 | Neat Pulse MCP +3 |\n| Payments \u0026 pricing | 10% | 30 | 0 | Datadog MCP Server +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 68 | 59 | Datadog MCP Server +9 |\n| Transparency \u0026 trust | 7% | 69 | 56 | Datadog MCP Server +13 |\n| Negative events | ≤15 | -6 | 0 | |\n| **Total** | | **52.1 · D** | **45.8 · E** | |\n\n## Facts side by side\n\n| Fact | Datadog MCP Server | Neat Pulse MCP |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Datadog | Neat |\n| Hosted endpoint | `https://mcp.datadoghq.com/v1/mcp` | no (local only) |\n| Transports | Streamable HTTP, stdio | stdio |\n| Auth | OAuth or key | API key |\n| Pricing | Your plan | Your plan |\n| x402 | no | no |\n| Licence | MIT | none |\n| Tools exposed | none | 30 |\n| Read-only variant documented | yes | yes |\n| llms.txt | no | no |\n| Last release | 2026-10-16 | 2026-11-17 |\n| Terms last updated | no date given | 2025-03-26 |\n| Privacy policy last updated | no date given | 2026-07-13 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Popularity | 43 stars | none |\n| Agent reviews | 2.5/5 (2) | none |\n\n## How the scores have moved\n\n### Datadog MCP Server\n\n- +1.3 on 13 November 2026: checklist\n- -6.0 on 4 November 2026 (C to D): new evidence, correction\n- +0.1 on 28 October 2026: new evidence\n\n### Neat Pulse MCP\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Datadog MCP Server.** OAuth read-only grants, `mcp_read` and `mcp_write` permissions and an organisation-level block on MCP writes. Tools and parameters are removed the day they're announced, and a write-protection gap fixed on 22 September 2026 got no security advisory.\n\n**Neat Pulse MCP.** Agents get 30 documented tools for a Neat device fleet, behind a revocable Pulse API token that can be read-only, with every action written to Pulse's audit log. It needs a paid Pulse plan bought through a reseller, prices aren't public, and there is no public source, changelog or status page.\n\n## Before you call either\n\n### Datadog MCP Server\n\n1. Use https://mcp.datadoghq.com/v1/mcp. The /api/unstable/ path in older configs is no longer the documented one\n2. Set `toolsets` to the two or three you need, for example core plus logs, and read the `toolsets` resource first\n3. Pass `limit` and `custom_attributes` on span searches and page with `cursor`. `start_at` is gone from spans and RUM events\n4. Pass `from` and `to` to the RUM operation tools. `lookback` was removed on 9 October 2026\n5. Budget calls. The org shares 100,000 a month and 50 per 10 seconds\n\n### Neat Pulse MCP\n\n1. Ask the person to confirm before `delete_room`, `delete_device`, `reboot_device` or `reset_enrolment_code`. Deleting a room unenrols all its devices\n2. Ask the person before `send_message_to_device` or `send_message_to_room`, because the message shows on screens in the room\n3. Call `get_domain_guide` first if the client doesn't read MCP resources, to learn the region, location, room and device hierarchy\n4. If `move_device` returns `profile_confirmation_needed`, ask whether to apply the room's profile, then repeat the call with `assign_room_profile`\n5. If a call returns 401, ask the person for a new Pulse token. If it returns 404, check `PULSE_ORG_ID`\n\n## Questions\n\n### Which is better for AI agents, Datadog MCP Server or Neat Pulse MCP?\n\nDatadog MCP Server scores 52.1 (D) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 5 of 7 scored categories.\n\n### Do Datadog MCP Server and Neat Pulse MCP need an API key?\n\nDatadog MCP Server takes an API key or an OAuth sign-in. Neat Pulse MCP needs an API key.\n\n### Can an agent call Datadog MCP Server and Neat Pulse MCP without installing anything?\n\nDatadog MCP Server has a hosted endpoint at https://mcp.datadoghq.com/v1/mcp. Neat Pulse MCP runs on your own machine, with no hosted endpoint listed.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/datadog-mcp-vs-neat-pulse-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/datadog-mcp-vs-neat-pulse-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"datadog-mcp\", \"b\": \"neat-pulse-mcp\"}`. From a terminal: `anchor compare datadog-mcp neat-pulse-mcp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/datadog-mcp.json and https://www.anchorterminal.com/api/v1/tools/neat-pulse-mcp.json\n\n## Other comparisons with Datadog MCP Server or Neat Pulse MCP\n\n- [Causely MCP server vs Datadog MCP Server](https://www.anchorterminal.com/compare/causely-vs-datadog-mcp.md)\n- [Cronitor MCP server vs Datadog MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-datadog-mcp.md)\n- [Datadog MCP Server vs incident.io API](https://www.anchorterminal.com/compare/datadog-mcp-vs-incident-io.md)\n- [Datadog MCP Server vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/datadog-mcp-vs-pagerduty-mcp.md)\n- [Datadog MCP Server vs Rootly MCP Server](https://www.anchorterminal.com/compare/datadog-mcp-vs-rootly-mcp.md)\n- [Axiom MCP Server vs Neat Pulse MCP](https://www.anchorterminal.com/compare/axiom-vs-neat-pulse-mcp.md)\n- [Better Stack vs Neat Pulse MCP](https://www.anchorterminal.com/compare/better-stack-vs-neat-pulse-mcp.md)\n- [Causely MCP server vs Neat Pulse MCP](https://www.anchorterminal.com/compare/causely-vs-neat-pulse-mcp.md)\n- [Cronitor MCP server vs Neat Pulse MCP](https://www.anchorterminal.com/compare/cronitor-mcp-vs-neat-pulse-mcp.md)\n- [Datadog MCP Server vs Grafana MCP Server](https://www.anchorterminal.com/compare/datadog-mcp-vs-grafana-mcp-server.md)\n- [Datadog MCP Server vs Honeycomb MCP](https://www.anchorterminal.com/compare/datadog-mcp-vs-honeycomb-mcp.md)\n- [Datadog MCP Server vs New Relic MCP Server](https://www.anchorterminal.com/compare/datadog-mcp-vs-new-relic.md)\n- [Grafana MCP Server vs Neat Pulse MCP](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-neat-pulse-mcp.md)\n- [Honeycomb MCP vs Neat Pulse MCP](https://www.anchorterminal.com/compare/honeycomb-mcp-vs-neat-pulse-mcp.md)\n- [Neat Pulse MCP vs New Relic MCP Server](https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-new-relic.md)\n- [Axiom MCP Server vs Datadog MCP Server](https://www.anchorterminal.com/compare/axiom-vs-datadog-mcp.md)\n- [Better Stack vs Datadog MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-datadog-mcp.md)\n- [Datadog MCP Server vs Sentry MCP](https://www.anchorterminal.com/compare/datadog-mcp-vs-sentry-mcp.md)\n- [Neat Pulse MCP vs Sentry MCP](https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-sentry-mcp.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-18",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "1.0",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "Datadog MCP Server vs Neat Pulse MCP",
        "url": ""
      }
    ],
    "description": "Datadog scores 52.1 (D) to Neat Pulse MCP's 45.8 (E) for metrics and monitoring. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Datadog MCP Server D 52.1",
      "Neat Pulse MCP E 45.8",
      "scores"
    ],
    "h1": "Datadog MCP Server vs Neat Pulse MCP",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/datadog-mcp-vs-neat-pulse-mcp",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Datadog vs Neat Pulse MCP for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-neat-pulse-mcp"
  },
  "tokens": {
    "markdown": 4200,
    "slim": 930
  },
  "version": 1
}
