tavily.com

no link to an API reference in the homepage HTML

Fix: If you have an API, link its reference from the homepage. If you don't, this check is safe to ignore.

title is only 6 characters: 'Tavily'

Fix: Expand the <title> to 10–70 characters naming the product and what it does.

https://tavily.com

3 docs link(s), e.g. https://docs.tavily.com

131 characters

og:title and og:description present

all 6 agent crawlers may fetch /

HTTP 200, 379 bytes

robots.txt has a Sitemap: line

70 URL(s) listed

search-based checks are deferred — excluded from the score

registry lookup not implemented in v1 — excluded from the score rather than guessed

Accept: text/markdown → text/html; charset=utf-8

Fix: Optional but increasingly expected: honour `Accept: text/markdown` by serving a markdown rendering of the page, so agents skip HTML parsing entirely.

ratio 0.0261 — 3479 readable chars in 133356 bytes of HTML

Fix: Most of what you serve is markup and inline script rather than content. Reduce inline payloads or server-render more text so the signal-to-noise ratio favours readers.

HTTP 200 for / (agent UA)

https://www.tavily.com/

2 valid block(s) (WebPage)

HTTP 200, 802321 bytes

HTTP 200, 16970 bytes

5 sampled link(s) all resolve

has headings and markdown links

both User-Agents got HTTP 200

3479 characters of text in the served HTML

1 redirect(s)

/docs not served (HTTP 404) — docs may live on another path or host

handshake failed: HTTP 404

Fix: Make https://www.tavily.com/mcp answer a streamable-HTTP `initialize` request. Check that POST is allowed, that `Accept: application/json, text/event-stream` is honoured, and that the response is a JSON-RPC envelope.

/docs → HTTP 404

Fix: Serve docs at the conventional /docs path, or redirect it to wherever they live. Agents try conventional paths first.

404 returns HTML, not a machine-readable body

Fix: Content-negotiate your errors: return a JSON body with a stable `code` (and a `next_action` where recovery exists) to clients that ask for JSON.

/openapi.json not served (HTTP 404)

Fix: If you have an HTTP API, publish its OpenAPI document at a predictable path (/openapi.json). It is the difference between an agent reading your contract and an agent guessing it. If you have no HTTP API, ignore this.

HTTP 200, 10883 bytes

HTTP 200, valid JSON

/api → HTTP 404 (no API at the conventional root)

no listed MCP tools to inspect

no listed MCP tools to inspect

handshake did not complete, so tools/list was not reached

no parseable OpenAPI document

no parseable OpenAPI document

no parseable OpenAPI document

no parseable OpenAPI document

x402 is declared but no probed endpoint answered HTTP 402

Fix: Your documents advertise x402 but the endpoints do not issue a 402 challenge. Return 402 with the challenge on metered endpoints, or drop the claim.

x402 referenced in a published document (x402)

no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.