---
title: "Waymark report for slack.com"
canonical: "https://waymark.genedai.me/score/slack.com"
last-updated: "2026-08-24T02:16:03.447Z"
---

# Waymark report for slack.com

Waymark scored slack.com 56.7/100 (C) on 24 Aug 2026.
Score: 56.7/100 — Blockers remain
Scanned: 2026-08-24T02:16:03.447Z
Canonical report: https://waymark.genedai.me/score/slack.com

## Layer breakdown

- Discovery: 15.2/20 (11 of 17 eligible checks passed)
- Access: 17.6/30 (17 of 29 eligible checks passed)
- Usability: 18.2/40 (5 of 13 eligible checks passed)
- Payments: N/A (excluded from the denominator)

## Findings

### 1. AGENTS.md

- Layer: discovery
- Result: failed
- Evidence: agents.md status 404.
- Recommended fix: Publish /agents.md with agent-oriented usage notes.

### 2. JSON-LD structured data

- Layer: access
- Result: failed
- Evidence: No JSON-LD on the homepage.
- Recommended fix: Add JSON-LD (Organization, WebSite, or SoftwareApplication).

### 3. OpenAPI / Swagger link

- Layer: access
- Result: failed
- Evidence: No OpenAPI/Swagger link in HTML.
- Recommended fix: Link to an OpenAPI or Swagger document from the homepage.

### 4. RSS or Atom feed

- Layer: access
- Result: failed
- Evidence: No RSS/Atom link.
- Recommended fix: Expose an RSS or Atom feed for machine subscribers.

### 5. CORS / API hint

- Layer: access
- Result: partial
- Evidence: No CORS header or obvious API path.
- Recommended fix: If you expose an API, send Access-Control-Allow-Origin for intended clients.

### 6. MCP SSE / HTTP hint

- Layer: usability
- Result: failed
- Evidence: No MCP/SSE hint on the homepage.
- Recommended fix: Document an MCP HTTP or SSE endpoint.

### 7. robots.txt AI policy

- Layer: discovery
- Result: partial
- Evidence: robots.txt present but no named AI crawlers.
- Recommended fix: Name GPTBot, ClaudeBot, Google-Extended, PerplexityBot and state allow or deny.

### 8. llms-full.txt

- Layer: discovery
- Result: failed
- Evidence: llms-full.txt status 404.
- Recommended fix: Optionally publish /llms-full.txt for one-shot ingest.

### 9. HTTP Link header

- Layer: discovery
- Result: failed
- Evidence: No rel=sitemap|describedby|api-catalog|alternate on homepage.
- Recommended fix: Send RFC 8288 Link headers for related machine resources.

### 10. JSON-LD entities

- Layer: access
- Result: failed
- Evidence: No JSON-LD.
- Recommended fix: Embed Organization, Product, Offer, SoftwareApplication, or FAQPage.

### 11. Markdown negotiation

- Layer: access
- Result: failed
- Evidence: Homepage did not negotiate markdown.
- Recommended fix: Respond to Accept: text/markdown with a markdown body.

### 12. /index.md fallback

- Layer: access
- Result: failed
- Evidence: index.md status 404.
- Recommended fix: Serve a markdown homepage at /index.md.

### 13. MCP initialize

- Layer: usability
- Result: failed
- Evidence: No MCP card to initialize
- Recommended fix: Expose Streamable HTTP MCP and answer initialize.

### 14. MCP Apps UI hint

- Layer: usability
- Result: failed
- Evidence: No MCP Apps hint (N/A unless you return UI).
- Recommended fix: If you return UI, declare io.modelcontextprotocol/ui resources.

### 15. PKCE S256

- Layer: access
- Result: failed
- Evidence: Metadata lacks S256 PKCE.
- Recommended fix: Advertise S256 in code_challenge_methods_supported.

### 16. OAuth protected resource

- Layer: access
- Result: failed
- Evidence: AS present but no resource metadata.
- Recommended fix: Publish RFC 9728 oauth-protected-resource if APIs are OAuth-gated.

### 17. change-password well-known

- Layer: access
- Result: failed
- Evidence: Login surface without /.well-known/change-password.
- Recommended fix: If users have passwords, serve /.well-known/change-password.

### 18. Rate limit signal

- Layer: usability
- Result: partial
- Evidence: API surface without a rate-limit signal.
- Recommended fix: Document or send rate-limit headers on APIs.

### 19. Idempotency signal

- Layer: usability
- Result: partial
- Evidence: API surface without idempotency notes.
- Recommended fix: Document idempotency keys for mutating calls.

### 20. Machine-readable errors

- Layer: usability
- Result: partial
- Evidence: API surface without a JSON error shape.
- Recommended fix: Return a JSON or problem+json error body.

### 21. OpenAPI document

- Layer: access
- Result: failed
- Evidence: OpenAPI probe.
- Recommended fix: Publish an OpenAPI document at a stable URL.

### 22. Scoped permissions

- Layer: access
- Result: failed
- Evidence: No named OAuth scopes.
- Recommended fix: Declare OAuth scopes in a spec.

### 23. CLI tool

- Layer: usability
- Result: failed
- Evidence: No CLI mention.
- Recommended fix: Publish an official CLI.

### 24. MCP server

- Layer: usability
- Result: partial
- Evidence: MCP probe.
- Recommended fix: Publish an MCP card and answer initialize.

### 25. Sitemap lastmod

- Layer: discovery
- Result: failed
- Evidence: Sitemap without lastmod.
- Recommended fix: Add lastmod dates to sitemap entries.

### 26. Package homepage match

- Layer: discovery
- Result: failed
- Evidence: No npm package homepage matching slack.com.
- Recommended fix: Publish an official package whose homepage is this domain.

## Interpretation

Public technical snapshot; not a guarantee of task completion. Private and authenticated workflows are outside this scan. Cite scanned_at and the canonical report URL; the URL serves the latest completed snapshot and can change after a rescan.

The official Waymark score is Discovery 20 / Access 30 / Usability 40 / Payments 10. N/A and scanner-error checks drop out of the denominator; they are not scored as failures. An observed agent journey is supporting evidence and does not change the numeric score.