Geo Tool Check
io.github.shufflethisPublished by GitHub account shufflethisv1.0.1Updated Oct 24, 2026
Is this page readable for AI search? Crawler access, structure and citability checks, runs locally.
The publisher's own server: check.tattoo: tattoo size and placement guide
Overview
Scores how readable and citable a web page is for AI crawlers, checking robots.txt access, HTML structure, and citability.
- What you can do
- Exposes three tools: check_ai_readiness returns a 0-100 readiness score with per-category findings for a URL, check_ai_crawlers reports which AI crawlers such as GPTBot, OAI-SearchBot, ClaudeBot and PerplexityBot are blocked by robots.txt, and check_citability scores how quotable a draft passage is without any network request. It runs locally over stdio and can also be used as a CLI, including a minimum-score exit code for CI gating.
- When to use it
- Use it when you want to know whether a page can be read and cited by AI search systems, which crawlers your robots.txt blocks, or why a page may not surface in AI answers. It is also useful for gating a deploy on a minimum readiness score.
- Requirements
- Local process via npm package geo-tool-check over stdio; Node.js 18 or newer, zero runtime dependencies. No account, API key, or environment variables declared. Network access is needed for the URL-based tools; check_citability makes no network request. A hosted Streamable HTTP endpoint is also offered as an alternative.
Installation
In SourceWeft
- Open Geo Tool Check in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
geo-tool-check
[npm] [CI] [MCP Registry] [Node] [License: MIT]
Is this page readable for AI search? One command answers it: crawler access, structure, and citability for ChatGPT, Perplexity, Claude, and Google AI — scored 0–100 with concrete findings.
Everything runs on your machine. No account, no API key, no telemetry — nothing is ever sent to geo-tool.com. The score is computed by the same engine as the free website audit on geo-tool.com, so the number here matches the number there.
- npm:
geo-tool-check— Node 18+, zero runtime dependencies - MCP registry:
io.github.shufflethis/geo-tool-check(stdio server, ships in the package) - Hosted MCP, no install:
https://www.geo-tool.com/mcp(Streamable HTTP) · manifest/.well-known/mcp.json - Docs: Copy-paste examples · Getting started · CLI reference · GitHub Actions · How scoring works · FAQ · Troubleshooting · Architecture
When to use it
- "Is example.com readable for AI search?" — full 0–100 score with findings
- "Which AI crawlers does my robots.txt block?" — GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended and more, each with what blocking it costs you
- "Why doesn't my pricing page show up in ChatGPT answers?" — the findings name what is missing (direct answer, structure, schema, evidence)
- "Is this draft worth citing?" —
check_citabilityscores a text passage with no network request at all - Gate a deploy —
--min-score 70turns the score into an exit code
Not for measuring whether AI answers actually mention your brand — that is a different measurement: the hosted geo-tool.com workspace checks real ChatGPT, Perplexity, and Gemini answers for your buying-intent questions daily.
Quick start
Use it from an AI agent (MCP)
Almost every MCP client accepts this block (per-client setup, config files to copy):
Clients that speak Streamable HTTP to remote servers can skip the install and use the hosted endpoint instead — same tools, rate-limited, fetches run through geo-tool.com's infrastructure rather than your machine:
The three tools, identical in both variants:
Claude Code plugin
Install once:
Then check any page with one command — works immediately, no restart needed:
FAQ
How do I check whether ChatGPT can read my website?
npx geo-tool-check example.com. Two things must be true: robots.txt must
not block OpenAI's crawlers, and the content must exist in the plain HTML —
ChatGPT's crawlers do not execute JavaScript.
Does robots.txt really affect AI visibility?
It can end it. Disallow: / for GPTBot means OpenAI's systems never see
your content. The checker flags blocked scored crawlers separately from
training-only bots, because the consequences differ.
Why does a JavaScript-rendered page score poorly?
Because AI crawlers see what curl sees. If content only exists after
client-side rendering, models find an empty shell — the low score is the
finding. Fixes: SSR, static generation, or prerendering.
Do I need an llms.txt file? Optional and cheap. Google states it does not use it; several AI tools read it. The check detects a real one and ignores SPA catch-all fakes.
Does geo-tool-check upload my content anywhere? No. Every fetch goes from your machine to the target site — never to geo-tool.com. The build fails if a bundle would try.
More: full FAQ.
Honest limits
Node runs no JavaScript — and neither do GPTBot, ClaudeBot, or PerplexityBot. A client-rendered page that scores low here is the finding, not a measurement gap. To compare the crawler's view against the rendered page, use the browser extension.
This checker measures whether a page can be read and cited. Whether AI systems actually mention your brand in real answers is a different measurement: the hosted geo-tool.com workspace checks real AI answers (ChatGPT, Perplexity, Gemini) for your buying-intent questions daily.
Links
- npm: geo-tool-check
- MCP Registry: io.github.shufflethis/geo-tool-check
- Browser extension: geo-tool-com/geo-tool-extension
- Smithery: tracktronaut/geo-tool-check
- Docs: geo-tool.com/en/developers
License
MIT. Built by track by track GmbH.
Source: README.md at commit 2039bc6
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Check integrations
check.tattoo: tattoo size and placement guide
tattoo.checkOfficial publisher
check.tattoo: tattoo size and placement guide's hosted MCP server, published by check.tattoo; no sign-in required; Streamable HTTP; 5 tools.
iva.pt — EU VAT check (VIES) and Portuguese VAT law
pt.ivaOfficial publisher
Validates EU VAT numbers against VIES and returns Portuguese VAT Code (CIVA) and RITI articles, in Portuguese or English.
Dirtsmith Evidence Quote Check
Published by GitHub account throttler300
A local MCP server that binds an assistant's citations to admitted source text with spans and can reject stale-hash references.
HTTP Header Policy Check — HSTS, CSP & Frame Declarations
Published by GitHub account kriton-dev
Remote Apify-hosted MCP server that lets an assistant check seven declared HTTP security header families on a site, without returning raw header values.
VOOPA Render Check
Published by GitHub account Voopa-Corp
Reviews a completed AI-generated video against its brief and recommends whether to edit, retry once, or change approach before paying for another render.