GenReady
Server Details
Scan a website for AI search and agent readiness, then get a fix checklist for your agent.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- odb366/genready-mcp-server
- GitHub Stars
- 0
- Server Listing
- @genready/mcp-server
- ChatGPT
- –
- Claude
- GenReady
TDQS
Scored across 12 tools
Each tool targets a distinct phase or resource: one-page scan vs. site-wide scan, progress vs. stored report, page findings vs. site fix plan, artifact generation vs. verification. The descriptions explicitly route between similar-sounding options and warn about ID requirements. No pair appears to do the same thing.
All tools follow a consistent snake_case verb_noun pattern: analyze_website, check_status, get_report, list_reports, start_site_analysis, update_finding, verify_findings. The convention is predictable and readable throughout.
Twelve tools is well-scoped for a scanning, reporting, and fix-management server. Each tool earns its place by covering scanning, status polling, reports, findings, artifacts, verification, usage, and domain listing without obvious redundancy.
The core lifecycle is covered: scan a page or site, poll status, read reports/findings/fix plans, generate artifacts, update decisions, and verify fixes. Minor gaps exist around domain CRUD and canceling or managing long-running site scans, but agents can work around these.
Publisher details
- Operator
- Super easy EOOD
- Operator website
- https://genready.ai/
- Vendor relationship
- Unknown
- Documentation
- https://github.com/odb366/genready-mcp-server
- Privacy policy
- Not provided
- Trust center
- Not available
- Restrictions
- Not available
Available Tools
12 toolsanalyze_websiteScan a page for AI readinessAInspect
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.
Inputs: url (required), wait, scope. Returns: url, scope, locked, scores, +3 more
check_statusCheck scan progressARead-onlyIdempotentInspect
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.
Inputs: report_id (required).
get_artifactGet a file to commitARead-onlyIdempotentInspect
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.
Inputs: kind (required), domain_id, report_id. Returns: kind, notes, changed, content, +4 more
get_findingsList findings for a page or siteARead-onlyIdempotentInspect
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.
Inputs: domain_id, report_id. Returns: findings
get_fix_planRead a site-wide fix planARead-onlyIdempotentInspect
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.
Inputs: domain_id, site_analysis_id. Returns: actions, domainId, generatedAt, siteAnalysisId
get_reportRead a page reportARead-onlyIdempotentInspect
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.
Inputs: report_id (required). Returns: url, scope, locked, scores, +3 more
get_usageCheck plan usageARead-onlyIdempotentInspect
Check the plan, API credits used and remaining, and the billing period. Call before a batch of scans.
Inputs: no named parameters.
list_domainsList monitored domainsARead-onlyIdempotentInspect
List the account's monitored domains and their IDs, for use with get_fix_plan. Requires an API key with the domain:read scope.
Inputs: no named parameters. Returns: domains
list_reportsList reportsARead-onlyIdempotentInspect
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.
Inputs: url, page, limit, status.
start_site_analysisScan a whole siteAInspect
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.
Inputs: domain_id (required), exclude, include, max_pages.
update_findingRecord what you did about a findingAIdempotentInspect
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.
Inputs: status (required), finding_id (required), reason, ignored_until.
verify_findingsCheck whether fixes landedAIdempotentInspect
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.
Inputs: domain_id, report_id, finding_ids, site_analysis_id. Returns: results, summary, checkedAt
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Scan a public website for AI agent readiness: 60 checks, a score, and the evidence for each.
Scan any public website and see how ready it is for AI agents and AI search, explained plainly.
Scan any website for AI-agent readiness: 0-100 score, grade, and agent-simulation audit.
Scan any website's AI readiness: AI search visibility and AI agent usability. Free, no auth.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables scanning any website for AI agent compatibility and marketing health, returning interactive dashboard reports with scores and revenue impact estimates.-

ASO Score MCPofficial
AlicenseAqualityBmaintenanceScans websites to evaluate agent-readiness and produce an ASO Score Report across 34 signals, helping improve discoverability, trust, and interoperability for AI agents.5199 npm2MIT- AlicenseAqualityBmaintenanceScans any website to generate an Agent Readiness Report based on the ASO framework, evaluating agent discoverability, trust, interoperability, and commerce readiness.5257 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables auditing any website for AI-answer readiness, returning a score and actionable fix list based on llms.txt, schema, sitemap, and related checks.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.