iGods Internet Marketing Inc. MCP server

Which servers in the official MCP registry are iGods Internet Marketing Inc.'s own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-20

← Back to iGods Internet Marketing Inc.

Whose server it is

Registry namecom.igods/gvtverified in the MCP registry

The registry name sits under igods.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-20

Stateanswerschecked 2026-10-20
Tools19
Server calls itselfgvt-mcp
Server version0.2.0
Protocol version2025-06-18

On 2026-10-20 the server answered initialize and tools/list without a sign-in. First answer in 109 ms.

Should an agent connect itNot proven either way yet

Whether its tools do the product's job has not been judged yet.
Checked on 1 of the 7 days it takes to judge reliability.

Once connected

gvt_set_test_visibility, gvt_delete_test change data without a sign-in: anyone with the address can call them.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-10-20

INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
Answeredmeasuring1 of the 7 daily checks it takes to print a share
Median first answer144 ms
Space in an agent's context≈ 6,080 tokensthe definitions of all its tools (19), which an agent carries on every turn
Tool definitionsA · 100 of 100

Every tool passes all six checks.

Worth a look

Tools that change data, on a server that answers without a sign-in: gvt_set_test_visibility, gvt_delete_test

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers19 tools · read 2026-10-20

gvt_run_visibility_test
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…
gvt_get_test_results
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_list_tests
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…
gvt_get_baseline
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_get_latest
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…
gvt_list_baselines
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…
gvt_get_score_trend
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…
gvt_list_sitemap_urls
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…
gvt_set_test_visibility
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…
gvt_delete_test
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…
gvt_run_visibility_batch
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…
gvt_get_batch_status
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…
gvt_get_batch_summary
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…
gvt_list_schedules
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…
gvt_schedule_test
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_get_knowledge
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…
gvt_get_fix
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…
gvt_list_prompts
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…
gvt_get_prompt
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)…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "gvt": {
      "type": "http",
      "url": "https://mcp.geo.igods.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http igods https://mcp.geo.igods.com/mcp

Add to Cursor Add to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.geo.igods.com/mcp as a custom connector in the settings.

Other servers listed as iGods Internet Marketing Inc.'s

com.igods/space-monkeyanswers, 26 toolsverified in the MCP registry

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.