Frozen archive
This report was produced on September 23, 2026. Scans are no longer run, and www.agentlitmus.com may have changed since.
This scan completed with notes
- Followed redirect to the canonical host: https://www.agentlitmus.com
www.agentlitmus.com
Scanned on September 23, 2026
Followed redirect to https://www.agentlitmus.com
97/100
Signal breakdown
The score above combines two different things: whether an agent can understand this site at all, and whether the site has adopted the emerging optional agent conventions. They're grouped separately here because a site can be excellent at one and have none of the other.
Comprehension
Whether an agent can read and understand the page at all.
58/58(100%)
Agent convention adoption
Whether the site has adopted the emerging optional agent conventions.
39/42(93%)
Tap a row to see how to fix it.
Agent Security
Low exposureWhat an agent could harvest, post, or be tricked into on this site.
Exposure to agents
100/100
Secrets, write surfaces, and exposed paths.
Exposure of agent visitors
100/100
Hidden text and prompt-injection payloads.
Info (4)
- Policy declared for user-triggered agent fetchersInfo
robots.txt names ChatGPT-User.
user-triggered: ChatGPT-User
Fix: No action needed.
- Edge protection observedInfo
Response headers indicate a CDN or WAF in front of the origin: Vercel.
Vercel
Fix: No action needed.
- Web Bot Auth: not verifiable passivelyInfo
Whether this site verifies signed agent requests (Web Bot Auth) cannot be determined without sending signed requests, which a passive scan does not do.
not tested — passive scan
Fix: No action needed. AgentLitmus plans to publish a signing key directory and sign its scans, which will make this checkable.
- Agent descriptor at /.well-known/mcp.json is read-only and unauthenticatedInfo
/.well-known/mcp.json declares no authentication scheme, but every advertised operation appears read-only (4 operation(s)). This is a legitimate design for public data — the operative question is whether the underlying data is meant to be public, not whether the endpoint is authenticated.
GET /.well-known/mcp.json -> 200, no auth scheme; read-only operations: scan_site, get_scan_report, get_domain_history, diff_scans
Fix: No action needed if this data is intended to be public. If any of it is not, add authentication.
Hardening checklist
3 of 9 presentRecommended declarations and headers. These don't affect the exposure score — their absence means something isn't declared, not that an agent could exploit it.
- security.txt published: absent — Publish /.well-known/security.txt with a Contact field and a future Expires date.
- Content usage preferences declared: absent — Declare preferences via Content-Signal lines in robots.txt or a Content-Usage response header.
- Content-Security-Policy header: absent — Add a Content-Security-Policy restricting script-src to sources you control.
- Strict-Transport-Security header: present
- X-Content-Type-Options header: absent — Add X-Content-Type-Options: nosniff.
- Referrer-Policy header: absent — Add Referrer-Policy: strict-origin-when-cross-origin.
- Permissions-Policy header: absent — Add a Permissions-Policy disabling browser features your site doesn't use.
- HTTPS with http redirect: present
- Source maps withheld from production: present
Secondary AI review (advisory)
gemini-3.1-pro-preview · okModel-generated observations, not verified findings. They do not affect the score or any label above.
No additional observations.
Adversarial Safety
CleanChecks for hidden text and prompt-injection payloads that could hijack an AI agent reading this site.
No hidden text or injection patterns detected.
Do these first
The highest-impact fixes, ranked by points left on the table.
- 1llms.txt+3 pts available
Ensure /llms.txt starts with a '# Title' heading, includes markdown links ([label](url)), and that those links point to pages on your own domain.
Scanned by AgentLitmusBot. Methodology v0.1. Source. All archived reports.