GenReady

io.github.odb366Published by GitHub account odb366v1.2.5Updated Oct 29, 2026

Scan a website for AI search and agent readiness, then get a fix checklist for your agent.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingAI & ML

Overview

GenReady's hosted MCP server (genready.ai); OAuth sign-in or API key required; Streamable HTTP; 12 tools.

No AI overview yet: these facts come from the registry entry and the server itself.

Endpoint
genready.ai
Last checked

Installation

In SourceWeft

  1. Open GenReady in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.odb366%2Fgenready/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "genready": {
      "type": "http",
      "url": "https://genready.ai/mcp"
    }
  }
}

README

@genready/mcp-server

Connect GenReady to your AI assistant or coding agent. Scan any page for readiness to be cited by AI search engines and used by AI agents, then hand the fix checklist straight to your agent.

1. Get an API key

Create one at genready.ai/api-keys. To read site-wide fix plans, enable Read site data (domain:read) when you create it.

2. Connect

Remote (recommended, nothing to install)

Any client that supports remote MCP servers over Streamable HTTP can connect directly:

  • URL: https://genready.ai/mcp
  • Header: Authorization: Bearer gr_live_your_key_here

Claude Code:

bash
claude mcp add --transport http genready https://genready.ai/mcp \  --header "Authorization: Bearer gr_live_your_key_here"

Cursor (.cursor/mcp.json):

json
{  "mcpServers": {    "genready": {      "url": "https://genready.ai/mcp",      "headers": { "Authorization": "Bearer gr_live_your_key_here" }    }  }}

Local command (stdio)

For clients that only launch local commands, such as Claude Desktop:

json
{  "mcpServers": {    "genready": {      "command": "npx",      "args": ["-y", "@genready/mcp-server"],      "env": { "GENREADY_API_KEY": "gr_live_your_key_here" }    }  }}

This package forwards to the hosted endpoint, so both options expose the same tools.

3. Ask

Scan https://example.com for AI readiness and fix what you can in this repo.

Tools

ToolWhat it doesCredits
analyze_websiteScan a URL. Returns scores and the fix checklist. scope: full, content, crawlability.1 per scan
get_reportRead a stored report by ID, including its fix checklist.Free
check_statusProgress of a scan that did not finish, or was started with wait: false.Free
list_reportsYour past reports, with filters for URL and status.Free
get_findingsThe fix list for a page or a site, with stable ids.Free
verify_findingsRe-check findings against the live site after you deploy a fix (Pro and Agency).Free
update_findingRecord that a finding is fixed, pending, or ignored.Free
get_artifactGenerate a robots.txt, llms.txt or JSON-LD file that fixes a finding.Free
start_site_analysisScan a whole site (needs site:analyze). Capped at 25 pages over OAuth.1 per page
get_usagePlan, credits used and remaining.Free
list_domainsYour monitored domains (needs domain:read).Free
get_fix_planRanked site-wide fixes from a domain's latest site analysis (needs domain:read).Free

The fix checklist is included on Pro and Agency plans. On other plans, reports say it is locked.

Environment variables (stdio)

