# io.github.shufflethis/geo-tool-check (npm · geo-tool-check)

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

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `geo-tool-check`: 76/100 (this document), [markdown](https://verifymcp.io/servers/shufflethis-geo-tool-check/geo-tool-check.md), [page](https://verifymcp.io/servers/shufflethis-geo-tool-check/geo-tool-check)

## Channel facts

- Registry: `npm`
- Package: `geo-tool-check`
- Version: `1.0.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 23/100
  - Repository check failed: the declared repository URL redirects; it must resolve directly.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 26 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 82/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add shufflethis-geo-tool-check -- npx -y geo-tool-check
```

### Cursor

```json
{
  "mcpServers": {
    "shufflethis-geo-tool-check": {
      "command": "npx",
      "args": [
        "-y",
        "geo-tool-check"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "shufflethis-geo-tool-check": {
      "command": "npx",
      "args": [
        "-y",
        "geo-tool-check"
      ]
    }
  }
}
```

### Codex

```bash
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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add shufflethis-geo-tool-check --command npx --arg -y --arg geo-tool-check
```

### Hermes

```yaml
mcp_servers:
  shufflethis-geo-tool-check:
    command: "npx"
    args: ["-y", "geo-tool-check"]
```

### Netclaw

```json
{
  "McpServers": {
    "shufflethis-geo-tool-check": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "geo-tool-check"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add shufflethis-geo-tool-check -t stdio -c npx -a -y geo-tool-check
```

### Other

```json
{
  "mcpServers": {
    "shufflethis-geo-tool-check": {
      "command": "npx",
      "args": [
        "-y",
        "geo-tool-check"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 76, +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.

### 2026-09-17 (score 75, +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.

### 2026-09-14 (score 74, +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.

### 2026-09-12 (score 73, +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.

### 2026-09-10 (score 72, +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.

### 2026-09-08 (score 71, +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.

### 2026-09-06 (score 70, +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.

### 2026-09-04 (score 69, +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.

## MCP tools (3)

### `check_ai_readiness` (~132 tokens)

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.

Input parameters:

- `lang` (string): Language of the labels and explanations in the result.
- `url` (string, required): Full URL of the page, e.g. https://example.com/pricing

### `check_ai_crawlers` (~107 tokens)

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.

Input parameters:

- `lang` (string): Language of the labels and explanations in the result.
- `url` (string, required): Any URL on the domain; only the origin is used.

### `check_citability` (~96 tokens)

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.

Input parameters:

- `content` (string, required): The passage. HTML is scored more accurately than plain text.
- `lang` (string): Language of the labels and explanations in the result.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/shufflethis-geo-tool-check/geo-tool-check#diagnostics

## Score history

- 2026-09-20: 76
- 2026-09-19: 76
- 2026-09-18: 75
- 2026-09-17: 75
- 2026-09-16: 74
- 2026-09-15: 74
- 2026-09-14: 74
- 2026-09-13: 73
- 2026-09-12: 73
- 2026-09-11: 72
- 2026-09-10: 72
- 2026-09-09: 71
- 2026-09-08: 71
- 2026-09-07: 70
- 2026-09-06: 70
- 2026-09-05: 69
- 2026-09-04: 69
- 2026-09-03: 68
- 2026-09-02: 68
- 2026-09-01: 64
- 2026-08-31: 64
- 2026-08-30: 64
- 2026-08-29: 64
- 2026-08-28: 64
- 2026-08-27: 64
- 2026-08-26: 63
- 2026-08-25: 66

## 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.

## Links

- npm package: https://www.npmjs.com/package/geo-tool-check
- Socket report: https://socket.dev/npm/package/geo-tool-check
- Changelog RSS feed: https://verifymcp.io/servers/shufflethis-geo-tool-check/geo-tool-check.xml
- Changelog JSON feed: https://verifymcp.io/servers/shufflethis-geo-tool-check/geo-tool-check.json
- HTML version of this page: https://verifymcp.io/servers/shufflethis-geo-tool-check/geo-tool-check