---
title: "Waymark report for navattic.com"
canonical: "https://waymark.genedai.me/score/navattic.com"
last-updated: "2026-08-26T16:27:11.853Z"
---

# Waymark report for navattic.com

Waymark scored navattic.com 74.9/100 (B) on 26 Aug 2026.
Score: 74.9/100 — Usable with gaps
Scanned: 2026-08-26T16:27:11.853Z
Canonical report: https://waymark.genedai.me/score/navattic.com

## Layer breakdown

- Discovery: 15/20 (12 of 20 eligible checks passed)
- Access: 25.1/30 (29 of 40 eligible checks passed)
- Usability: 27.4/40 (20 of 30 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. Well-known AI catalog

- Layer: discovery
- Result: failed
- Evidence: No ai-plugin.json or ai-catalog.json.
- Recommended fix: Add /.well-known/ai-plugin.json or /.well-known/ai-catalog.json.

### 3. RSS or Atom feed

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

### 4. CSP or X-Frame-Options

- Layer: access
- Result: failed
- Evidence: Neither CSP nor X-Frame-Options on homepage.
- Recommended fix: Send Content-Security-Policy or X-Frame-Options.

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

### 7. llms-full.txt

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

### 8. ai-plugin.json

- Layer: discovery
- Result: failed
- Evidence: No /.well-known/ai-plugin.json.
- Recommended fix: Optionally publish a plugin-style capability manifest.

### 9. security.txt

- Layer: access
- Result: failed
- Evidence: No /.well-known/security.txt Contact.
- Recommended fix: Publish /.well-known/security.txt with a Contact field.

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

### 11. Web app manifest

- Layer: access
- Result: partial
- Evidence: manifest link without a fetchable file.
- Recommended fix: Host /manifest.webmanifest if the site is installable.

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

### 13. Idempotency signal

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

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

### 15. CLI tool

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

### 16. JSON-LD sameAs

- Layer: access
- Result: failed
- Evidence: JSON-LD without sameAs.
- Recommended fix: Add sameAs profile URLs.

### 17. Sitemap lastmod

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

### 18. Package homepage match

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

### 19. Agent instruction / when-to-use

- Layer: access
- Result: failed
- Evidence: Agent file exists without when-to-use guidance.
- Recommended fix: Tell agents when to reach for you: add a 'when to use this' section to your llms.txt (or a dedicated agent-instructions file) that names your best-fit use cases.

### 20. Organization schema completeness

- Layer: access
- Result: failed
- Evidence: Organization JSON-LD missing contactPoint and address.
- Recommended fix: Add Organization JSON-LD that includes both contactPoint (with email/phone and contactType) and address (PostalAddress).

### 21. llms.txt links resolve

- Layer: access
- Result: partial
- Evidence: 7 real, 1 homepage-shell, 0 dead of 8 sampled links.
- Recommended fix: Make every link your llms.txt declares resolve to real content, not a homepage shell 200.

### 22. Markdown frontmatter metadata

- Layer: access
- Result: failed
- Evidence: Served markdown has no YAML frontmatter block.
- Recommended fix: Open served markdown with a --- frontmatter block carrying title plus description, canonical, or last-updated.

### 23. Accessible document structure

- Layer: usability
- Result: partial
- Evidence: Landmarks partial (main=true nav=true h1=true skip=true).
- Recommended fix: Give the homepage a main region, nav, H1, and a heading order that does not skip levels.

### 24. Registry branding

- Layer: discovery
- Result: failed
- Evidence: MCP card missing description, icon.
- Recommended fix: Give your MCP server-card a display name, an icon or logo, and a description.

### 25. REST typed error model

- Layer: usability
- Result: failed
- Evidence: OpenAPI 4xx/5xx responses lack a typed error schema.
- Recommended fix: Document 4xx and 5xx responses with a typed error schema (or RFC 9457 problem+json).

### 26. REST versioning / deprecation policy

- Layer: usability
- Result: failed
- Evidence: OpenAPI has no versioning or deprecation signal.
- Recommended fix: Version your API (path or header) and publish how you signal deprecation.

### 27. REST response schema coverage

- Layer: usability
- Result: failed
- Evidence: Few operations declare typed success response schemas.
- Recommended fix: Define typed JSON response schemas for endpoints in your OpenAPI spec.

### 28. Function calling compatibility

- Layer: usability
- Result: partial
- Evidence: Spec is missing unique operationIds/descriptions for function calling.
- Recommended fix: Give endpoints unique operationIds, typed schemas, and descriptions for function calling.

### 29. Multi-language SDK packages

- Layer: usability
- Result: failed
- Evidence: No npm+PyPI official packages whose homepage is this domain.
- Recommended fix: Publish official SDK packages on npm and PyPI 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.