---
title: "New Relic: the 360 agent-readiness check | Agent MCP Directory"
description: "New Relic on Ora's agent-readiness scan, read 2026-11-09: 75 of 100, grade B, with the MCP, API and OAuth surfaces an agent can call."
canonical: https://agentmcpdirectory.com/blog/newrelic-agent-readiness
site: "Agent MCP Directory"
last_updated: 2026-11-09
date: 2026-11-09
section: "360 checks"
---

# New Relic: the 360 agent-readiness check | Agent MCP Directory

> New Relic on Ora's agent-readiness scan, read 2026-11-09: 75 of 100, grade B, with the MCP, API and OAuth surfaces an agent can call.

Source: https://agentmcpdirectory.com/blog/newrelic-agent-readiness
Site: Agent MCP Directory
Last reviewed: 2026-11-09

# New Relic: the 360 agent-readiness check

New Relic scores 75 of 100 on Ora's agent-readiness scan, a B, read 9 November 2026. Of the five surfaces an agent acts on, Ora found 3: a public API, OAuth, a command line. Three act-layer rows behind a shield, and a home page with no H1.

On 9 November 2026 the public site at newrelic.com scored 75 of 100 on [Ora's](https://ora.ai/?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=check) agent-readiness scan, a B, in Ora's Infrastructure category. Ora probes a site the way an agent would: it requests pages with the agents' own user agents, reads robots.txt, looks for the files agents read, and tries the API, MCP and payment surfaces. This check reads the act layer first, because that is what the directory records, then the door, what an agent can read, and whether the company is found and recommended. Ora's one-line summary: New Relic offers strong discovery and SDK access, but lacks WebMCP support and Idempotency-Key handling for agents.

## The score

| Layer | Asks | Points | Share |
| --- | --- | --- | --- |
| Usability | Can agents use it | 43 of 65 | 66% |
| Access | Can agents read it | 42 of 51 | 82% |
| Discovery | Can agents find and recommend it | 13 of 16 | 81% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade B | 75 of 100 | 75% |

## What an agent can do

The surfaces an agent acts on: an API it can find and call, an MCP server, an agent card, OAuth metadata, a command line. This is the layer the directory records, so it comes first. 3 checks in this group do not apply to this site and are left out.

In the directory, New Relic sign-in required, tools not seen, not counted; the connector run of 4 November 2026 is on [the entry page](https://agentmcpdirectory.com/directory/newrelic-com/). Ora's MCP server check for the same domain reads partial; the two look for different things, the directory for a server that answers a handshake and lists tools, Ora for a server it can find from the site.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| MCP server / manifest mcp-server | Partial | 5 of 6 | MCP server detected at https://mcp.newrelic.com/mcp; it requires authentication. Presence is verified (5/6), but Ora could not inspect its tools or verify access scopes without credentials. |
| MCP well-known discovery mcp-well-known-discovery | Partial | 1 of 2 | MCP server at https://mcp.newrelic.com/mcp - list its server card, hosted on your own domain, in /.well-known/ai-catalog.json so MCP clients can discover it |
| Public API with reachable endpoints public-api | Pass | 7 of 7 | REST API documentation found at https://docs.newrelic.com/docs/new-relic-solutions/get-started/intro-new-relic.md. GraphQL endpoint at https://api.newrelic.com/graphql is reachable; |
| Public API/docs linked from homepage public-api-docs | Pass | 3 of 3 | Documentation site found at https://docs.newrelic.com |
| Developer portal developer-portal | Pass | 6 of 6 | Developer portal found at /docs |
| API catalog (RFC 9727) api-catalog-rfc9727 | Fail | 0 of 2 | No /.well-known/api-catalog found (RFC 9727) |
| OAuth 2.0 support oauth-support | Pass | 5 of 5 | OpenID Connect discovery endpoint found at https://mcp.newrelic.com |
| OAuth Protected Resource metadata (RFC 9728) oauth-protected-resource | Pass | 2 of 2 | no detail published |
| auth.md exists auth-md-exists | Fail | 0 of 2 | No /auth.md found at site root |
| WebMCP support webmcp | Fail | 0 of 5 | No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 14 of 14 same-origin script bundle(s) for modelContext registrations) |
| NLWeb /ask endpoint nlweb-ask | Pass | 1 of 1 | NLWeb /ask endpoint exists but requires authentication (HTTP 403, via POST) |
| CLI tool available cli-tool | Pass | 3 of 3 | CLI package found on npm: newrelic |
| Multi-language SDK packages rest-sdk-packages | Pass | 3 of 3 | SDK packages found across 4 ecosystems: npm, pypi, go, rubygems |
| Rate limit response headers rate-limit-headers | Fail | 0 of 2 | GraphQL introspection auth-gated and no header convention documented on GraphQL-tagged pages |
| Idempotency-Key support idempotency-key-support | Fail | 0 of 3 | GraphQL introspection auth-gated and no idempotency documentation found on GraphQL-tagged pages |
| JSON error responses json-error-responses | Pass | 4 of 4 | no detail published |

## At the door

What the site answers when a request arrives with an agent's user agent, and what robots.txt says to agents. One check in this group does not apply to this site and is left out.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Not blocked by bot detection bot-detection | Pass | 2 of 2 | Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot). |
| Agent crawler reachability agent-crawler-reachability | Pass | 2 of 2 | Reachable to every agent we tested - ChatGPT-User: reachable, OAI-SearchBot: reachable, Claude-User: reachable, PerplexityBot: reachable |
| robots.txt AI crawler policy robots-ai-policy-quality | Pass | 2 of 2 | AI search crawlers: allowed in 18 of 18 checks (3 crawlers on 6 pages). AI training crawlers: allowed in 12 of 12 checks (2 crawlers on 6 pages), not scored. |
| robots.txt agent-user policy robots-agent-user-policy | Pass | 2 of 2 | No applicable crawl or usage restriction found for 3 user-triggered agents (chatgpt-user, claude-user, perplexity-user) on 1 public page: https://newrelic.com/. Declared policy only; |
| Content behind auth docs-auth-gate | Pass | 2 of 2 | All 5 sampled pages are publicly readable (5 with substantive content) |
| Homepage not hidden from search noindex-directives | Pass | 1 of 1 | No noindex on the homepage: no robots, googlebot or bingbot meta tag and no X-Robots-Tag header hides it from search. |
| Redirect hygiene redirect-hygiene | Pass | 1 of 1 | no detail published |

## What an agent can read

Whether the text is in the first response, what the site publishes for agents, and how it describes itself to them.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Content without JavaScript content-no-js | Partial | 1 of 3 | Homepage: 10191 chars of readable text, but no H1 tag. 5 of 5 sampled inner pages have text without JavaScript. |
| Page token budget page-token-budget | Pass | 1 of 1 | All 6 measured pages fit an agent context budget (largest ~5K tokens) |
| Sitemap exists sitemap | Pass | 2 of 2 | Valid sitemap found at https://newrelic.com/sitemap.xml with 2655 entries |
| Sitemap freshness (lastmod) sitemap-lastmod | Pass | 1 of 1 | no detail published |
| llms.txt exists llms-txt-exists | Pass | 1 of 1 | Found the llms.txt at https://docs.newrelic.com/llms.txt. |
| llms.txt formatting llms-txt-formatting | Partial | 1 of 2 | The llms.txt at https://newrelic.com/llms.txt is well-formatted with markdown links, but at 43,753 characters it exceeds the 30,000-character recommendation for a navigation index. |
| llms.txt links resolve llms-txt-links-resolve | Pass | 2 of 2 | no detail published |
| Markdown agent docs markdown-negotiation | Fail | 0 of 1 | Missing markdown content negotiation. Homepage returned text/html when probed with Accept: text/markdown (expected text/markdown), and none of the well-known root paths (/llms.md, /auth.md, /agents.md, /developers.md, |
| Markdown URL fallback markdown-url-fallback | Fail | 0 of 2 | Homepage does not support the .md suffix. Probed https://newrelic.com/index.md and it did not return markdown (expected text/markdown content-type or a heading-led non-HTML body). |
| Bot-UA markdown serving agent-ua-markdown | Fail | 0 of 1 | No probed bot User-Agent (ChatGPT-User, Claude-User, Perplexity-User) receives markdown when requesting HTML. Optional: detect AI-bot UAs server-side and serve them a markdown representation directly. |
| Agent mode view agent-mode-view | Fail | 0 of 2 | ?mode=agent returns same content as homepage (no dedicated agent view) |
| JSON-LD structured data json-ld | Partial | 2 of 4 | JSON-LD Organization found - missing description on this entity |
| Organization schema completeness org-schema-completeness | Partial | 1 of 2 | Organization schema found but missing: address |
| JSON-LD entity linking (sameAs) json-ld-entity-linking | Partial | 1 of 2 | Entity linking to linkedin.com - add more authority profiles (Wikipedia, Wikidata, LinkedIn, GitHub) |
| Schema type breadth schema-type-breadth | Fail | 0 of 2 | No extended schema types found - AI can only answer basic questions about this entity |
| Metadata completeness metadata-completeness | Pass | 2 of 2 | All metadata signals present: canonical URL, lang="en", og:image, og:type |
| Agent instruction / when-to-use agent-instruction | Pass | 3 of 3 | no detail published |

## Found and recommended

Whether an assistant can find the company by name, confirm what it is, and see it in the registries agents read. 2 checks in this group do not apply to this site and are left out.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Brand name discoverability brand-search-accuracy | Partial | 1 of 3 | newrelic.com ranks #8 for "New Relic" (searched your brand name alone: no main product term from your homepage qualified) |
| Wikipedia / Wikidata entity presence wikipedia-presence | Pass | 4 of 4 | Wikipedia "New Relic" and Wikidata Q7011152 both verified - domain confirmed on both sources |
| Developer resource discoverability agentic-search-specific | Pass | 3 of 3 | no detail published |
| Listed in MCP registries mcp-registry-listed | Pass | 1 of 1 | no detail published |
| NPM/PyPI SDK package npm-sdk-package | Pass | 1 of 1 | no detail published |
| Listed on skills.sh skills-sh-listed | Pass | 1 of 1 | no detail published |
| ARD discovery ard-catalog | Fail | 0 of 1 | No /.well-known/ard.json, no same-site rel="ard" link, and no legacy /.well-known/ai-catalog.json |

## Payments

The agent payment protocols Ora probes for. A site that sells nothing has nothing here, and Ora scores the layer out of zero when none applies. None of the 6 payment checks applied to newrelic.com.

## The fixes worth most points

Ora attaches an estimate to each failing or partial check: how many points the site would gain by passing it. These are the 5 with the largest estimates for New Relic, with what Ora observed. The wording of each fix is Ora's; [the 28 checks it runs on an MCP server](https://agentmcpdirectory.com/mcp-checks/) are listed with their layer and tier.

-   WebMCP support: fail, 0 of 5, about 3.4 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 14 of 14 same-origin script bundle(s) for modelContext registrations)
-   Brand name discoverability: partial, 1 of 3, about 2.8 points to gain. Ora saw: newrelic.com ranks #8 for "New Relic" (searched your brand name alone: no main product term from your homepage qualified)
-   GraphQL typed error model: fail, 0 of 3, about 2.1 points to gain. Ora saw: GraphQL introspection auth-gated and no typed graphql error model documentation found on GraphQL-tagged pages
-   Idempotency-Key support: fail, 0 of 3, about 2.1 points to gain. Ora saw: GraphQL introspection auth-gated and no idempotency documentation found on GraphQL-tagged pages
-   ARD discovery: fail, 0 of 1, about 1.4 points to gain. Ora saw: No /.well-known/ard.json, no same-site rel="ard" link, and no legacy /.well-known/ai-catalog.json

## Our read

New Relic's read has a shield across three of its act-layer rows. The OpenAPI specification probe at /.well-known/openapi.json, the A2A agent card and the agent skills index were each answered 403 by a bot shield rather than by the site, so those rows are unverified and fall out of the maximum, which is part of why Access reads 42 of 51. What Ora could reach is in order: the MCP server at mcp.newrelic.com/mcp answers and requires authentication, OpenID Connect discovery is on the same host, the REST documentation is at docs.newrelic.com with an llms.txt, the newrelic CLI is on npm and SDKs are in four registries. The deductions are a home page of 10,191 characters with no H1, no WebMCP registration in 14 script bundles, a gated GraphQL introspection with no typed error model, and a brand search that places the domain eighth. Letting the probes through would settle three rows in one setting.

## Test your own surfaces

The scan above is free and needs no account: enter a domain at [ora.ai](https://ora.ai/?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=check) and read the same four layers for your own site. For an MCP server, Ora scans the server URL itself and runs 28 of its 132 public checks on it, which is why it is the check this directory recommends; [the reasons, the limits and the alternatives](https://agentmcpdirectory.com/test-your-mcp-server/) are on their own page. The command below runs the same audit from a terminal and exits with 1 under the score you set, so it can gate a deploy.

```bash
npx ax@0.10 audit https://example.com --min-score 70
```

[All 360 checks](https://agentmcpdirectory.com/blog/), one company a day. Corrections to [the corrections page](https://agentmcpdirectory.com/corrections/).

Edition

4 November 2026

Method

[How rows are verified](https://agentmcpdirectory.com/method/)

Data

[CSV and JSON](https://agentmcpdirectory.com/data/)

Markdown

[This page as markdown](https://agentmcpdirectory.com/blog/newrelic-agent-readiness/index.md)

## Sources

-   [Ora's scan of newrelic.com, GET /api/score (vendor)](https://ora.ai/api/score/newrelic.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=check), read 9 November 2026
-   [Ora check catalogue, contract 1.38.0](https://ora.ai/api/checks?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=check), read 5 November 2026
-   [newrelic.com, the company's site](https://newrelic.com/), read 9 November 2026

Last reviewed 9 November 2026