Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.shufflethis/geo-tool-check

NPM · GEO-TOOL-CHECK · SCANNED SEP 20

Is this page readable for AI search? Crawler access, structure and citability checks, runs locally.

Available components

npm · geo-tool-check 76
+3 this week 76 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency23
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 403 tokens (~134/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the io.github.shufflethis/geo-tool-check MCP server?

io.github.shufflethis/geo-tool-check runs locally as an npm package, launched with npx -y geo-tool-check. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · geo-tool-check

# add to Claude Code
claude mcp add shufflethis-geo-tool-check -- npx -y geo-tool-check
// .cursor/mcp.json
{
  "mcpServers": {
    "shufflethis-geo-tool-check": {
      "command": "npx",
      "args": [
        "-y",
        "geo-tool-check"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "shufflethis-geo-tool-check": {
      "command": "npx",
      "args": [
        "-y",
        "geo-tool-check"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add shufflethis-geo-tool-check -- npx -y geo-tool-check
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "shufflethis-geo-tool-check": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "geo-tool-check"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add shufflethis-geo-tool-check --command npx --arg -y --arg geo-tool-check
# ~/.hermes/config.yaml
mcp_servers:
  shufflethis-geo-tool-check:
    command: "npx"
    args: ["-y", "geo-tool-check"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "shufflethis-geo-tool-check": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "geo-tool-check"
      ]
    }
  }
}
# add to Vellum
assistant mcp add shufflethis-geo-tool-check -t stdio -c npx -a -y geo-tool-check
// mcp.json
{
  "mcpServers": {
    "shufflethis-geo-tool-check": {
      "command": "npx",
      "args": [
        "-y",
        "geo-tool-check"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/geo-tool-check@1.0.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~335 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_ai_crawlers ~107

Read a domain's robots.txt and report which AI crawlers are fully blocked — GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended and others. Faster than a full readiness check and the first thing to look at when a site is missing from AI answers entirely.

NameTypeReqDescription
langstring–Language of the labels and explanations in the result.
urlstringyesAny URL on the domain; only the origin is used.

No output schema declared.

No examples provided.

check_ai_readiness ~132

Check whether a public web page can be read, understood and cited by AI search systems such as ChatGPT, Perplexity, Claude and Google AI. Returns a score from 0 to 100 across six categories plus concrete findings. Fetches the page from this machine; nothing is sent to a third party. Use this when someone asks why their page does not appear in AI answers, or before publishing a page.

NameTypeReqDescription
langstring–Language of the labels and explanations in the result.
urlstringyesFull URL of the page, e.g. https://example.com/pricing

No output schema declared.

No examples provided.

check_citability ~96

Score a passage of text or HTML on how likely an AI answer is to quote it: answer in the first paragraph, lists, tables, evidence, freshness and depth. Makes no network request at all. Use this while drafting content, before it is published.

NameTypeReqDescription
contentstringyesThe passage. HTML is scored more accurately than plain text.
langstring–Language of the labels and explanations in the result.

No output schema declared.

No examples provided.

Common questions

What is the io.github.shufflethis/geo-tool-check MCP server?

io.github.shufflethis/geo-tool-check is an MCP server listed in the public MCP registry as io.github.shufflethis/geo-tool-check. Is this page readable for AI search? Crawler access, structure and citability checks, runs locally. This page covers its npm package (geo-tool-check).

Is the io.github.shufflethis/geo-tool-check MCP server safe to use?

io.github.shufflethis/geo-tool-check scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.shufflethis/geo-tool-check MCP server expose?

io.github.shufflethis/geo-tool-check exposes 3 tools: check_ai_readiness, check_ai_crawlers, check_citability. Their descriptions and schemas cost roughly 335 tokens of context every time the server is loaded.

Is the io.github.shufflethis/geo-tool-check MCP server still maintained?

io.github.shufflethis/geo-tool-check is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.shufflethis/geo-tool-check MCP server under?

io.github.shufflethis/geo-tool-check declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.