Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
GenReady is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
99/100
trust score
347
downloads a day
local
or remote
540
downloads in 30d
What it does
Scan a website for AI search and agent readiness, then get a fix checklist for your agent.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'GENREADY_API_KEY=${GENREADY_API_KEY}' --transport stdio genready-mcp '--' npx -y @genready/mcp-server
# 2 — ask your agent for something these tools do
# analyze_website, get_report, get_findings and 9 more
It needs GENREADY_API_KEY: this reads it from your environment, so export it first.
GenReady costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ODAll 1 server
odb3661 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads GENREADY_API_KEY (GenReady API key. Create one at https://genready.ai/api-keys) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx GENREADY_API_KEY … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'GENREADY_API_KEY=${GENREADY_API_KEY}' --transport stdio genready-mcp '--' npx -y @genready/mcp-serverReconnect, or start a new session, and the tools appear in the model’s tool list.
Or connect to its publisher’s address
Its publisher also runs it at https://genready.ai/mcp: nothing to start on your machine, and this marketplace is not in the path.
claude mcp add --scope user --transport http genready-mcp https://genready.ai/mcpFree on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: GENREADY_API_KEY — GenReady API key. Create one at https://genready.ai/api-keys. You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Full http(s) URL of the page to scan |
| scope | string | no | 'full' (default), 'content' (content quality only) or 'crawlability' (technical checks only) |
| wait | boolean | no | Wait up to about 25s for the result (default). Slower scans, or false, return a report ID to poll with check_status. |
Read a previously generated report by ID, including its fix checklist. Free: does not use a credit.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| report_id | string | yes | Report ID from analyze_website or list_reports |
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 or domain_id. Free: does…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| report_id | string | no | Report ID, for one page |
| domain_id | string | no | Domain ID, for the latest site analysis |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| report_id | string | no | Report ID whose findings to re-check |
| domain_id | string | no | Domain ID, for its latest site analysis |
| site_analysis_id | string | no | A specific site analysis run |
| finding_ids | array | no | Finding ids from get_findings. Omit to check them all. |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | yes | Which file to generate |
| report_id | string | no | Report ID, for a page-scoped artifact |
| domain_id | string | no | Domain ID, for a site-scoped artifact |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| finding_id | string | yes | Finding id from get_findings |
| status | string | yes | 'fixed_pending' after making a change, 'ignored' to silence it, 'open' to undo |
| reason | string | no | Why. Required when ignoring, and worth writing for the next session. |
| ignored_until | string | no | ISO timestamp when an ignore should lapse. Omit to ignore indefinitely. |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain_id | string | yes | Domain ID from list_domains |
| max_pages | integer | no | Your own ceiling on pages, and therefore on credits |
| include | array | no | Only scan URLs matching these patterns. * is the wildcard. |
| exclude | array | no | Never scan URLs matching these. Applied after include. |
Check the progress of a running scan started with wait=false.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| report_id | string | yes | Report ID to check |
List reports this account has generated, newest first, with IDs, URLs, scores and status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number |
| limit | integer | no | Results per page |
| status | string | no | Filter by status: complete, processing, queued, failed |
| url | string | no | Filter by URL (partial match) |
Check the plan, API credits used and remaining, and the billing period. Call before a batch of scans.
No parameter schema on file.
List the account's monitored domains and their IDs, for use with get_fix_plan. Requires an API key with the domain:read scope.
No parameter schema on file.
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain_id | string | no | Domain ID from list_domains; reads its latest completed run |
| site_analysis_id | string | no | A specific site analysis run ID |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install GenReady or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 99 / 100
Release 1.2.2 · scanned 19 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest9f79fe1c4f762e01c80f916cb4ec55ba81ae31dee60192135ccc5062ffa361e5
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest9f79fe1c4f762e01
Scanned2026-10-19
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.2.2. Pin a release below and the command asks for exactly that one.
1.2.2
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish GenReady can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.