---
title: "Waymark report for tavily.com"
canonical: "https://waymark.genedai.me/score/tavily.com"
last-updated: "2026-08-25T04:41:29.789Z"
---

# Waymark report for tavily.com

Waymark scored tavily.com 85/100 (B) on 25 Aug 2026.
Score: 85/100 — Usable with gaps
Scanned: 2026-08-25T04:41:29.789Z
Canonical report: https://waymark.genedai.me/score/tavily.com

## Layer breakdown

- Discovery: 17/20 (15 of 20 eligible checks passed)
- Access: 23.9/30 (25 of 37 eligible checks passed)
- Usability: 34/40 (25 of 31 eligible checks passed)
- Payments: 10/10 (2 of 2 eligible checks passed)

## Findings

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

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

### 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. OAuth / OIDC well-known

- Layer: access
- Result: failed
- Evidence: No oauth-authorization-server or openid-configuration.
- Recommended fix: Publish /.well-known/openid-configuration or oauth-authorization-server if you authenticate agents.

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

### 8. Markdown negotiation

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

### 9. /index.md fallback

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

### 10. ai-plugin.json

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

### 11. security.txt

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

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

### 13. Idempotency signal

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

### 14. Sitemap lastmod

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

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

### 16. llms.txt links resolve

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

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

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

### 19. Registry branding

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

### 20. Function calling compatibility

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

### 21. Multi-language SDK packages

- Layer: usability
- Result: partial
- Evidence: npm matches; second ecosystem homepage does not.
- Recommended fix: Publish official SDK packages on npm and PyPI whose homepage is this domain.

### 22. MCP resources exposed

- Layer: usability
- Result: failed
- Evidence: resources capability advertised but resources/list was empty.
- Recommended fix: If initialize advertises resources, resources/list should return at least one. Omit the capability if you are tool-only.

### 23. MCP error handling

- Layer: usability
- Result: failed
- Evidence: Bad tools/call did not return a JSON-RPC error object.
- Recommended fix: Return structured JSON-RPC errors (code and message) for invalid tools or arguments.

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