geo-hint — llms.txt Readiness MCP Tool
geo-hint
(geo hint) is one of 31 tools on the
llms.txt Readiness
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call geo-hint from your client
- Claude Code llms.txt Readiness geo-hint run in your project directory
- Claude Desktop llms.txt Readiness geo-hint ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor llms.txt Readiness geo-hint ~/.cursor/mcp.json
- VS Code llms.txt Readiness geo-hint .vscode/mcp.json
- Zed llms.txt Readiness geo-hint ~/.config/zed/settings.json
- Windsurf llms.txt Readiness geo-hint ~/.codeium/windsurf/mcp_config.json
- Cline llms.txt Readiness geo-hint ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI llms.txt Readiness geo-hint ~/.gemini/settings.json
- Grok llms.txt Readiness geo-hint .mcp.json (in your project root)
- ChatGPT llms.txt Readiness geo-hint Settings → Connectors → Advanced → Developer mode
- Claude.ai llms.txt Readiness geo-hint Settings → Connectors → Add custom connector
- LangChain llms.txt Readiness geo-hint pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http llms-txt-readiness https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/llms-txt-readiness/mcpOther tools on this server
- llms-txt-readiness
- utc-time
- timezone
- validate-json
- normalize-url
- inspect-robots
- domain-shape
- citation
- compatibility
- status-catalog
- iana-zones
- web-fetch
- fetch-status
- github-repo-shape
- weather-hint
- memory-key-count
- file-path-ok
- browser-url-ok
- think-steps
- search-query-len
- hn-front-count
- lib-docs-hint
- playwright-url-ok
- figma-url-shape
- jira-key-shape
- calc-eval
- wiki-title-ok
- agent-tool-index
- people-search-index
- agent-ads-index
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.