notion.so Website

CachedScored . Refresh available now. This is cache-reuse eligibility; a fresh audit is still subject to service limits.Markdown · JSON
68site score

28 global-ready

relative to the checks that apply to this site, including 1 host it declares (see Declared hosts); global measures it against a maximally agent-ready site. Website https://notion.so/ (audited at www.notion.so). Global keeps the 17 checks this audit could not run in its maximum.

Declared hosts

notion.so points agents to these hosts; results from the hosts anc could confirm are credited to notion.so.

  1. ai-catalog entry

    mcp.notion.com

    https://mcp.notion.com/mcp/server-card

    evaluated

  2. server card

    mcp.notion.com

    https://mcp.notion.com/mcp

    evaluated

    confirmed by https://mcp.notion.com/mcp/server-card

Checks by category

  1. C1

    Discoverability

    3 / 6 checks pass

    /robots.txt present SHOULD PASS

    Goal: Publish robots.txt and state your crawl policy explicitly.

    Result: Verified (https://www.notion.so/robots.txt -> 200)

    Resources: RFC 9309 · Fix skill

    /sitemap.xml present MAY PASS

    Goal: Publish sitemap.xml so agents can enumerate your content URLs.

    Result: Verified (https://www.notion.so/sitemap.xml -> 200)

    Resources: sitemaps.org · Fix skill

    Homepage sends RFC 8288 Link headers pointing at agent resources SHOULD MISSING

    Goal: Advertise machine surfaces in a Link response header on / for header-only discovery.

    Result: Not found (https://www.notion.so/ -> 200 (header link no match /rel="?(service-desc|describedby|api-catalog|service-doc)"?/))

    Fix: Send a `Link` response header on `/` (RFC 8288) whose `rel` points at your machine surfaces, so an agent reading only response headers finds them without parsing HTML or probing `/.well-known`. Use the RFC 8631 service trio and the RFC 9727 catalog: `rel="service-desc"` at a machine-readable description (OpenAPI, or an MCP server card), `rel="service-doc"` at the human-readable doc, `rel="service-meta"` at the service-context declaration, and `rel="api-catalog"` at your `/.well-known/api-catalog` index. Example: `Link: </.well-known/api-catalog>; rel="api-catalog", </.well-known/mcp/server-card.json>; rel="service-desc"`.

    Resources: RFC 8288 (Link) · RFC 8631 (service links) · RFC 9727 (api-catalog) · Fix skill

    Root HTML links to machine surfaces via <link rel> SHOULD PASS

    Goal: Point link rel elements at your machine surfaces from the root HTML head.

    Result: Verified (https://www.notion.so/ -> 200)

    Resources: RFC 8631 (service-desc/doc) · Fix skill

    DNS for AI Discovery (DNS-AID) records under _agents (IETF draft) MAY N/A

    Goal: Publish DNSSEC-signed SVCB records under _agents for DNS-level agent discovery.

    Result: Not implemented, optional (no DNS-AID records)

    Resources: DNS-AID draft · Fix skill

    404 body is markdown with a recovery link SHOULD BROKEN

    Goal: Serve a short markdown 404 that links at least one agent recovery surface.

    Result: Present but broken (https://www.notion.so/anc-web-audit-no-such-page -> 200 (status 200 not in [404, 410]))

    Fix: When `Accept: text/markdown` hits an unknown path, return 404 or 410 with a short markdown body that includes at least one recovery link: sitemap, `llms.txt`, a docs index, or an equivalent same-origin href. Linking both sitemap and `llms.txt` as absolute URLs is the stronger pattern. Zero links is a miss even when the status is correct.

    Resources: llmstxt.org · Fix skill

    Unknown paths return HTTP 404 or 410 SHOULD BROKEN

    Goal: Return a real HTTP 404 or 410 for unknown paths instead of a 200 SPA shell.

    Result: Present but broken (https://www.notion.so/anc-web-audit-no-such-page -> 200 (status 200 not in [404, 410]))

    Fix: Configure the origin so a nonsense path under the site returns HTTP 404 or 410, not 200 with the application shell. A soft-404 hides recovery from agents: they treat the page as content and never look for a sitemap or `llms.txt`. Verify with `curl -sS -o /dev/null -w "%{http_code}" https://example.com/this-path-does-not-exist` — it MUST print `404` (or `410`).

    Resources: RFC 9110 status codes · Fix skill

    partial
  2. C2

    Content for agents

    7 / 11 checks pass

    Evaluated at www.notion.com

    /llms.txt present with a summary and link index SHOULD PASS

    Evaluated at www.notion.so

    Goal: Serve /llms.txt with a title, summary, and categorized link index.

    Result: Verified (https://www.notion.so/llms.txt -> 200)

    Resources: llmstxt.org · Fix skill

    /llms-full.txt present (single-fetch full corpus) MAY N/A

    Evaluated at www.notion.so

    Goal: Serve the whole docs corpus as markdown at /llms-full.txt for one-fetch ingestion.

    Result: Not implemented, optional (https://www.notion.so/llms-full.txt -> 404 (status 404 not in [200]))

    Resources: llmstxt.org · Fix skill

    Accept text/markdown content negotiation returns markdown SHOULD MISSING

    Evaluated at www.notion.so

    Goal: Honor Accept text/markdown on content URLs with raw markdown, not HTML chrome.

    Result: Not found (https://www.notion.so/ -> 200 (content-type "text/html; charset=utf-8" !~ /markdown|text/plain/))

    Fix: Honor `Accept: text/markdown` on content URLs and return raw markdown rather than HTML chrome. Agents parse markdown far more reliably than a JS-rendered page. Serve the markdown twin at the same URL via content negotiation, invisibly to crawlers.

    Resources: RFC 7763 (text/markdown) · Fix skill

    Per-section llms-full.txt files resolve under content subdirectories MAY N/A

    Goal: Serve a scoped llms-full.txt corpus inside each major content section.

    Result: Not applicable (root llms-full.txt not present)

    Resources: llmstxt.org · Fix skill

    llms.txt has H1, summary, and a link index SHOULD MISSING

    Evaluated at www.notion.so

    Goal: Structure /llms.txt with an H1, a blockquote summary, and a markdown link index.

    Result: Not found (https://www.notion.so/llms.txt -> error (link index present))

    Fix: Follow the llmstxt.org shape: start with `# Title`, add a `>` summary blockquote, then a categorized list of markdown links. A file that is present but is only a heading, or only a blob of prose, fails this row even when the presence check passes.

    Resources: llmstxt.org · Fix skill

    llms.txt has a when-to-use or programmatic-access section SHOULD MISSING

    Evaluated at www.notion.so

    Goal: Tell agents when to use the MCP or docs from a short llms.txt heading.

    Result: Not found (https://www.notion.so/llms.txt -> error (no when-to-use heading))

    Fix: Add a heading such as `## When to use` or `## Programmatic access` with a few lines on when an agent should connect (for example: "Use the MCP when you need to search or score a CLI"). The audit looks for that heading; it does not grade the prose with an LLM.

    Resources: llmstxt.org · Fix skill

    Per-section llms.txt files resolve under content subdirectories MAY N/A

    Goal: Serve a scoped llms.txt inside each major content section.

    Result: Not implemented, optional (llms-txt-scoped -> error (no section directories in the root llms.txt or sitemap))

    Resources: llmstxt.org · Fix skill

    Bare CLI User-Agent receives the markdown twin MAY N/A

    Evaluated at www.notion.so

    Goal: Serve the markdown twin to shell HTTP clients that state no content-type preference.

    Result: Not implemented, optional (https://www.notion.so/ -> 200 (content-type "text/html; charset=utf-8" !~ /markdown|text/plain/))

    Resources: RFC 7763 (text/markdown) · RFC 9110 (User-Agent) · Fix skill

    AI user-fetch User-Agent receives the markdown twin MAY N/A

    Evaluated at www.notion.so

    Goal: Serve the markdown twin to AI on-demand user-fetchers that state no content-type preference.

    Result: Not implemented, optional (https://www.notion.so/ -> 200 (content-type "text/html; charset=utf-8" !~ /markdown|text/plain/))

    Resources: RFC 7763 (text/markdown) · OpenAI bots and User-Agents · Fix skill

    Negotiated responses carry Vary Accept SHOULD MISSING

    Evaluated at www.notion.so

    Goal: Name every negotiated request header in Vary so shared caches never serve one client the wrong variant.

    Result: Not found (https://www.notion.so/ -> 200 (header vary no match /(?:^|[\s,])(?:accept|\*)(?:[\s,]|$)/))

    Fix: When the same URL serves HTML or markdown depending on the request, emit a `Vary` header on every response that names each request header the choice depends on: `Vary: Accept` when you negotiate on `Accept` alone, and `Vary: Accept, User-Agent` when agent User-Agents also receive the markdown twin. Without it a shared cache (a CDN or a corporate proxy) can store the markdown twin under the bare URL and then hand it to a browser, or the reverse. If the CDN ignores or strips Vary (Cloudflare's zone cache historically keeps only `Accept-Encoding`), do not give that cache a long `s-maxage` on negotiated responses: HIT replies would then reach clients with no Vary, and the check still fails.

    Resources: RFC 9110 (Vary) · Fix skill

    Root HTML has a descriptive <meta name="description"> SHOULD PASS

    Evaluated at www.notion.so

    Goal: Add a meta description naming what the service does and its agent entry points.

    Result: Verified (https://www.notion.so/ -> 200)

    Resources: MDN meta description · Fix skill

    Root HTML embeds Schema.org JSON-LD MAY PASS

    Evaluated at www.notion.so

    Goal: Embed Schema.org JSON-LD so agents get typed facts without inference.

    Result: Verified (https://www.notion.so/ -> 200)

    Resources: Schema.org · Fix skill

    Markdown twin carries YAML frontmatter MAY N/A

    Evaluated at www.notion.so

    Goal: Prefix the markdown twin with a YAML frontmatter block so agents read page metadata without parsing the body.

    Result: Not implemented, optional (https://www.notion.so/ -> 200 (root served HTML, not a markdown twin))

    Resources: YAML front matter (Jekyll) · RFC 7763 (text/markdown) · Fix skill

    Root HTML has an H1 and readable text without JavaScript SHOULD PASS

    Evaluated at www.notion.so

    Goal: Put an H1 and enough visible text in the raw root HTML that a non-JS agent can read the page.

    Result: Verified (https://www.notion.so/ -> 200)

    Resources: llmstxt.org · Fix skill

    Root HTML uses semantic landmarks MAY PASS

    Evaluated at www.notion.so

    Goal: Use semantic landmarks so the HTML path is parseable structure, not div soup.

    Result: Verified (https://www.notion.so/ -> 200)

    Resources: MDN content sectioning · Fix skill

    Root HTML has a <noscript> with machine entry points SHOULD PASS

    Evaluated at www.notion.so

    Goal: Give non-JS agents a noscript block listing your machine entry points.

    Result: Verified (https://www.notion.so/ -> 200)

    Resources: MDN noscript · Fix skill

    Accept text/plain returns the markdown twin MAY N/A

    Evaluated at www.notion.so

    Goal: Treat Accept text/plain as a request for the raw markdown source.

    Result: Not implemented, optional (https://www.notion.so/ -> 200 (content-type "text/html; charset=utf-8" !~ /markdown|text/plain/))

    Resources: RFC 7763 (text/markdown) · Fix skill

    llms.txt links resolve SHOULD PASS

    Goal: Make every markdown href in /llms.txt https and fetchable.

    Result: Verified (https://www.notion.com/product/ai -> 200)

    Resources: llmstxt.org · Fix skill

    partial
  3. C3

    Bot & crawl policy

    3 / 4 checks pass

    AI user-fetch User-Agent can reach the homepage SHOULD PASS

    Goal: Let on-demand user-fetchers GET / with Accept */* and receive 2xx, not a challenge page.

    Result: Verified (https://www.notion.so/ -> 200)

    Resources: OpenAI user-fetchers · Fix skill

    robots.txt declares AI-crawler rules (RFC 9309) SHOULD PASS

    Goal: State your AI-crawler policy in robots.txt with explicit User-agent rules.

    Result: Verified (https://www.notion.so/robots.txt -> 200)

    Resources: RFC 9309 · Fix skill

    robots.txt declares Content-Signal AI-usage preferences SHOULD MISSING

    Goal: Declare Content-Signal AI-usage preferences in robots.txt.

    Result: Not found (https://www.notion.so/robots.txt -> 200 (body no match /^\s*Content-Signal:\s*(ai-train|search|ai-input)/))

    Fix: Add `Content-Signal` directives to `robots.txt` (contentsignals.org): `ai-train`, `search`, and `ai-input` set to `yes` or `no`. They express usage preferences at a finer grain than a blanket allow/deny.

    Resources: contentsignals.org · Fix skill

    Web Bot Auth signature directory present (informational) MAY N/A

    Goal: Publish an HTTP Message Signatures directory if your site sends signed bot traffic.

    Result: Not implemented, optional (https://www.notion.so/.well-known/http-message-signatures-directory -> 404 (status 404 not in [200]))

    Resources: Web Bot Auth draft · Fix skill

    /.well-known/security.txt present (RFC 9116) MAY PASS

    Goal: Publish security.txt with a Contact and Expires field.

    Result: Verified (https://www.notion.so/.well-known/security.txt -> 200)

    Resources: RFC 9116 · Fix skill

    partial
  4. C4

    API

    0 / 0 checks pass

    No checks in this category apply to this site.

    An OpenAPI description is published MUST N/A

    Goal: Publish an OpenAPI description so non-MCP agents can call your HTTP API.

    Result: Not applicable (no API surface detected)

    Resources: OpenAPI 3.1 · Fix skill

    Referenced JSON Schemas resolve as application/schema+json MAY N/A

    Goal: Serve the JSON Schemas your API references so agents can validate payloads pre-flight.

    Result: Not applicable (no JSON Schema references detected)

    Resources: JSON Schema · Fix skill

    /.well-known/api-catalog published (RFC 9727) MAY N/A

    Goal: Serve an RFC 9727 api-catalog linkset indexing your API descriptions.

    Result: Not applicable (no API surface detected)

    Resources: RFC 9727 · Fix skill

    API client errors return JSON, not HTML SHOULD N/A

    Goal: Return a JSON error body on client-error API responses so agents can parse the failure.

    Result: Not applicable (no API surface detected)

    Resources: RFC 9457 (problem+json) · Fix skill

    API responses advertise rate-limit headers SHOULD N/A

    Goal: Advertise remaining quota on API responses so agents can back off instead of retrying blindly.

    Result: Not applicable (no API surface detected)

    Resources: IETF RateLimit header draft · Fix skill

    n/a
  5. C5

    MCP

    7 / 8 checks pass · 17 not run

    Evaluated at mcp.notion.com, declared by notion.so's ai-catalog entry

    Every MCP server

    7 / 8 pass

    transport, discovery, and card checks that apply whichever protocol the server speaks

    GET on the MCP endpoint answers fast (not a held-open hang) SHOULD PASS

    Goal: Answer GET with 405 or an SSE stream, never a document and never a held-open hang.

    Result: Verified (https://mcp.notion.com/mcp -> 401)

    Resources: MCP transports · Fix skill

    CORS preflight (OPTIONS) succeeds with Access-Control-Allow-* headers SHOULD PASS

    Goal: Serve one consistent CORS posture on the MCP endpoint, full preflight support or none.

    Result: Verified (preflight 204 allow-origin https://example.com; post 401 allow-origin https://example.com)

    Resources: MDN CORS preflight · Fix skill

    POST response carries Access-Control-Allow-Origin SHOULD PASS

    Goal: Mirror the declared CORS posture on the actual MCP POST response.

    Result: Verified (preflight 204 allow-origin https://example.com; post 401 allow-origin https://example.com)

    Resources: MDN CORS · Fix skill

    An MCP server card is published SHOULD PASS

    Goal: Publish a SEP-2127 server card for your MCP server and list it in your AI catalog.

    Result: Verified (https://mcp.notion.com/mcp/server-card -> 200)

    Resources: SEP-2127 · Server card discovery · AI catalog · Fix skill

    Legacy MCP card paths redirect to the canonical card MAY NONCOMPLIANT

    Evaluated at www.notion.so

    Goal: Point every legacy MCP card path at the canonical card instead of serving its own copy.

    Result: Works but does not conform (https://www.notion.so/.well-known/mcp.json -> 200 (200 serves content inline (ambiguous duplicate)))

    Fix: Serve whichever legacy pointer paths you publish (`/.well-known/mcp`, `/.well-known/mcp.json`, `/mcp.json`) as `301` redirects to `/.well-known/mcp/server-card.json`. A legacy path that answers with its own JSON body is a second source of truth that may drift from the canonical card, and a `302`/`307` or a redirect to any other location sends agents somewhere else. Paths you never published need no redirect.

    Resources: SEP-1649 · Fix skill

    A human/agent usage doc for the server resolves MAY N/A

    Evaluated at www.notion.so

    Goal: Publish a one-fetch markdown usage doc for your MCP server.

    Result: Not implemented, optional (https://www.notion.so/mcp-skill.md -> 404 (status 404 not in [200]))

    Resources: anc.dev example · Fix skill

    a 401 names the RFC 9728 metadata in its WWW-Authenticate challenge MAY PASS

    Goal: Name your protected-resource metadata in the WWW-Authenticate challenge of every 401.

    Result: Verified (resource_metadata names https://mcp.notion.com/.well-known/oauth-protected-resource/mcp)

    Resources: MCP authorization · RFC 9728 section 5.1 · Fix skill

    protected-resource metadata lists public https authorization_servers MAY PASS

    Goal: List the authorization servers that issue tokens for your MCP server in its RFC 9728 metadata.

    Result: Verified (authorization_servers: https://mcp.notion.com)

    Resources: RFC 9728 section 2 · MCP authorization · Fix skill

    a tools/list without an access token is refused with 401 MAY PASS

    Goal: Refuse every MCP request that carries no access token with 401.

    Result: Verified (refused with 401)

    Resources: MCP authorization · Fix skill

    Legacy lane · 2025-06-18

    10 not run

    initialize, then a session

    10 checks not run: mcp.notion.com requires sign-in N/A

    anc's public audit holds no sign-in for mcp.notion.com.

    initialize handshake returns serverInfo + protocolVersion MUST N/A

    Goal: Answer JSON-RPC initialize with serverInfo and protocolVersion so clients can begin a session.

    Result: Not evaluated: mcp.notion.com requires sign-in (HTTP 401 from https://mcp.notion.com/mcp)

    Resources: MCP lifecycle · Fix skill

    initialize advertises capabilities (tools / resources / prompts) SHOULD N/A

    Goal: Advertise the capability groups your MCP server implements in the initialize result.

    Result: Not evaluated: mcp.notion.com requires sign-in (https://mcp.notion.com/mcp)

    Resources: MCP lifecycle · Fix skill

    tools/list returns a tools array with input schemas MUST N/A

    Goal: Return tools/list entries with name, description, and a JSON inputSchema.

    Result: Not evaluated: mcp.notion.com requires sign-in (https://mcp.notion.com/mcp)

    Resources: MCP tools · Fix skill

    resources/list returns at least one resource when advertised SHOULD N/A

    Goal: Honor capabilities.resources with a non-empty resources/list result.

    Result: Not evaluated: mcp.notion.com requires sign-in (https://mcp.notion.com/mcp)

    Resources: MCP resources · Fix skill

    unknown JSON-RPC method returns -32601 SHOULD N/A

    Goal: Reject unknown JSON-RPC methods with error -32601 instead of a hang or 500.

    Result: Not evaluated: mcp.notion.com requires sign-in (HTTP 401 from https://mcp.notion.com/mcp)

    Resources: JSON-RPC 2.0 · Fix skill

    a non-JSON body draws -32700 (or a typed HTTP 400/415 refusal) SHOULD N/A

    Goal: Refuse an unparseable request body with a parse-error envelope or a typed HTTP refusal.

    Result: Not evaluated: mcp.notion.com requires sign-in (HTTP 401 from https://mcp.notion.com/mcp)

    Resources: JSON-RPC 2.0 · Fix skill

    a batch carrying a modern-envelope request is rejected -32600 SHOULD N/A

    Goal: Refuse JSON array batches that carry modern-era envelopes with -32600.

    Result: Not evaluated: mcp.notion.com requires sign-in (HTTP 401 from https://mcp.notion.com/mcp)

    Resources: JSON-RPC 2.0 · MCP transports (2026-07-28) · Fix skill

    tools/call with an unknown tool name returns -32602 SHOULD N/A

    Goal: Reject an unknown tool name with -32602 instead of a hang, a 500, or a fake result.

    Result: Not evaluated: mcp.notion.com requires sign-in (https://mcp.notion.com/mcp)

    Resources: MCP tools · JSON-RPC 2.0 · Fix skill

    a JSON-only Accept is answered without SSE framing SHOULD N/A

    Goal: Serve a single application/json response to a client whose Accept names only application/json.

    Result: Not evaluated: mcp.notion.com requires sign-in (https://mcp.notion.com/mcp)

    Resources: MCP transports · RFC 9110 section 12.5.1 (Accept) · Fix skill

    an unsatisfiable Accept draws a 406 rather than an unasked-for type SHOULD N/A

    Goal: Refuse an Accept you cannot satisfy with 406, never a 200 carrying a type the client did not request.

    Result: Not evaluated: mcp.notion.com requires sign-in (https://mcp.notion.com/mcp)

    Resources: RFC 9110 section 15.5.7 (406 Not Acceptable) · MCP transports · Fix skill

    Modern lane · 2026-07-28

    7 not run

    header-routed and stateless; no initialize or session

    7 checks not run: mcp.notion.com requires sign-in N/A

    anc's public audit holds no sign-in for mcp.notion.com.

    header-routed tools/list (2026-07-28) returns tools without initialize MUST N/A

    Goal: Answer a modern header-routed tools/list without requiring an initialize handshake.

    Result: Not evaluated: mcp.notion.com requires sign-in (https://mcp.notion.com/mcp)

    Resources: MCP lifecycle (2026-07-28) · MCP tools (2026-07-28) · Fix skill

    server/discover answers with server identity on the modern lane SHOULD N/A

    Goal: Answer server/discover with supported versions, capabilities, and server identity.

    Result: Not evaluated: mcp.notion.com requires sign-in (https://mcp.notion.com/mcp)

    Resources: MCP lifecycle (2026-07-28) · Fix skill

    an unknown method on the modern lane returns -32601 SHOULD N/A

    Goal: Reject unknown header-routed methods with -32601 on the 2026-07-28 lane.

    Result: Not evaluated: mcp.notion.com requires sign-in (HTTP 401 from https://mcp.notion.com/mcp)

    Resources: JSON-RPC 2.0 · MCP lifecycle (2026-07-28) · Fix skill

    _meta missing clientCapabilities is rejected (-32602 or -32600) SHOULD N/A

    Goal: Enforce the mandatory clientCapabilities key on every modern request.

    Result: Not evaluated: mcp.notion.com requires sign-in (HTTP 401 from https://mcp.notion.com/mcp)

    Resources: MCP lifecycle (2026-07-28) · Fix skill

    an Mcp-Method header disagreeing with the body method draws -32020 SHOULD N/A

    Goal: Validate the SEP-2243 header mirror between Mcp-Method and the body method.

    Result: Not evaluated: mcp.notion.com requires sign-in (HTTP 401 from https://mcp.notion.com/mcp)

    Resources: MCP lifecycle (2026-07-28) · Fix skill

    an unsupported protocol version is rejected -32022 with data.supported SHOULD N/A

    Goal: Refuse unsupported protocol version claims with -32022 and advertise the served revisions.

    Result: Not evaluated: mcp.notion.com requires sign-in (HTTP 401 from https://mcp.notion.com/mcp)

    Resources: MCP lifecycle (2026-07-28) · Fix skill

    modern resources/read with an unknown URI returns -32602 SHOULD N/A

    Goal: Answer an unknown resource URI with the typed miss code, not a hang or a fake result.

    Result: Not evaluated: mcp.notion.com requires sign-in (https://mcp.notion.com/mcp)

    Resources: MCP resources (2026-07-28) · JSON-RPC 2.0 · Fix skill

    In-page tools · WebMCP

    browser tools exposed by the site's HTML, not by the MCP server

    Root HTML exposes WebMCP browser tools MAY N/A

    Evaluated at www.notion.so

    Goal: Expose page tools to browser agents via WebMCP.

    Result: Not implemented, optional (https://www.notion.so/ -> 200 (no WebMCP markers in root HTML))

    Resources: WebMCP spec · Fix skill

    partial
  6. C6

    Agent discovery & auth

    2 / 2 checks pass

    Evaluated at mcp.notion.com, declared by notion.so's ai-catalog entry

    OAuth/OIDC discovery metadata published MAY N/A

    Evaluated at www.notion.so

    Goal: Publish OAuth/OIDC discovery metadata if agents authenticate to your service.

    Result: Not implemented, optional (https://www.notion.so/.well-known/openid-configuration -> 404 (status 404 not in [200]))

    Resources: RFC 8414 · Fix skill

    /.well-known/ai-catalog.json published (ARD) MAY PASS

    Evaluated at www.notion.so

    Goal: Publish an Agentic Resource Discovery catalog so agents can enumerate your AI artifacts.

    Result: Verified (https://www.notion.so/.well-known/ai-catalog.json -> 200)

    Resources: AI Catalog · Fix skill

    OAuth Protected Resource Metadata published (RFC 9728) MAY PASS

    Goal: Publish RFC 9728 protected-resource metadata for your authenticated MCP server.

    Result: Verified (https://mcp.notion.com/.well-known/oauth-protected-resource -> 200)

    Resources: RFC 9728 · Fix skill

    A2A Agent Card published for agent-to-agent discovery MAY N/A

    Evaluated at www.notion.so

    Goal: Publish an A2A Agent Card for agent-to-agent discovery.

    Result: Not implemented, optional (https://www.notion.so/.well-known/agent-card.json -> 404 (status 404 not in [200]))

    Resources: A2A protocol · Fix skill

    Agent auth/registration metadata doc published MAY N/A

    Evaluated at www.notion.so

    Goal: Publish an auth.md telling agents how to obtain credentials.

    Result: Not implemented, optional (https://www.notion.so/.well-known/auth.md -> 404)

    Resources: anc.dev example · Fix skill

    Agent-skills discovery index published MAY N/A

    Evaluated at www.notion.so

    Goal: Publish an agent-skills discovery index so agents can enumerate your skills.

    Result: Not implemented, optional (https://www.notion.so/.well-known/agent-skills/index.json -> 404 (status 404 not in [200]))

    Resources: Agent Skills Discovery · Fix skill

    pass

Scored against registry 58718e156460.

This scorecard reflects the target's public agent-facing surface and the hosts it declares at audit time. Re-audit from the control above to refresh it, or call the audit_website MCP tool.