prometheus.services

only 0 characters of readable text in the served HTML

Fix: Server-render the homepage's core content (SSR, static export, or prerendering). A client-rendered shell is empty to every agent.

no JSON-LD blocks on the homepage

Fix: Add a JSON-LD block (schema.org Organization or SoftwareApplication) so agents get your name, description and links as data rather than prose.

/llms-full.txt not served

Fix: Optional but cheap: publish /llms-full.txt with your docs inlined as one markdown file, so an agent can read everything in a single fetch.

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.0 — 0 readable chars in 12345 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.

5949 characters of text at /docs

HTTP 200 for / (agent UA)

https://www.prometheus.services/

HTTP 200, 4244 bytes

5 sampled link(s) all resolve

has headings and markdown links

both User-Agents got HTTP 200

0 redirect(s)

HTTP 401 — the endpoint requires credentials to initialize

Fix: Let unauthenticated clients complete `initialize` and `tools/list`, and require auth only on `tools/call`. An agent that cannot see your tools cannot decide to use them.

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.

HTTP 200, 5845 bytes

/docs → HTTP 200

2 scheme(s): apiKey, cognitoIdToken

78/78 operations described (100%)

HTTP 200, 761768 bytes of JSON

307 error response(s) with a schema

OpenAPI 3.1.0, 78 path(s)

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 agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.

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

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