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

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

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

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

# Postman: the 360 agent-readiness check

Postman scores 80 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. The API specification company, without a specification for its own API.

On 9 November 2026 the public site at postman.com scored 80 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 Developer Tools 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: Postman offers strong developer resource discoverability and MCP registry listings, but lacks a published OpenAPI specification for agents to act on.

## The score

| Layer | Asks | Points | Share |
| --- | --- | --- | --- |
| Usability | Can agents use it | 57 of 74 | 77% |
| Access | Can agents read it | 44 of 60 | 73% |
| Discovery | Can agents find and recommend it | 15 of 16 | 94% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade B | 80 of 100 | 80% |

## 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. 2 checks in this group do not apply to this site and are left out.

In the directory, Postman sign-in required, tools not seen, not counted; the connector run of 4 November 2026 is on [the entry page](https://agentmcpdirectory.com/directory/postman-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.postman.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.postman.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 /api. Best-of-protocols score: 7/7. |
| Public API/docs linked from homepage public-api-docs | Pass | 3 of 3 | API/docs link found on homepage and resolves: https://learning.postman.com/docs/reference/developer-resources/postman-plugin |
| Developer portal developer-portal | Pass | 6 of 6 | Developer portal found at /docs |
| 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 | Pass | 5 of 5 | OAuth authorization server metadata at https://mcp.postman.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 | Path https://postman.com/auth.md returned HTML (SPA / 404 fallback), not an auth.md document |
| WebMCP support webmcp | Fail | 0 of 5 | No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 30 of 30 same-origin script bundle(s) for modelContext registrations) |
| 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 package found on npm: postman-cli |
| Multi-language SDK packages rest-sdk-packages | Partial | 1 of 3 | SDK package found only in npm |
| 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.

| 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 3 of 3 checks (3 crawlers on 1 page). AI training crawlers: allowed in 2 of 2 checks (2 crawlers on 1 page), 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://postman.com/. Declared policy only; |
| Content behind auth docs-auth-gate | Pass | 2 of 2 | All 5 sampled pages are publicly readable (0 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 | 1 of 3 | Homepage: 3254 chars with H1, but 1.6% content ratio is below the 5% target. Sampled pages with almost no text without JavaScript (5 of 5): https://www.postman.com/category/app-security (7 chars), |
| Page token budget page-token-budget | Pass | 1 of 1 | All 6 measured pages fit an agent context budget (largest ~1K tokens) |
| Sitemap exists sitemap | Pass | 2 of 2 | Valid sitemap found at https://www.postman.com/sitemap.xml with multiple sitemaps entries |
| Sitemap freshness (lastmod) sitemap-lastmod | Partial | 0 of 1 | Sitemap lastmod dates are all stale - the newest is 593 days old. Update lastmod when content changes or agents will deprioritize the whole site as unmaintained. |
| llms.txt exists llms-txt-exists | Pass | 1 of 1 | Found the llms.txt at https://postman.com/llms.txt. |
| llms.txt formatting llms-txt-formatting | Pass | 2 of 2 | The llms.txt is well-formatted: 130 lines with markdown links, 21,271 characters in total. |
| llms.txt links resolve llms-txt-links-resolve | Pass | 2 of 2 | no detail published |
| Markdown agent docs markdown-negotiation | Pass | 1 of 1 | Returns markdown when requested via Accept header |
| Markdown URL fallback markdown-url-fallback | Fail | 0 of 2 | Homepage does not support the .md suffix. Probed https://postman.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 | Pass | 2 of 2 | no detail published |
| JSON-LD structured data json-ld | Pass | 4 of 4 | Rich JSON-LD identity: Organization with name, description, url, and sameAs/logo/address (2 block(s)) |
| Organization schema completeness org-schema-completeness | Pass | 2 of 2 | no detail published |
| JSON-LD entity linking (sameAs) json-ld-entity-linking | Pass | 2 of 2 | no detail published |
| 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:type |
| Agent instruction / when-to-use agent-instruction | Fail | 0 of 3 | No agent instruction file with when-to-use guidance found |

## Found and recommended

Whether an assistant can find the company by name, confirm what it is, and see it in the registries agents read.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Brand name discoverability brand-search-accuracy | Pass | 3 of 3 | postman.com ranks #4 for "Postman Application Programming Interfaces" and #10 for "Postman API development" |
| Wikipedia / Wikidata entity presence wikipedia-presence | Partial | 2 of 4 | Wikidata Q105538901 (Postman) verified - draft a Wikipedia page with cited references to complete knowledge graph coverage |
| 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 |
| ChatGPT app listed chatgpt-app-listed | Pass | 2 of 2 | no detail published |
| Registry branding registry-branding | Partial | 1 of 2 | MCP manifest has name but missing description/icon at /.well-known/mcp.json |
| 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 | OPTIONS allows POST at https://api.postman.com/checkout_sessions but POST 404 returned no ACP response |
| ACP delegate payment acp-delegate-payment | Partial | 0 of 3 | OPTIONS allows POST at https://api.postman.com/agentic_commerce/delegate_payment but POST 404 returned no ACP response |
| 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 Postman, 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 3.9 points to gain. Ora saw: No OpenAPI/Swagger specification found
-   Scoped permissions: fail, 0 of 5, about 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 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 30 of 30 same-origin script bundle(s) for modelContext registrations)
-   Agent instruction / when-to-use: fail, 0 of 3, about 1.7 points to gain. Ora saw: No agent instruction file with when-to-use guidance found
-   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

Postman is the company that made the API specification a product, and Ora found no OpenAPI specification for Postman's own API at any path it probes, about 4 points and the largest single deduction on this page. The rest of the act layer is in order: the MCP server at mcp.postman.com/mcp answers and requires authentication, OAuth authorization server metadata is on the same host, the REST documentation scores 7 of 7, postman-cli is on npm and postman.com serves an llms.txt and returns markdown when an agent asks for it with an Accept header. The gaps beyond the specification are the usual newer ones, no declared scopes, no WebMCP registration in 30 script bundles, no agent instruction file and no ARD catalog. The home page gives 3,254 characters at a 1.6 percent text ratio under two Organization blocks. A B at 80 for the API company; the file its users publish for their APIs is the one it has not published for itself.

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

## Sources

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

Last reviewed 9 November 2026