NTT: 68 of 100 on Ora's agent-readiness scan

The score

NTT is a telecommunications group based in Tokyo.

• 68of 100, grade C
  Ora's agent-readiness scan of group.ntt, read 10 November 2026.
• 8Discovery, of 9
  Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
• 23Access, of 38
  Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
• 10Usability, of 16
  Whether they can act through it: an MCP server, an API with a specification, sign-in for agents.
• 0Payments, of 0
  No check in this layer applied to the site.

79 percent of the 132,085 domains Ora ranks score under 60, and the average score is 44.

Ora's one-line summary: NTT's group site offers a solid discovery and crawler-policy foundation, but lacks WebMCP support and any agent instruction file with when-to-use guidance.

What an assistant meets at the door

Before an assistant can read, compare or buy, it has to get in. These rows are the door: whether the bot shield lets the main agents through, what robots.txt tells the search, training and user-triggered agents, and whether the home page has text without running JavaScript.

What it can read, and what it can do

The reading layer is what an assistant takes away from the pages: a text file written for it, markdown on request, structured data about the company, a sitemap. The act layer is whether it can do anything through a published interface rather than by clicking through the site.

The six payment checks did not apply on this read: Ora did not read the site as a shop.

Three fixes to hand to the web team

Ora estimates how many points each open check would return. These are the largest on this read, in Ora's words where it gave them, so a leader can hand the list over without translating it.

1. WebMCP support, worth about 13.9 points by Ora's estimate: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 9 of 9 same-origin script bundle(s) for modelContext registrations).
2. Agent-friendly 404s, worth about 2.8 points by Ora's estimate: The nonexistent path https://group.ntt/__ora-404-probe-0zn1omhh correctly returns HTTP 404. Partial credit: no Markdown error body was detected.
3. Agent auth discovery metadata, worth about 2.6 points by Ora's estimate: Neither /.well-known/oauth-protected-resource nor /.well-known/oauth-authorization-server found. Probed: group.ntt, api.group.ntt.

Our read

NTT's group site is a well-kept front door with little behind it for an agent to do. All four test agents reached the home page, robots.txt allowed the AI search crawlers in 18 of 18 checks across six pages and the training crawlers in 12 of 12, and no restriction applies to the user-triggered agents; Discovery reads 8 of 9. What an assistant can read is thinner than the door suggests: 3,492 characters with an H1 at a 0.8 percent content ratio, 2 of 5 sampled pages with almost no text without JavaScript, a sitemap of 10,922 entries, complete metadata, an Organization block missing its description and url, and no llms.txt. What it can do is nothing yet: neither an API nor OAuth, no MCP server or developer portal, and a search for NTT's API documentation found none of the 10 results official. A C at 68 where one fix, WebMCP, is worth about 14 points, and the rest are change.

Test your own site

Run the same scan on your own domain at ora.ai. The score, the layers and the fixes on this page come from its public result for group.ntt; a scan of a public site takes a few minutes and needs no account.

• Scan your domain on OraThe same checks, the same scoring, on your own site.
• The self-check, 18 questionsWhat to ask for, in business terms, before the scan.
• All the 360 checksThe other companies in this series, newest first.