How do I use agent-ready-mcp?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@agent-ready-mcp scan https://example.com for agent-readiness" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

agent-ready-mcp

by VeldinS

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

agent-ready

agent-ready: 100/100 npm version License: MIT

Make any website agent-ready in one command. Scan a site, get an agent-readiness score, and auto-generate the two things the agentic web now expects — an llms.txt and a WebMCP tool scaffold — so AI agents can understand and act on your site instead of blindly scraping it.

npx agent-readiness https://yoursite.com

No install? Scan any site in your browser at agent-ready-web.vercel.app — paste a URL, get the score + per-check breakdown, and download the generated llms.txt + WebMCP scaffold.

agent-ready — scanning https://yoursite.com

  ✗ llms.txt present (0/22)
     → Add /llms.txt so agents get a clean, token-cheap map of your site (generated below).
  ✗ WebMCP tools (document.modelContext) (0/22)
     → Expose your key actions as WebMCP tools so agents can ACT, not just scrape (scaffold generated below).
  ✔ Structured data (JSON-LD / OpenGraph) (+13/13)
  ✔ Semantic landmarks + an H1 (+13/13)
  ✔ Title + meta description (+10/10)
  ✗ robots.txt + sitemap.xml (0/8)
  ✔ Canonical URL (<link rel="canonical">) (+4/4)
  ✔ Document language (<html lang>) (+4/4)
  ✔ Image alt-text coverage (18/20, 90%) (+4/4)

  Agent-Readiness: 48/100
  pages: 17  •  forms: 2  •  inferred actions: 3
  Generated → ./agent-ready-out/llms.txt, ./agent-ready-out/webmcp.tools.js, ./agent-ready-out/structured-data.html, ./agent-ready-out/agent-ready.json

Why this exists

Chrome's Lighthouse now ships an "Agentic Browsing" audit in the default config (13.3, May 2026), and WebMCP is a W3C draft in origin trial. Millions of sites are about to see a failing agent-readiness grade with no obvious way to fix it. agent-ready is the fix: it doesn't just diagnose (every scanner does that) — it generates the artifacts and is built to run in CI.

llms.txt — a clean, machine-readable map of your pages (with one-line summaries) and actions, built from a multi-page crawl (the emerging standard agents read first).
webmcp.tools.js — a WebMCP scaffold that registers each <form> and inferred action (search / login / signup / cart / checkout / contact / subscribe) as a callable agent tool via document.modelContext.registerTool(...), so an agent can complete the signup / search / booking instead of guessing at your DOM.
structured-data.html — a JSON-LD + OpenGraph snippet to drop into your <head> so machines get explicit, structured meaning.

Related MCP server: agent-readiness-auditor

One command, one PR (the fixer)

Every other tool scans. agent-ready also fixes — and opens the fix as a pull request:

npx agent-readiness fix ./my-site --pr

It detects your framework (Next.js App/Pages Router, Vite, or plain static HTML), writes llms.txt + webmcp.tools.js into the right place, injects the <script> tag and the missing <html lang> / meta description / JSON-LD + OpenGraph into your entry HTML or layout, then branches, commits, and opens a PR with a clear before → after score:

agent-ready fix — ./my-site

  Framework: Static / plain HTML
  Score: 17/100 → 88/100

  Files:
    + llms.txt          (token-cheap site map for agents)
    + webmcp.tools.js   (WebMCP tool scaffold)
    inject → index.html (html-lang, meta-description, structured-data, webmcp-script)

  ✔ Opened pull request: https://github.com/you/my-site/pull/42

--dry-run — print the plan (and the exact git/gh commands) without touching anything.
--url https://yoursite.com — scan the live site for a richer llms.txt (multi-page) and to fill real URLs + a canonical tag.
--base <branch> / --branch <name> — control the PR target and head branch.
Injection is idempotent — re-running never duplicates a tag. --pr needs a git repo with an origin remote and the gh CLI authenticated.

Prefer to apply locally without a PR? agent-ready fix ./my-site writes + injects in place; agent-ready <url> --apply ./my-site just drops the files into public/.

Use it in CI (GitHub Action)

permissions:
  contents: read
  pull-requests: write   # so it can comment the score on the PR
steps:
  - uses: VeldinS/agent-ready@v0
    with:
      url: https://yoursite.com
      comment: true        # post a sticky agent-readiness comment on the PR (default)
      min-score: 60        # optional: fail the job if the score drops below this