VariableRequiredDescription
GENREADY_API_KEYYesYour API key (starts with gr_live_)
GENREADY_MCP_URLNoHosted MCP endpoint (default https://genready.ai/mcp)

Links

Support and contributing

  • Found a bug or a wrong tool description? Open an issue. Include the tool name, what you asked, and the error text.
  • Questions about your account or plan: genready.ai/support.
  • This repository is a published copy of the MCP server that lives in the GenReady monorepo. See CONTRIBUTING.md before you open a pull request.

Source: README.md at commit 163b1e4

Tools

12

analyze_website

Scan a page for AI readiness

Scan one URL for readiness to be cited by AI search engines (ChatGPT, Perplexity, Google AI Overviews) and used by AI agents. Returns scores and the fix checklist: prioritized problems with concrete fixes. Uses one API credit per call, so re-scan only after deploying a change. scope='content' or 'crawlability' runs a narrower, faster scan.

Parametersurlrequiredwaitscope

get_report

Read a page report

Read a stored page report by report ID: the scores and the prioritized fix checklist, with a note on any fixes locked on the account's plan. Use it when you already have a report ID (from analyze_website, check_status or list_reports). It reads saved data and never rescans, so it shows the page as it was when scanned; call analyze_website to see changes. Returns an error if the ID is unknown or belongs to another account. Free: does not use a credit.

Parametersreport_idrequired

get_findings

List findings for a page or site

Findings are the fix list keyed by rule: each carries a stable id that survives re-scans, a policy saying whether an agent may apply the fix unattended ('apply') or should only propose it, and whether a fix can be confirmed by one cheap fetch. Pass exactly one of report_id (the findings of one page) or domain_id (the findings of the latest site analysis), otherwise it returns an error. Use get_report instead if you only need scores. Pass the ids it returns to verify_findings, update_finding and get_artifact. Read-only. Free: does not use a credit.

Parametersdomain_idreport_id

verify_findings

Check whether fixes landed

Re-check findings after deploying a fix. Fetches the live page once per check, with no analysis and no credit, and answers verified, still_failing or unverifiable per finding. Use this instead of re-running analyze_website. Pass exactly one of report_id, domain_id or site_analysis_id, and optionally the finding ids to check. Included with Pro and Agency.

Parametersdomain_idreport_idfinding_idssite_analysis_id

get_artifact

Get a file to commit

Generate a file that fixes a deterministic finding: 'robots_txt' (unblocks AI crawlers while leaving other rules alone), 'llms_txt' (lists the site's real pages) or 'jsonld' (a script block for one page). Anything we did not measure comes back as TODO rather than a guess, so check needsHumanInput before committing. Pass exactly one of report_id or domain_id. Free: does not use a credit.

Parameterskindrequireddomain_idreport_id

update_finding

Record what you did about a finding

Remember a decision so a later session does not redo it. 'fixed_pending' means you changed something and it is not deployed or confirmed yet; 'ignored' silences a finding and requires a reason; 'open' undoes either. You cannot set 'verified': that is earned by calling verify_findings against the live site. Free: does not use a credit.

Parametersreasonstatusrequiredfinding_idrequiredignored_until

start_site_analysis

Scan a whole site

Start a site-wide analysis and let it pick its own pages: the homepage first, then the sections covering the most pages, since a template problem there repeats across the site. Spends one credit per page scanned, so it can cost a lot at once; the plan cap and the credits left both apply and the smaller wins. When connected through OAuth (for example from Claude), a run scans at most 25 pages unless you pass max_pages. Returns immediately. Over an API key it requires the Start site analyses (site:analyze) scope.

Parametersexcludeincludedomain_idrequiredmax_pages

check_status

Check scan progress

Check the progress of one page scan by report ID. Returns its status (queued, processing, complete or failed), a progress percentage when known, and which tool to call next. Use it when analyze_website returned a report ID before the scan finished, or after you started a scan with wait=false. Poll every few seconds, not in a tight loop. For a whole-site run started with start_site_analysis, call get_fix_plan instead. Returns an error if the report ID is unknown. Read-only. Free: does not use a credit.

Parametersreport_idrequired

list_reports

List reports

List the page reports this account has generated, newest first. Each entry has the report ID, URL, overall score, status and creation time. Use it to find a report ID for get_report or get_findings, or to see which pages were already scanned before spending a credit on analyze_website. Filter by URL or status; results come in pages of up to 100, so check the page count at the top of the output and request the next page for more. Read-only. Free: does not use a credit. Returns 'No reports found.' when nothing matches.

Parametersurlpagelimitstatus

get_usage

Check plan usage

Check the plan, API credits used and remaining, and the billing period. Call before a batch of scans.

Takes no parameters.

list_domains

List monitored domains

List the account's monitored domains and their IDs, for use with get_fix_plan. Requires an API key with the domain:read scope.

Takes no parameters.

get_fix_plan

Read a site-wide fix plan

Read the ranked, site-wide fix plan from a domain's latest site analysis: each action says how many pages it affects, how to fix it, and which URLs to verify on. Pass exactly one of domain_id (latest run) or site_analysis_id (a specific run). Free: does not use a credit. Requires the domain:read scope.

Parametersdomain_idsite_analysis_id

Version history

3
  1. v1.2.5LatestOct 20, 2026
  2. v1.2.2Oct 18, 2026
  3. v1.2.1Oct 18, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts