Google Search Console integration for Model Context Protocol (MCP)
iGods GEO Visibility Tool (GVT) 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.
What it does
GEO visibility tests, score trends, sitemap discovery, and domain monitoring for AI agents.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http igods-geo-visibility-tool-gvt-mcp https://mcp.geo.igods.com/mcp
# 2 — ask your agent for something these tools do
# gvt_run_visibility_test, gvt_get_test_results, gvt_list_tests and 16 more
iGods GEO Visibility Tool (GVT) costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http igods-geo-visibility-tool-gvt-mcp https://mcp.geo.igods.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
19 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.
Run a GEO visibility test on a URL. Analyzes 7 categories: JavaScript dependencies (js), no-JS rendering (nojs), semantic HTML5, heading structure, schema.org markup, social tags, and accessibility. This is an async operation — it returns a tid immediately. Pass that tid to gvt_get_test_results to retrieve scores and issues once the test completes (poll until status is not "pending" or "running").
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The URL to analyze |
| waitForJs | boolean | no | Wait for JavaScript rendering before analysis. Set to false to skip JS rendering (faster, but may miss dynamically injected content). |
Get results for a visibility test by tid: overall scores, findingSentence, shareableTid, and per-category resultData. The tid is an opaque 8-character HashID — copy it verbatim from gvt_run_visibility_test, gvt_list_tests, or gvt_get_batch_status; partial or reformatted values will not match, and results are scoped to the caller's own tests. If status is "pending" or "running", wait and retry. fin
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tid | string | yes | Opaque 8-character hash ID returned by gvt_run_visibility_test or gvt_list_tests. Not an integer. |
| detail | string | no | Payload shape. summary: analysisSummary plus the top issues per category (deduplicated by type, capped at 10, sorted by severity then weight) — no semantic tree, per-element markup, or nojs_rendered p |
List visibility tests for the authenticated user, newest first. Supports filtering by domain (optionally including subdomains), by URL (exact or contains match), by creation date range, by status, and by test type. This is the tid and history discovery surface: use it to find the exact recorded URL string and tids that gvt_get_baseline, gvt_get_latest, and gvt_get_test_results require, and use gvt
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max results to return (default 10, max 100) |
| offset | integer | no | Number of records to skip before returning results (not a page number). Use offset=0 for the first page, offset=limit for the second page, etc. |
| domain | string | no | Domain to filter tests by, e.g. example.com. Subdomains are included unless includeSubdomains is false. |
| includeSubdomains | boolean | no | If true (the default), includes tests for subdomains of the given domain. Set false to match the exact domain only. |
| url | string | no | URL to filter tests by; matched per urlMode (contains by default). |
| urlMode | string | no | How the url filter matches: "exact" for full-URL equality, "contains" for substring match. |
| createdFrom | string | no | Inclusive creation-date lower bound. YYYY-MM-DD (UTC midnight) or full ISO 8601 instant. |
| createdTo | string | no | Exclusive creation-date upper bound. YYYY-MM-DD (UTC midnight) or full ISO 8601 instant. |
| status | string | no | Test status to filter by: pending, processing, completed, or failed. |
| testType | string | no | Test type to filter by: url, html, or html_paste. |
| sortDirection | string | no | Sort direction by creation date: desc (newest first, default) or asc (oldest first). |
Get the oldest baseline test snapshot for a single URL, including expired tests. For pre-computed baseline-vs-latest deltas without fetching full snapshots, use gvt_get_score_trend instead; for baselines across many URLs in one call, use gvt_list_baselines. Use with gvt_get_latest to compare baseline vs current when you need the full snapshot detail on both ends. The url must be passed exactly as
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The URL to look up (must match the URL used when the test was run). |
Get the most recent non-expired test snapshot for a single URL. For pre-computed baseline-vs-latest deltas without fetching full snapshots, use gvt_get_score_trend instead. Use with gvt_get_baseline to compare baseline vs current when you need the full snapshot detail on both ends. The url must be passed exactly as the test was run — matching is exact string equality, not nearest-match; an unrecor
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The URL to look up (must match the URL used when the test was run). |
Get the oldest baseline test snapshots for a batch of URLs (up to 100) in a single call. Each result includes the URL and its oldest test object (null if no test exists for that URL). For a single URL use gvt_get_baseline; for pre-computed baseline-vs-latest deltas use gvt_get_score_trend. This bulk form is ideal for monthly/periodic batch comparisons: fetch baselines in bulk here, then call gvt_g
| Parameter | Type | Required | Notes |
|---|---|---|---|
| urls | array | yes | Array of URLs to look up (max 100). |
Compare the oldest baseline vs the latest non-expired test for a single URL or an entire domain, with pre-computed per-category deltas (latest minus baseline). Provide exactly one of url or domain. Domain mode matches the exact domain, www.<domain>, and subdomains (alphabetical, capped by limit). Page through the whole domain with offset: offset=0 for the first page, offset=limit for the second, f
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | no | Single URL scope (XOR with domain). |
| domain | string | no | Domain scope — matches the domain, www.<domain>, and subdomains (XOR with url). |
| limit | integer | no | Cap on returned records in domain mode (max 100, default 25). |
| offset | integer | no | Number of matched URLs to skip in domain mode (row skip, not a page number). Use offset=0 for the first page, offset=limit for the second. Ignored in single-URL mode. |
Discovers and ranks URLs from a domain's XML sitemaps to find the most significant pages (homepages, product pages, recently updated content) before analyzing them. Supports URL-pattern filtering and automatically flags robots.txt-blocked and already-tested pages. Legal/policy boilerplate (privacy, terms, cookies, disclaimers, refunds) is flagged legalPage:true with a -25 significance penalty; use
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The target website URL or an explicit sitemap .xml URL. |
| limit | integer | no | Maximum number of URLs to return (default 10). |
| sort | string | no | How to sort the discovered URLs. 'significance' uses SEO heuristics. |
| include | array | no | Wildcard patterns to require (e.g., '*blog*'). Only '*' wildcards are supported. |
| exclude | array | no | Wildcard patterns to reject (e.g., '*archive*'). |
| excludeDisallowed | boolean | no | If true, silently drops URLs that are blocked by robots.txt. |
| excludeTested | boolean | no | If true, omits URLs the user has already tested. |
| excludeScheduled | boolean | no | If true, omits URLs currently in the testing queue. |
| legalPages | string | no | Tri-state filter for legal/policy boilerplate pages (privacy, terms, cookies, disclaimers, refund policies, etc). "include" keeps them (default), "exclude" drops them, and "only" returns just the lega |
Toggle the public visibility of a test session. Set is_public to true to make the test shareable and receive its public share URL, or false to make it private. The response confirms the new state and, when making a test public, includes the share_url the recipient can visit without any authentication. is_public is the only lever: true both publishes and yields the link in this same response; false
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tid | string | yes | The 8-character test ID returned by gvt_run_visibility_test. |
| is_public | boolean | yes | true to make the test publicly shareable, false to make it private. |
Permanently delete a test session and all its associated results. This action cannot be undone. Use gvt_set_test_visibility instead if you only want to hide a test from public view. Deleting a test does not delete its schedule (if one exists): recurring runs continue until removed via gvt_schedule_test delete mode.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tid | string | yes | The 8-character test ID of the test to delete. |
Queue up to 500 URLs for batch GEO visibility testing. Returns a batch ID for tracking progress. Optionally add URLs to recurring schedules (daily, weekly, monthly) during the same call. Poll gvt_get_batch_status with the batchId until status is completed or failed; then get the compact per-page score summary with gvt_get_batch_summary, or individual results with gvt_get_test_results. This tool qu
| Parameter | Type | Required | Notes |
|---|---|---|---|
| urls | array | yes | Array of URL objects to test (max 500) |
| webhookUrl | string | no | Optional HTTPS URL to receive a batch completion webhook |
Retrieves the current progress, state, and test IDs (tids) of an ongoing or completed visibility testing batch. Poll this tool with the batchId returned by gvt_run_visibility_batch until status is completed or failed. A tid appears on each URL entry only after its test completes — then call gvt_get_batch_summary for the compact per-page scores and top shared issues, or gvt_get_test_results for a s
| Parameter | Type | Required | Notes |
|---|---|---|---|
| batchId | string | yes | The UUID of the batch to check, returned by gvt_run_visibility_batch. |
Compact per-page results and pre-computed aggregates for a completed visibility testing batch: per-URL overall and category scores, findingSentence, average overall score, strongest and weakest categories, best and worst scoring pages, and the top shared issue types with their fixIds. One call replaces one gvt_get_test_results call per URL for audit and status-report workflows — a 10-URL batch dro
| Parameter | Type | Required | Notes |
|---|---|---|---|
| batchId | string | yes | The UUID of the completed batch to summarize, returned by gvt_run_visibility_batch. |
Retrieves the paginated roster of the authenticated caller's test monitoring schedules, allowing filtering by domain, frequency, and status. This is the only way to discover existing schedules and their schids, which the pause/resume/cancel/change_frequency modes of gvt_schedule_test require. Completed one-off rows are hidden by default: batch runs create a throwaway once row per queued URL, so in
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | The maximum number of schedules requested for this page. |
| offset | integer | no | The number of skipped items from the beginning of the result set. |
| domain | string | no | Filter to schedules matching this domain substring. |
| includeSubdomains | boolean | no | Whether subdomains should be included in the domain filter match. |
| frequency | string | no | Filter by repetition interval. |
| status | string | no | Filter by the derived overall state of the schedule. |
| includeCompletedOnce | boolean | no | Whether to include completed one-off schedules in the results. Hidden by default because batch runs create a throwaway once row per queued URL; include them only when investigating batch history. |
| sortDirection | string | no | Sort order by creation time; desc is newest first. |
Manage recurring GVT test schedules: add, delete, reset, pause, resume, cancel, and change_frequency. Discover existing schedules and their schids via gvt_list_schedules; control modes require a schid. For one-off tests use gvt_run_visibility_test; for queued batches without recurrence use gvt_run_visibility_batch. Modes: "add" upserts schedules for the provided urls without duplicating; "delete"
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mode | string | no | Schedule operation mode. add/delete/reset operate on URLs (require urls array). pause/resume/cancel/change_frequency operate on a single schedule (require schid). |
| domain | string | no | Domain to scope a reset operation (reset mode only). e.g. "example.com". Matches https://, http://, with/without www., with/without trailing path. Omit to reset ALL schedules. |
| schid | string | no | Schedule ID. Required for pause, resume, cancel, and change_frequency modes. |
| frequency | string | no | New frequency for the schedule. Required for change_frequency mode. |
| urls | array | no | Array of URL/schedule objects. Required for add, delete, and reset modes. |
Read GVT reference knowledge: how scoring works, score bands and category weights, what each analysis category checks, or GEO glossary definitions. Use it to interpret test results and scores correctly instead of guessing. The topic is matched exactly and case-sensitively (Methodology will not match methodology); unrecognized values fail fast with the valid list. The same content is served as MCP
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | no | Which knowledge topic to read: methodology (how GVT analyzes pages), scoring (score bands and category weights), categories (what each of the six categories checks), glossary (GEO term definitions), o |
Read the canonical fix record for one GVT issue type: severity range, impact, scoring weight, plain-language description, and the recommended remediation. Issue IDs come from the fixId field on issues in gvt_get_test_results output. The same content is served as the gvt://knowledge/fixes/{issue_id} resource template for resource-capable clients. Copy fixId verbatim from the results output — unknow
| Parameter | Type | Required | Notes |
|---|---|---|---|
| issue_id | string | yes | Stable issue identifier, e.g. og_title_missing or color-contrast. Matches the fixId field in gvt_get_test_results output. |
List the GVT prompt workflows: user-invocable recipes that chain GVT tools into complete tasks (check a page, review a monthly batch, analyze regressions, verify fixes, set up domain monitoring, report client status). Each entry lists its arguments. Use gvt_get_prompt to render a prompt with concrete argument values, then follow the rendered instructions to run the workflow. This catalog is static
No parameter schema on file.
Render a GVT prompt workflow with concrete argument values, returning the complete step-by-step instruction text ready to follow. Also returns the effective arguments that were bound (provided values plus defaults for omitted optionals). Prompt names and their arguments come from gvt_list_prompts; an unknown name or argument key errors rather than guessing. The rendered text references GVT tools b
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Prompt name from gvt_list_prompts, e.g. gvt_setup_domain_monitoring. |
| arguments | object | no | Argument values for the prompt, keyed by argument name (e.g. {"domain": "example.com", "frequency": "weekly"}). Omit optional arguments to use their defaults. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- 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 iGods GEO Visibility Tool (GVT) or to call it, at any volume.
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.3.1.
No release note was published with this version.
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.
Any signed-in account that does not publish iGods GEO Visibility Tool (GVT) can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.