{
  "data": {
    "a": {
      "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"
    },
    "answer": "New Relic MCP Server scores 62.9 (B) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 6 of 7 scored categories.",
    "b": {
      "slug": "new-relic",
      "name": "New Relic MCP Server",
      "vendor": "New Relic, Inc.",
      "vendorUrl": "https://newrelic.com",
      "company": "newrelic.com",
      "kind": "mcp",
      "category": "observability",
      "summary": "New Relic's hosted MCP server at mcp.newrelic.com gives AI agents read access to an account's entities, NRQL data, alerts, issues, logs, errors, traces and deployments, with OAuth or a user API key, on top of the NerdGraph API.",
      "url": "https://www.anchorterminal.com/tools/new-relic",
      "markdownUrl": "https://www.anchorterminal.com/tools/new-relic.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/new-relic.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/new-relic.json",
      "dns": "new-relic.grade.anchorterminal.com",
      "repo": "https://github.com/newrelic/nr-skills-hub",
      "transports": [
        "streamable-http"
      ],
      "remoteUrl": "https://mcp.newrelic.com/mcp/",
      "packages": [],
      "auth": "oauth",
      "authNotes": "OAuth 2.0 (recommended) with scopes `observability:read`, `offline` and `offline_access`; access tokens expire after 5 minutes and are refreshed, with sign-in again after 24 hours. Or a user API key (`NRAK-...`) in an `api-key` header, which the docs say only works where stated and excludes the AI analysis, gap and preview tools. An administrator must leave the MCP toggles on in feature control manager and the user needs an organisation-scoped read role. EU and JP accounts use mcp.eu.newrelic.com and mcp.jp.newrelic.com.",
      "pricing": "freemium",
      "pricingNotes": "MCP is available on every New Relic account, including the free tier (100 GB of ingest a month, one full platform user, no card). Most tools are metered as Core Compute Units against the account's allocation and four AI analysis tools as Advanced Compute Units; no per-call price is published. Data beyond 100 GB costs $0.40 per GB; user and edition prices are quoted on request (https://newrelic.com/pricing).",
      "priceSummary": "$0.40 / GB",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the MCP docs, pricing page or terms (checked 2026-11-03). MCP calls are metered as compute units on the account's bill.",
        "endpoints": []
      },
      "toolCount": 40,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-03"
      },
      "docsUrl": "https://docs.newrelic.com/docs/agentic-ai/mcp/overview/",
      "llmsTxt": "https://docs.newrelic.com/llms.txt",
      "registryName": "com.newrelic/mcp-server",
      "capabilities": [
        "observability.metrics",
        "observability.logs",
        "observability.errors",
        "observability.traces",
        "observability.incidents"
      ],
      "tags": [
        "hosted",
        "freemium",
        "free-tier",
        "no-card",
        "mcp",
        "remote-mcp",
        "mcp-registry",
        "oauth",
        "read-only-mode",
        "llms-txt",
        "status-page",
        "security-txt",
        "bug-bounty",
        "soc2",
        "eu-region",
        "closed-source"
      ],
      "lastRelease": "2026-10-28",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 62.9,
        "grade": "B",
        "agentReady": false,
        "rank": 657,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 5,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 59,
          "maintenance": 80,
          "payments": 45,
          "reliability": 60,
          "schema": 51,
          "security": 76,
          "transparency": 81
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-03"
        },
        "negative": 0,
        "verdict": "OAuth with a read scope, 5-minute access tokens, role-bound calls and a queryable audit trail make this a safe read surface over an account's data, and the free tier includes it. 40 tools need tag filtering, the schemas aren't public, there is no per-call price, and no dated GA notice was found.",
        "bestFor": "Agents investigating incidents, errors, deployments and performance in an existing New Relic account, where reads are enough.",
        "strengths": [
          "OAuth 2.0 with `observability:read`, access tokens that expire after 5 minutes, revocation by user or organisation toggle, and every call bound to the user's roles",
          "`include-tags` header limits the 40 tools to the groups a task needs, such as `discovery,alerting`",
          "Sign-ins and NRQL sent through the server are queryable in NrAuditEvent and NrdbQuery with a product label",
          "Available on the free tier (100 GB a month, no card) and rate-limited at a published 2,000 tool calls an hour per user",
          "llms.txt and Markdown twins of every docs page, a dated what's-new feed and a verified registry namespace"
        ],
        "weaknesses": [
          "Tool input schemas are visible only through an authenticated session; the docs give one-line descriptions and no parameters",
          "40 tools in the default list, above the 30-tool line, unless the client sends `include-tags`",
          "No per-call price; tools are metered as Core and Advanced Compute Units on the account's bill",
          "Public preview since 4 November 2025 with no dated general availability notice found, and preview tools mixed into the list",
          "Logs, errors and traces come back as untrusted text with no prompt-injection guidance; the trust centre renders through a script our reader can't run"
        ],
        "agentNotes": [
          "Connect with OAuth; an `api-key` header reaches only the core tools and the docs say the API key route works only where stated",
          "Send `include-tags` with the groups the task needs (for example `discovery,data-access`) to keep the tool list under 30",
          "Call `list_available_new_relic_accounts` first and pass the account id to every query; `convert_time_period_to_epoch_ms` turns phrases such as last 30 minutes into the epoch bounds the other tools take",
          "Stay under 2,000 tool calls an hour per user and 25 concurrent NerdGraph requests; a 429 clears as in-flight requests finish",
          "Ask the organisation administrator to turn on the Preview Tools, API Keys, Atlassian or AWS toggles in feature control manager before relying on those tools; they are off by default"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 62.9
          }
        ],
        "editorialScores": {
          "ergonomics": 59,
          "maintenance": 80,
          "payments": 45,
          "reliability": 60,
          "schema": 51,
          "security": 76,
          "transparency": 63
        },
        "provenanceScore": 98,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-03",
            "maintenance": "2026-11-03",
            "payments": "2026-11-03",
            "reliability": "2026-11-03",
            "schema": "2026-11-03",
            "security": "2026-11-03",
            "transparency": "2026-11-03"
          },
          "last": "2026-11-03",
          "lastMoved": "2026-11-13",
          "oldest": "2026-11-03",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "claudeCode": "claude mcp add --transport http --scope user newrelic https://mcp.newrelic.com/mcp/",
        "config": {
          "mcpServers": {
            "newrelic": {
              "type": "http",
              "url": "https://mcp.newrelic.com/mcp/"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/observability.metrics",
        "tool": "https://letme.dev/new-relic"
      },
      "area": "developer",
      "unitPrices": [
        {
          "item": "Data ingest beyond 100 GB a month",
          "unit": "gb",
          "usd": 0.4,
          "note": "100 GB a month free on every edition. User and compute prices are quoted on request"
        }
      ],
      "provenance": {
        "legalEntity": "New Relic, Inc.",
        "domain": "newrelic.com",
        "domainRegistered": "2006-04-19",
        "endpointOnVendorDomain": true,
        "terms": "https://newrelic.com/termsandconditions/paid",
        "privacy": "https://newrelic.com/termsandconditions/privacy",
        "statusPage": "https://status.newrelic.com",
        "changelog": "https://docs.newrelic.com/whats-new/",
        "securityTxt": "valid",
        "checked": "2026-11-03",
        "notes": [
          "The paid terms of service are dated 8 November 2022 and the unpaid terms 21 October 2021; the master cloud agreement path is disallowed by newrelic.com/robots.txt and wasn't read. The privacy notice is dated 14 September 2026.",
          "newrelic.com/robots.txt disallows /signup/, /lp/, the master cloud agreement and a few files; /security redirected to trust.newrelic.com, which renders through a script and was not readable. docs.newrelic.com allows everything.",
          "security.txt at newrelic.com/.well-known/security.txt points to HackerOne for contact and policy.",
          "status.newrelic.com is an Atlassian Statuspage with 115 components across US, EU and JP; the history page needs JavaScript, so the 90-day record was read from history.rss, which holds 25 incidents back to 12 January 2026.",
          "RDAP gives newrelic.com a registration date of 19 April 2006. firstReleased is 4 November 2025, the public preview date of the MCP server."
        ],
        "score": 98
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/new-relic.json",
      "live": {
        "slug": "new-relic",
        "probe": {
          "target": "https://mcp.newrelic.com/mcp/",
          "method": "mcp-initialize",
          "lastAt": "2026-11-18T23:13:36.942965949Z",
          "lastOk": true,
          "lastStatus": 401,
          "lastMs": 362,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 340,
          "p95ms24h": 466,
          "samples24h": 241,
          "samples30d": 3418,
          "days": [
            {
              "date": "2026-11-04",
              "probes": 87,
              "ok": 87
            },
            {
              "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-11-04T00:00:00Z"
        },
        "vendorStatus": {
          "page": "https://status.newrelic.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-11-18T23:13:36.947346216Z"
        },
        "versions": [
          {
            "registry": "mcp-registry",
            "name": "com.newrelic/mcp-server",
            "version": "0.1.0",
            "seenAt": "2026-11-18T22:45:57.054523297Z"
          }
        ],
        "githubStars": 7,
        "securityTxt": {
          "url": "https://newrelic.com/.well-known/security.txt",
          "state": "valid",
          "checkedAt": "2026-11-18T16:29:33.85857375Z"
        },
        "llmsTxt": {
          "url": "https://docs.newrelic.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-18T16:15:23.564162893Z"
        },
        "domain": {
          "domain": "newrelic.com",
          "registered": "2006-04-19",
          "source": "https://rdap.verisign.com/com/v1/domain/newrelic.com",
          "checkedAt": "2026-11-15T15:25:09.428138872Z"
        },
        "pages": [
          {
            "url": "https://docs.newrelic.com/whats-new/",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-11-18T21:41:00.071717734Z",
            "changedAt": "2026-11-10T16:17:47.152833105Z",
            "fingerprint": "41175802039c"
          },
          {
            "url": "https://newrelic.com/pricing",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-11-18T21:49:08.519781313Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "5258cab1dd72"
          },
          {
            "url": "https://newrelic.com/termsandconditions/privacy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-11-18T21:49:12.571493123Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "e38b67a01617"
          },
          {
            "url": "https://newrelic.com/termsandconditions/paid",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-11-18T21:49:10.644617796Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "a692124e88f0"
          }
        ],
        "mcpTools": {
          "url": "https://mcp.newrelic.com/mcp/",
          "checkedAt": "2026-11-18T04:26:10.969019559Z",
          "status": "auth",
          "note": "asks for credentials before listing its tools",
          "changedAt": "2026-11-05T01:29:27.984114072Z"
        },
        "github": {
          "repo": "newrelic/nr-skills-hub",
          "checkedAt": "2026-11-16T11:27:12.232489737Z",
          "stars": 7,
          "archived": false,
          "issuesEnabled": true,
          "pushedAt": "2026-09-15T17:05:40Z",
          "openIssues": 0,
          "openPRs": 2,
          "issuesOpened90d": 0,
          "issuesClosed90d": 0,
          "prsMerged90d": 8
        },
        "updatedAt": "2026-11-18T23:13:36.942965949Z"
      },
      "streak": {
        "days": 14,
        "from": "2026-11-04",
        "sinceWatching": true,
        "best": 14
      }
    },
    "edges": [
      {
        "by": 45,
        "category": "payments",
        "leads": "new-relic",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "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.",
          "b": "No x402, MPP or L402 (0). The pricing page is public for the free tier and data ingest ($0.40 per GB beyond 100 GB), but MCP tools are metered as compute units with no per-call rate, and user and edition prices are quoted on request (10). The free tier includes MCP, 100 GB a month and one full platform user with no card (20). A person signs up in a browser and completes the OAuth flow (0). 0 + 10 + 20 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45."
        },
        "scores": {
          "a": 0,
          "b": 45
        }
      },
      {
        "by": 25,
        "category": "reliability",
        "leads": "new-relic",
        "name": "Reliability",
        "reasons": {
          "a": "Read with the local-software lines, since the server is an npm package the client starts on the person's machine. Official npm package with Node.js 20 or later stated (20). No public repository, so no CI or test suite could be seen (0). No public issue tracker (0). Versions follow semver on npm, but no changelog was found (0). Version 1.1.0 and generally available since 18 November 2026 (15). The Pulse cloud API it relays to has no status page linked from the pages read. 20 + 0 + 0 + 0 + 15 = 35.",
          "b": "Scored as a hosted MCP server. status.newrelic.com is an Atlassian Statuspage with 115 components across the US, EU and JP regions and no MCP component (20). history.rss holds seven incidents in the 90 days to 3 November 2026, among them delayed queries and alerts in the US for 49 minutes on 2 November, synthetics ping delays the same day, the JP entity platform unavailable for 67 minutes on 28 October, delayed US data and alerts from 19:24 to 22:04 UTC on 25 September, intermittent UI errors for two and a half hours the same night, a Salesforce support outage on 16 September and a 10-minute EU metric issue. Two regional incidents over an hour on the query and alert paths the server depends on, so one major (10). Published numbers, 2,000 tool calls an hour per user on the MCP server and 25 concurrent NerdGraph requests per user (15). NerdGraph answers 429 on concurrency with guidance to batch or pool, but no Retry-After is documented and nothing covers retries of MCP calls; the tools are reads, so idempotency doesn't arise (8). The pricing page lists support response SLAs, and the paid terms promise commercially reasonable efforts, so no availability SLA (0). Public preview on 4 November 2025, available to all accounts on 3 November 2026 with preview tools marked separately, but no dated GA notice was found (7). 20 + 10 + 15 + 8 + 0 + 7 = 60."
        },
        "scores": {
          "a": 35,
          "b": 60
        }
      },
      {
        "by": 25,
        "category": "transparency",
        "leads": "new-relic",
        "name": "Transparency \u0026 trust",
        "reasons": {
          "a": "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.",
          "b": "Closed service with clear dated terms (paid 8 November 2022, unpaid 21 October 2021) naming New Relic, Inc. (15). A privacy notice of 14 September 2026, a data retention page with per-namespace periods, a security policy, and the MCP docs' statement that gap-analysis responses aren't stored; the master cloud agreement and the trust centre couldn't be read (22). End-of-life notices with dates (REST API keys, 2025) and a pre-release policy that says preview services can change or end (16). US, EU and JP regions are documented for the server and the platform, but no sub-processor list was found on a readable page (10). 15 + 22 + 16 + 10 = 63."
        },
        "scores": {
          "a": 56,
          "b": 81
        }
      },
      {
        "by": 21,
        "category": "maintenance",
        "leads": "new-relic",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "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.",
          "b": "Read as a closed service. The what's-new feed and press releases record changes through October 2026, the latest on 28 October (Change Tracking in GitHub Copilot), and docs llms.txt was regenerated on 3 November (30). More than three dated entries in 90 days, among them the Ground Truth CLI on 6 October, the CEO appointment on 1 October, OpenTelemetry AI monitoring in August and the ISO 42001 announcement (20). A support portal, in-app support and a community forum; the skills hub repository on GitHub, whose issue replies couldn't be read (10 of 15). com.newrelic/mcp-server in the official registry since 28 October 2025 under a DNS-verified namespace, still at 0.1.0 (15). No package to assess for a hosted server; NerdGraph has official clients (5). 30 + 20 + 10 + 15 + 5 = 80."
        },
        "scores": {
          "a": 59,
          "b": 80
        }
      },
      {
        "by": 16,
        "category": "ergonomics",
        "leads": "new-relic",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "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.",
          "b": "40 tools in the default list, above the 30-tool line (5), with the `include-tags` header to load only named groups (add 10, so 15). Time windows on most tools, `convert_time_period_to_epoch_ms`, filters on incidents, errors and logs, and NRQL's own LIMIT and FACET; no documented page size (14). The troubleshooting page covers setup errors with fixes, and the docs say nothing about tool-level error bodies (8). Every tool is a read (query, list, fetch, analyse) and the gap tool reads files the client sends, so a retry is safe; no readOnlyHint or destructiveHint was confirmed because tools/list wasn't read (12). Natural-language prompts need no parameters from the user, and the API behind the server has official NerdGraph clients; nothing agent-specific beyond skills (10). 15 + 14 + 8 + 12 + 10 = 59."
        },
        "scores": {
          "a": 43,
          "b": 59
        }
      }
    ],
    "facts": [
      {
        "a": "MCP server",
        "b": "MCP server",
        "name": "Kind"
      },
      {
        "a": "Neat",
        "b": "New Relic, Inc.",
        "name": "Vendor"
      },
      {
        "a": "no (local only)",
        "b": "https://mcp.newrelic.com/mcp/",
        "name": "Hosted endpoint"
      },
      {
        "a": "stdio",
        "b": "Streamable HTTP",
        "name": "Transports"
      },
      {
        "a": "API key",
        "b": "OAuth",
        "name": "Auth"
      },
      {
        "a": "Your plan",
        "b": "Freemium",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "30",
        "b": "40",
        "name": "Tools exposed"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "Read-only variant documented"
      },
      {
        "a": "no",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "not listed",
        "b": "com.newrelic/mcp-server",
        "name": "MCP registry"
      },
      {
        "a": "2026-11-17",
        "b": "2026-10-28",
        "name": "Last release"
      },
      {
        "a": "2025-03-26",
        "b": "2022-11-08",
        "name": "Terms last updated"
      },
      {
        "a": "2026-07-13",
        "b": "2026-09-14",
        "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": "yes",
        "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": "yes",
        "b": "not found in the text",
        "name": "Arbitration or class-action waiver"
      }
    ],
    "faq": [
      {
        "answer": "New Relic MCP Server scores 62.9 (B) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 6 of 7 scored categories.",
        "question": "Which is better for AI agents, Neat Pulse MCP or New Relic MCP Server?"
      },
      {
        "answer": "Neat Pulse MCP needs an API key. New Relic MCP Server uses an OAuth sign-in.",
        "question": "Do Neat Pulse MCP and New Relic MCP Server need an API key?"
      },
      {
        "answer": "Neat Pulse MCP runs on your own machine, with no hosted endpoint listed. New Relic MCP Server has a hosted endpoint at https://mcp.newrelic.com/mcp/.",
        "question": "Can an agent call Neat Pulse MCP and New Relic MCP Server without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": null,
        "also": [
          "Runs on your own machine"
        ],
        "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"
      },
      {
        "aheadOn": [
          "Reliability, 60 against 35",
          "Agent ergonomics, 59 against 43",
          "Payments \u0026 pricing, 45 against 0",
          "Maintenance \u0026 community, 80 against 59",
          "Transparency \u0026 trust, 81 against 56"
        ],
        "also": [
          "A hosted endpoint, with nothing to install",
          "Free to start without a card"
        ],
        "goodFor": "Agents investigating incidents, errors, deployments and performance in an existing New Relic account, where reads are enough.",
        "slug": "new-relic",
        "watchFor": "Tool input schemas are visible only through an authenticated session; the docs give one-line descriptions and no parameters"
      }
    ],
    "history": {
      "neat-pulse-mcp": null,
      "new-relic": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 1.9,
          "from": 61,
          "fromGrade": "C",
          "to": 62.9,
          "toGrade": "B"
        }
      ]
    },
    "job": {
      "capability": "observability.metrics",
      "name": "Metrics and monitoring"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/causely-vs-new-relic.json",
        "title": "Causely MCP server vs New Relic MCP Server",
        "url": "https://www.anchorterminal.com/compare/causely-vs-new-relic"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-new-relic.json",
        "title": "Cronitor MCP server vs New Relic MCP Server",
        "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-new-relic"
      },
      {
        "json": "https://www.anchorterminal.com/compare/incident-io-vs-new-relic.json",
        "title": "incident.io API vs New Relic MCP Server",
        "url": "https://www.anchorterminal.com/compare/incident-io-vs-new-relic"
      },
      {
        "json": "https://www.anchorterminal.com/compare/new-relic-vs-pagerduty-mcp.json",
        "title": "New Relic MCP Server vs PagerDuty MCP Server",
        "url": "https://www.anchorterminal.com/compare/new-relic-vs-pagerduty-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/new-relic-vs-rootly-mcp.json",
        "title": "New Relic MCP Server vs Rootly MCP Server",
        "url": "https://www.anchorterminal.com/compare/new-relic-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-neat-pulse-mcp.json",
        "title": "Datadog MCP Server vs Neat Pulse MCP",
        "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-neat-pulse-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/grafana-mcp-server-vs-new-relic.json",
        "title": "Grafana MCP Server vs New Relic MCP Server",
        "url": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-new-relic"
      },
      {
        "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/axiom-vs-new-relic.json",
        "title": "Axiom MCP Server vs New Relic MCP Server",
        "url": "https://www.anchorterminal.com/compare/axiom-vs-new-relic"
      },
      {
        "json": "https://www.anchorterminal.com/compare/better-stack-vs-new-relic.json",
        "title": "Better Stack vs New Relic MCP Server",
        "url": "https://www.anchorterminal.com/compare/better-stack-vs-new-relic"
      },
      {
        "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"
      },
      {
        "json": "https://www.anchorterminal.com/compare/new-relic-vs-sentry-mcp.json",
        "title": "New Relic MCP Server vs Sentry MCP",
        "url": "https://www.anchorterminal.com/compare/new-relic-vs-sentry-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/honeycomb-mcp-vs-new-relic.json",
        "title": "Honeycomb MCP vs New Relic MCP Server",
        "url": "https://www.anchorterminal.com/compare/honeycomb-mcp-vs-new-relic"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 25,
        "edge": "new-relic",
        "key": "reliability",
        "name": "Reliability",
        "neat-pulse-mcp": 35,
        "new-relic": 60,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 2,
        "edge": "new-relic",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "neat-pulse-mcp": 49,
        "new-relic": 51,
        "weight": 13
      },
      {
        "by": 16,
        "edge": "new-relic",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "neat-pulse-mcp": 43,
        "new-relic": 59,
        "weight": 13
      },
      {
        "by": 3,
        "edge": "neat-pulse-mcp",
        "key": "security",
        "name": "Security \u0026 auth",
        "neat-pulse-mcp": 79,
        "new-relic": 76,
        "weight": 14
      },
      {
        "by": 45,
        "edge": "new-relic",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "neat-pulse-mcp": 0,
        "new-relic": 45,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 21,
        "edge": "new-relic",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "neat-pulse-mcp": 59,
        "new-relic": 80,
        "weight": 7
      },
      {
        "by": 25,
        "edge": "new-relic",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "neat-pulse-mcp": 56,
        "new-relic": 81,
        "weight": 7
      }
    ],
    "summary": "New Relic MCP Server scores 62.9 (B) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 6 of 7 scored categories. Both do metrics and monitoring.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "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.",
      "new-relic": "OAuth with a read scope, 5-minute access tokens, role-bound calls and a queryable audit trail make this a safe read surface over an account's data, and the free tier includes it. 40 tools need tag filtering, the schemas aren't public, there is no per-call price, and no dated GA notice was found."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-new-relic",
    "json": "https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-new-relic.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-new-relic.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-new-relic.min.md"
  },
  "markdown": "New Relic MCP Server scores 62.9 (B) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 6 of 7 scored categories. Both do metrics and monitoring.\n\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- New Relic MCP Server: grade B, 62.9/100, rank #657 of 1557. Markdown https://www.anchorterminal.com/tools/new-relic.md · JSON https://www.anchorterminal.com/api/v1/tools/new-relic.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### 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- Runs on your own machine\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### New Relic MCP Server (B)\n\nGood for: Agents investigating incidents, errors, deployments and performance in an existing New Relic account, where reads are enough.\n\nAhead on:\n- Reliability, 60 against 35\n- Agent ergonomics, 59 against 43\n- Payments \u0026 pricing, 45 against 0\n- Maintenance \u0026 community, 80 against 59\n- Transparency \u0026 trust, 81 against 56\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Free to start without a card\n\nWatch for: Tool input schemas are visible only through an authenticated session; the docs give one-line descriptions and no parameters\n\n\n## Why the edge\n\n### Payments \u0026 pricing: New Relic MCP Server +45\n\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- New Relic MCP Server (45): No x402, MPP or L402 (0). The pricing page is public for the free tier and data ingest ($0.40 per GB beyond 100 GB), but MCP tools are metered as compute units with no per-call rate, and user and edition prices are quoted on request (10). The free tier includes MCP, 100 GB a month and one full platform user with no card (20). A person signs up in a browser and completes the OAuth flow (0). 0 + 10 + 20 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.\n\n### Reliability: New Relic MCP Server +25\n\n- Neat Pulse MCP (35): Read with the local-software lines, since the server is an npm package the client starts on the person's machine. Official npm package with Node.js 20 or later stated (20). No public repository, so no CI or test suite could be seen (0). No public issue tracker (0). Versions follow semver on npm, but no changelog was found (0). Version 1.1.0 and generally available since 18 November 2026 (15). The Pulse cloud API it relays to has no status page linked from the pages read. 20 + 0 + 0 + 0 + 15 = 35.\n- New Relic MCP Server (60): Scored as a hosted MCP server. status.newrelic.com is an Atlassian Statuspage with 115 components across the US, EU and JP regions and no MCP component (20). history.rss holds seven incidents in the 90 days to 3 November 2026, among them delayed queries and alerts in the US for 49 minutes on 2 November, synthetics ping delays the same day, the JP entity platform unavailable for 67 minutes on 28 October, delayed US data and alerts from 19:24 to 22:04 UTC on 25 September, intermittent UI errors for two and a half hours the same night, a Salesforce support outage on 16 September and a 10-minute EU metric issue. Two regional incidents over an hour on the query and alert paths the server depends on, so one major (10). Published numbers, 2,000 tool calls an hour per user on the MCP server and 25 concurrent NerdGraph requests per user (15). NerdGraph answers 429 on concurrency with guidance to batch or pool, but no Retry-After is documented and nothing covers retries of MCP calls; the tools are reads, so idempotency doesn't arise (8). The pricing page lists support response SLAs, and the paid terms promise commercially reasonable efforts, so no availability SLA (0). Public preview on 4 November 2025, available to all accounts on 3 November 2026 with preview tools marked separately, but no dated GA notice was found (7). 20 + 10 + 15 + 8 + 0 + 7 = 60.\n\n### Transparency \u0026 trust: New Relic MCP Server +25\n\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- New Relic MCP Server (81): Closed service with clear dated terms (paid 8 November 2022, unpaid 21 October 2021) naming New Relic, Inc. (15). A privacy notice of 14 September 2026, a data retention page with per-namespace periods, a security policy, and the MCP docs' statement that gap-analysis responses aren't stored; the master cloud agreement and the trust centre couldn't be read (22). End-of-life notices with dates (REST API keys, 2025) and a pre-release policy that says preview services can change or end (16). US, EU and JP regions are documented for the server and the platform, but no sub-processor list was found on a readable page (10). 15 + 22 + 16 + 10 = 63.\n\n### Maintenance \u0026 community: New Relic MCP Server +21\n\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- New Relic MCP Server (80): Read as a closed service. The what's-new feed and press releases record changes through October 2026, the latest on 28 October (Change Tracking in GitHub Copilot), and docs llms.txt was regenerated on 3 November (30). More than three dated entries in 90 days, among them the Ground Truth CLI on 6 October, the CEO appointment on 1 October, OpenTelemetry AI monitoring in August and the ISO 42001 announcement (20). A support portal, in-app support and a community forum; the skills hub repository on GitHub, whose issue replies couldn't be read (10 of 15). com.newrelic/mcp-server in the official registry since 28 October 2025 under a DNS-verified namespace, still at 0.1.0 (15). No package to assess for a hosted server; NerdGraph has official clients (5). 30 + 20 + 10 + 15 + 5 = 80.\n\n### Agent ergonomics: New Relic MCP Server +16\n\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- New Relic MCP Server (59): 40 tools in the default list, above the 30-tool line (5), with the `include-tags` header to load only named groups (add 10, so 15). Time windows on most tools, `convert_time_period_to_epoch_ms`, filters on incidents, errors and logs, and NRQL's own LIMIT and FACET; no documented page size (14). The troubleshooting page covers setup errors with fixes, and the docs say nothing about tool-level error bodies (8). Every tool is a read (query, list, fetch, analyse) and the gap tool reads files the client sends, so a retry is safe; no readOnlyHint or destructiveHint was confirmed because tools/list wasn't read (12). Natural-language prompts need no parameters from the user, and the API behind the server has official NerdGraph clients; nothing agent-specific beyond skills (10). 15 + 14 + 8 + 12 + 10 = 59.\n\n## Score by category\n\n| Category | Weight | Neat Pulse MCP | New Relic MCP Server | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 35 | 60 | New Relic MCP Server +25 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 49 | 51 | New Relic MCP Server +2 |\n| Agent ergonomics | 13% | 43 | 59 | New Relic MCP Server +16 |\n| Security \u0026 auth | 14% | 79 | 76 | Neat Pulse MCP +3 |\n| Payments \u0026 pricing | 10% | 0 | 45 | New Relic MCP Server +45 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 59 | 80 | New Relic MCP Server +21 |\n| Transparency \u0026 trust | 7% | 56 | 81 | New Relic MCP Server +25 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **45.8 · E** | **62.9 · B** | |\n\n## Facts side by side\n\n| Fact | Neat Pulse MCP | New Relic MCP Server |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Neat | New Relic, Inc. |\n| Hosted endpoint | no (local only) | `https://mcp.newrelic.com/mcp/` |\n| Transports | stdio | Streamable HTTP |\n| Auth | API key | OAuth |\n| Pricing | Your plan | Freemium |\n| x402 | no | no |\n| Tools exposed | 30 | 40 |\n| Read-only variant documented | yes | yes |\n| llms.txt | no | yes |\n| MCP registry | not listed | `com.newrelic/mcp-server` |\n| Last release | 2026-11-17 | 2026-10-28 |\n| Terms last updated | 2025-03-26 | 2022-11-08 |\n| Privacy policy last updated | 2026-07-13 | 2026-09-14 |\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 | yes |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | yes | not found in the text |\n\n## How the scores have moved\n\n### Neat Pulse MCP\n\nNo score change since it was listed.\n\n### New Relic MCP Server\n\n- +1.9 on 13 November 2026 (C to B): checklist\n\n## Verdicts\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**New Relic MCP Server.** OAuth with a read scope, 5-minute access tokens, role-bound calls and a queryable audit trail make this a safe read surface over an account's data, and the free tier includes it. 40 tools need tag filtering, the schemas aren't public, there is no per-call price, and no dated GA notice was found.\n\n## Before you call either\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### New Relic MCP Server\n\n1. Connect with OAuth; an `api-key` header reaches only the core tools and the docs say the API key route works only where stated\n2. Send `include-tags` with the groups the task needs (for example `discovery,data-access`) to keep the tool list under 30\n3. Call `list_available_new_relic_accounts` first and pass the account id to every query; `convert_time_period_to_epoch_ms` turns phrases such as last 30 minutes into the epoch bounds the other tools take\n4. Stay under 2,000 tool calls an hour per user and 25 concurrent NerdGraph requests; a 429 clears as in-flight requests finish\n5. Ask the organisation administrator to turn on the Preview Tools, API Keys, Atlassian or AWS toggles in feature control manager before relying on those tools; they are off by default\n\n## Questions\n\n### Which is better for AI agents, Neat Pulse MCP or New Relic MCP Server?\n\nNew Relic MCP Server scores 62.9 (B) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 6 of 7 scored categories.\n\n### Do Neat Pulse MCP and New Relic MCP Server need an API key?\n\nNeat Pulse MCP needs an API key. New Relic MCP Server uses an OAuth sign-in.\n\n### Can an agent call Neat Pulse MCP and New Relic MCP Server without installing anything?\n\nNeat Pulse MCP runs on your own machine, with no hosted endpoint listed. New Relic MCP Server has a hosted endpoint at https://mcp.newrelic.com/mcp/.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-new-relic.json, and with the fewest tokens: https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-new-relic.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"neat-pulse-mcp\", \"b\": \"new-relic\"}`. From a terminal: `anchor compare neat-pulse-mcp new-relic`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/neat-pulse-mcp.json and https://www.anchorterminal.com/api/v1/tools/new-relic.json\n\n## Other comparisons with Neat Pulse MCP or New Relic MCP Server\n\n- [Causely MCP server vs New Relic MCP Server](https://www.anchorterminal.com/compare/causely-vs-new-relic.md)\n- [Cronitor MCP server vs New Relic MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-new-relic.md)\n- [incident.io API vs New Relic MCP Server](https://www.anchorterminal.com/compare/incident-io-vs-new-relic.md)\n- [New Relic MCP Server vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/new-relic-vs-pagerduty-mcp.md)\n- [New Relic MCP Server vs Rootly MCP Server](https://www.anchorterminal.com/compare/new-relic-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 Neat Pulse MCP](https://www.anchorterminal.com/compare/datadog-mcp-vs-neat-pulse-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- [Grafana MCP Server vs New Relic MCP Server](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-new-relic.md)\n- [Honeycomb MCP vs Neat Pulse MCP](https://www.anchorterminal.com/compare/honeycomb-mcp-vs-neat-pulse-mcp.md)\n- [Axiom MCP Server vs New Relic MCP Server](https://www.anchorterminal.com/compare/axiom-vs-new-relic.md)\n- [Better Stack vs New Relic MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-new-relic.md)\n- [Neat Pulse MCP vs Sentry MCP](https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-sentry-mcp.md)\n- [New Relic MCP Server vs Sentry MCP](https://www.anchorterminal.com/compare/new-relic-vs-sentry-mcp.md)\n- [Honeycomb MCP vs New Relic MCP Server](https://www.anchorterminal.com/compare/honeycomb-mcp-vs-new-relic.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": "Neat Pulse MCP vs New Relic MCP Server",
        "url": ""
      }
    ],
    "description": "New Relic scores 62.9 (B) to Neat Pulse MCP's 45.8 (E) for metrics and monitoring. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Neat Pulse MCP E 45.8",
      "New Relic MCP Server B 62.9",
      "scores"
    ],
    "h1": "Neat Pulse MCP vs New Relic MCP Server",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/neat-pulse-mcp-vs-new-relic",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Neat Pulse MCP vs New Relic for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-new-relic"
  },
  "tokens": {
    "markdown": 4250,
    "slim": 930
  },
  "version": 1
}
