agent-tool-index — US state MN MCP Tool
agent-tool-index
(agent tool index) is one of 31 tools on the
US state MN
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call agent-tool-index from your client
- Claude Code US state MN agent-tool-index run in your project directory
- Claude Desktop US state MN agent-tool-index ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor US state MN agent-tool-index ~/.cursor/mcp.json
- VS Code US state MN agent-tool-index .vscode/mcp.json
- Zed US state MN agent-tool-index ~/.config/zed/settings.json
- Windsurf US state MN agent-tool-index ~/.codeium/windsurf/mcp_config.json
- Cline US state MN agent-tool-index ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI US state MN agent-tool-index ~/.gemini/settings.json
- Grok US state MN agent-tool-index .mcp.json (in your project root)
- ChatGPT US state MN agent-tool-index Settings → Connectors → Advanced → Developer mode
- Claude.ai US state MN agent-tool-index Settings → Connectors → Add custom connector
- LangChain US state MN agent-tool-index pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http st-mn https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/st-mn/mcpOther tools on this server
- st-mn
- 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
- geo-hint
- calc-eval
- wiki-title-ok
- 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.