On every pull request it posts (and updates) a single comment with the score and per-check breakdown. Add the badge to your README once you're green:

![agent-ready](https://img.shields.io/badge/agent--ready-100%2F100-brightgreen)

Use it from your agent (MCP server)

Run "make my site agent-ready" right inside Claude Code / Cursor / Claude Desktop. The @veldins/agent-ready-mcp server exposes two tools — scan_site (score + per-check breakdown) and generate_fixes (the llms.txt + WebMCP scaffold + structured-data contents) — over stdio, sharing the same scanner core.

claude mcp add agent-ready -- npx -y @veldins/agent-ready-mcp

{ "mcpServers": { "agent-ready": { "command": "npx", "args": ["-y", "@veldins/agent-ready-mcp"] } } }

What it checks

Check	Weight
`llms.txt` present	22
WebMCP tools (`document.modelContext`)	22
Structured data (JSON-LD / OpenGraph)	13
Semantic landmarks + an `<h1>`	13
Title + meta description	10
`robots.txt` + `sitemap.xml`	8
Canonical URL (`<link rel="canonical">`)	4
Document language (`<html lang>`)	4
Image alt-text coverage (≥80%)	4

The score reflects the server-rendered HTML an agent first sees; heavily client-rendered SPAs will under-report content checks until they ship meaningful HTML.

Roadmap

fix mode: write + inject the artifacts and open a PR with a before → after score
Framework adapters (Next.js App/Pages Router, Vite, static HTML)
GitHub Action comments the score on every PR
Web scanner page: paste a URL → scored report + downloadable fixes (no install)
MCP server so Claude Code / Cursor can run "make my site agent-ready" (@veldins/agent-ready-mcp)
Re-grade against live Lighthouse Agentic Browsing on each PR

Local dev

npm install
node bin/agent-ready.mjs examples/sample-site.html
npm test          # node --test — fixtures, generators, crawl, CLI

One runtime dependency (node-html-parser); Node ≥20.19; ESM; no build step.

MIT.

This server cannot be deployed

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

Need Help?

Related Servers

Related MCP Connectors

AgentGrade A
com.agentgrade
Scan any website for AI agent readiness, payment protocols, and discovery endpoints
Web Scraping AI & Machine Learning Agent Orchestration
43
AI Readiness Kit A
io.github.silverbackmarketing
Generate 18 AI readiness files (llms.txt, ai.txt, RAG indexes, schema) for any website.
RAG Systems Search Knowledge & Memory
623
agent-ready-kit A
com.mudko
Agent-readiness scanner (0-5 score), robots.txt + llms.txt generators, managed agent enablement.
Agent Orchestration Browser Automation Developer Tools
262
Myagi - Open Agent Registry A
bot.myagi
Score any website's AI-agent readiness. Open Agent Registry scanner + platform tools.
Browser Automation Agent Orchestration
32

Related MCP Servers

maxaeo-ai-visibility-mcp
Web Scraping Search
maxaeo
A
license
A
quality
B
maintenance
Enables AI agents to check whether a public website is crawlable, understandable, and ready for AI search workflows through local-only audits of robots.txt, sitemaps, metadata, and llms.txt.
Updated a month ago (2026-08-26 07:56 UTC)
3
72 npm
1
MIT
agent-readiness-auditor
Web Scraping Security
asish-singh
A
license
Not graded
quality
A
maintenance
Scans a website to score its compatibility and safety for AI agents, and exposes an audit tool via the Model Context Protocol.
Updated 2 months ago (2026-07-12 00:08 UTC)
21 npm
1
MIT
ai-agent-layer
RAG Systems Web Scraping Knowledge & Memory
mhsh77
F
license
Not graded
quality
C
maintenance
Enables AI agents to interact with any website through MCP, providing structured knowledge graph contexts, generated actions, and readiness scoring.
Updated a month ago (2026-08-07 14:06 UTC)
-
Engawa
Browser Automation Search
thierry-gilgen-ict
A
license
Not graded
quality
C
maintenance
Enables websites to expose a first-class interface for AI agents by providing read-only MCP tools like search_site and generating llms.txt discovery files.
Updated 2 days ago (2026-09-19 09:06 UTC)
2 npm
5
MIT