Why we think this is Replit (1 signals)
- · bare 'replit' mention in HTML
1 failed out of 9 that apply to your site.
Quick Wins
Top 1 fixes ranked by score impact
- 01Fail+4 pts if fixed
OAuth discovery metadata
See full detailsPublish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.
# Task: raise AIScan agent-readiness score Site: https://aiscan.site/ Platform: replit (30% confidence) AIScan score: 88/100 — Level 4 (Interactive) Rubric: v2026-06-08.1 Implement the fixes below in this repository. Make atomic commits per check id. After all edits, run the build to confirm nothing breaks. ## Failing checks - **[P4] OAuth discovery metadata** — FAIL - Evidence: auth-server: 404, protected-resource: 404 - Fix: Publish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints. ## Notes - Treat `public/` (or framework equivalent) as the source for `robots.txt`, `llms.txt`, and `.well-known/` files. - For Markdown content negotiation, respond to `Accept: text/markdown` and `?format=md` on canonical content URLs. - For MCP / Agent Skills, drop card files under `.well-known/` even if the server isn't live yet — discovery matters first.
Discoverability
100Can agents find your pages? robots, sitemaps, llms.txt.
Content
100Can agents read your content cleanly? Markdown, structured data.
Bot Access
100Are AI crawlers explicitly allowed or blocked?
Capabilities
69Can agents do things? APIs, auth, MCP, Agent Skills.
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · P4
What we foundauth-server: 404, protected-resource: 404
How to fix itPublish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.
1.⚡ Fix automatically with AIScanThe fastest way to apply this fix is using AIScan's own agent tooling — it gives any AI coding assistant machine-readable instructions for this exact check. **Option A — Claude Code skill** 1. Download `CLAUDE.md` from https://aiscan.site/CLAUDE.md and drop it into your project root. 2. Ask Claude Code: *"Fix the failing AIScan check for <your-url>"* — it will read the skill, call our API, and apply the fix. **Option B — MCP (any MCP-compatible agent: Claude Desktop, Cursor, etc.)** - Endpoint: `https://aiscan.site/api/mcp` - Tools: `scan_website`, `get_fixes`, `get_grade` - Call `get_fixes` with your URL for machine-readable fix instructions. **Option C — REST API (any tool / script)** ``` GET https://aiscan.site/api/public/scan?url=YOUR_URL ``` Returns the full report including failing checks and fix details. Then re-scan at https://aiscan.site to verify.
2.This is a Replit projectStatic files (`robots.txt`, `llms.txt`, `.well-known/*`) go in the `public/` folder. Edit them in the Replit IDE, or ask Replit AI / Agent to apply the fixes for you.
3.Publish OAuth discovery metadataIf your API supports OAuth, serve RFC 8414 metadata at `/.well-known/oauth-authorization-server` and/or RFC 9728 at `/.well-known/oauth-protected-resource`.
4.VerifyAfter deploying, re-scan at https://aiscan.site. You can also test with `curl -I` or `curl` directly.
Embed your AIScan badge
Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of aiscan.site on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2Faiscan.site%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade A (88/100) — AIScan.site"> <img src="https://aiscan.site/api/public/badge.svg?score=88&grade=A&host=aiscan.site" alt="AIScan.site Grade A — 88/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2Faiscan.site%2F)
Track this over time
Coming soon: save sites, schedule re-scans, get email when something material changes. Standards land weekly — your tracker shouldn't be one-shot.
Scan your own site
Get a plain-English agent-readiness report you can hand straight to ChatGPT or Claude.
Scan your site