---
title: "Amazon Web Services: the 360 agent-readiness | Agent MCP Directory"
description: "Amazon Web Services on Ora's agent-readiness scan, read 2026-11-09: 60 of 100, grade C, with the MCP, API and OAuth surfaces an agent can call."
canonical: https://agentmcpdirectory.com/blog/aws-agent-readiness
site: "Agent MCP Directory"
last_updated: 2026-11-09
date: 2026-11-09
section: "360 checks"
---

# Amazon Web Services: the 360 agent-readiness | Agent MCP Directory

> Amazon Web Services on Ora's agent-readiness scan, read 2026-11-09: 60 of 100, grade C, with the MCP, API and OAuth surfaces an agent can call.

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

# Amazon Web Services: the 360 agent-readiness check

Amazon Web Services scores 60 of 100 on Ora's agent-readiness scan, a C, read 9 November 2026. Of the five surfaces an agent acts on, Ora found 2: a public API, a command line. The largest cloud, with its MCP server a blog post and its specifications in repositories.

On 9 November 2026 the public site at aws.amazon.com scored 60 of 100 on [Ora's](https://ora.ai/?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=check) agent-readiness scan, a C, 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: AWS offers strong developer resource discoverability and SDK packages, but lacks published OpenAPI specifications for agent integration.

## The score

| Layer | Asks | Points | Share |
| --- | --- | --- | --- |
| Usability | Can agents use it | 27 of 68 | 40% |
| Access | Can agents read it | 38 of 59 | 64% |
| Discovery | Can agents find and recommend it | 16 of 17 | 94% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade C | 60 of 100 | 60% |

## 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.

In the directory, Amazon Web Services has an open MCP server with tools listed at https://knowledge-mcp.global.api.aws, 5 tools listed, no authentication; the connector run of 4 November 2026 is on [the entry page](https://agentmcpdirectory.com/directory/aws-amazon-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 | 2 of 6 | MCP mentioned at https://aws.amazon.com/blogs/aws/the-aws-mcp-server-is-now-generally-available but no standard manifest endpoint found |
| MCP well-known discovery mcp-well-known-discovery | Fail | 0 of 2 | No MCP server URL discovered |
| Public API with reachable endpoints public-api | Pass | 7 of 7 | API described in documentation at https://docs.aws.amazon.com but no machine-verifiable API surface confirmed. GraphQL endpoint at https://api.amazon.com/graphql is reachable; |
| Public API/docs linked from homepage public-api-docs | Pass | 3 of 3 | Documentation site found at https://docs.aws.amazon.com |
| Developer portal developer-portal | Pass | 6 of 6 | Developer portal found at /developers |
| OpenAPI spec published openapi-spec | Fail | 0 of 7 | No OpenAPI/Swagger specification found |
| API catalog (RFC 9727) api-catalog-rfc9727 | Fail | 0 of 2 | No /.well-known/api-catalog found (RFC 9727) |
| A2A / agent-card a2a-agent-card | Fail | 0 of 2 | No A2A agent card found at /.well-known/agent-card.json |
| Agent discovery file agent-discovery-file | Fail | 0 of 2 | No agent discovery file found |
| OAuth 2.0 support oauth-support | Fail | 0 of 5 | No OAuth 2.0 or OpenID Connect support detected |
| OAuth Protected Resource metadata (RFC 9728) oauth-protected-resource | Fail | 0 of 2 | No /.well-known/oauth-protected-resource found (RFC 9728) |
| 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 |
| NLWeb /ask endpoint nlweb-ask | Fail | 0 of 1 | No NLWeb-conformant /ask endpoint found via GET or POST |
| CLI tool available cli-tool | Pass | 3 of 3 | CLI tool found on PyPI: cloudformation-cli |
| 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 | Fail | 0 of 4 | API does not return JSON error responses (or no API detected) |

## At the door

What the site answers when a request arrives with an agent's user agent, and what robots.txt says to agents.

| 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://aws.amazon.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 |
| Web Bot Auth directory web-bot-auth-directory | Fail | 0 of 2 | No /.well-known/http-message-signatures-directory found |

## 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 | 2 of 3 | Homepage: 4564 chars with H1, but 2.7% content ratio is below the 5% target. 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 ~4K tokens) |
| Sitemap exists sitemap | Pass | 2 of 2 | Valid sitemap found at https://aws.amazon.com/sitemaps/index/ with multiple sitemaps 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.aws.amazon.com/llms.txt. |
| llms.txt formatting llms-txt-formatting | Partial | 1 of 2 | The llms.txt is well-formatted with markdown links, but at 411,652 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://aws.amazon.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 | 1 of 4 | JSON-LD found (2 block(s)) but no identity type - use SoftwareApplication, Product, Organization, Person, or Article so agents can tell what this site is |
| Organization schema completeness org-schema-completeness | Fail | 0 of 2 | No Organization type found in JSON-LD |
| JSON-LD entity linking (sameAs) json-ld-entity-linking | Fail | 0 of 2 | No sameAs entity linking in JSON-LD - agents cannot disambiguate your brand |
| Schema type breadth schema-type-breadth | Partial | 1 of 2 | Some extended schema types found: ItemList - add 2 more types that match what the homepage shows, for full coverage |
| Metadata completeness metadata-completeness | Partial | 1 of 2 | 3/4 metadata signals present - missing: og:image |
| Agent instruction / when-to-use agent-instruction | Partial | 2 of 3 | When-to-use guidance found at https://docs.aws.amazon.com |

## 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 | Pass | 3 of 3 | aws.amazon.com ranks #2 for "Amazon Web Services, Inc. cloud computing" (search term updated) |
| Wikipedia / Wikidata entity presence wikipedia-presence | Pass | 4 of 4 | Wikipedia "Amazon Web Services" and Wikidata Q456157 both verified - domain confirmed on both sources |
| Developer resource discoverability agentic-search-specific | Pass | 3 of 3 | no detail published |
| NPM/PyPI SDK package npm-sdk-package | Pass | 1 of 1 | no detail published |
| ChatGPT app listed chatgpt-app-listed | Pass | 2 of 2 | 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.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| UCP - Universal Commerce Protocol ucp-support | Partial | 0 of 3 | no UCP (Universal Commerce Protocol) signals detected |
| ACP - Agentic Commerce Protocol acp-support | Partial | 0 of 3 | no ACP (Agentic Commerce Protocol) signals detected |
| ACP delegate payment acp-delegate-payment | Partial | 0 of 3 | No ACP Delegate Payment signals detected |
| AP2 - Agent Payments Protocol ap2-support | Partial | 0 of 3 | No AP2 (Agent Payments Protocol) signals detected |
| x402 payment protocol x402-support | Partial | 0 of 2 | No x402 payment protocol support detected |
| MPP payment protocol mpp-support | Partial | 0 of 2 | No MPP (Machine Payments Protocol) support detected |

## 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 Amazon Web Services, 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.

-   OpenAPI spec published: fail, 0 of 7, about 4 points to gain. Ora saw: No OpenAPI/Swagger specification found
-   OAuth 2.0 support: fail, 0 of 5, about 3.3 points to gain. Ora saw: No OAuth 2.0 or OpenID Connect support detected
-   Scoped permissions: fail, 0 of 5, about 3.3 points to gain. Ora saw: No declared OAuth scopes, security schemes, or scoped-permission documentation found
-   WebMCP support: fail, 0 of 5, about 3.3 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found
-   JSON error responses: fail, 0 of 4, about 2.6 points to gain. Ora saw: API does not return JSON error responses (or no API detected)

## Our read

AWS is read here at aws.amazon.com, and the act layer Ora finds on that host is a blog post. The MCP server credit is a mention in the announcement that the AWS MCP server is generally available, with no endpoint at a URL Ora could discover; the APIs are described at docs.aws.amazon.com with no machine-verifiable surface, there is no OpenAPI specification, no OAuth or OpenID Connect discovery, no declared scopes and no JSON error responses from the endpoints Ora tried. SDKs are in four registries and a CLI, cloudformation-cli, is on PyPI, and docs.aws.amazon.com carries an llms.txt. The reading side is middling: the two JSON-LD blocks have no identity type, the home page is 2.7 percent text, the door is open to all four agent user agents and five of five sampled pages read. The largest cloud in the world publishes service specifications by the hundred inside its SDK repositories; none is where this scan looks.

## 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/aws-agent-readiness/index.md)

## Sources

-   [Ora's scan of aws.amazon.com, GET /api/score (vendor)](https://ora.ai/api/score/aws.amazon.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
-   [aws.amazon.com, the company's site](https://aws.amazon.com/), read 9 November 2026

Last reviewed 9 November 2026