fetch-status — File Path Check MCP Tool Read-only
fetch-status
(fetch status) is one of 30 tools on the
File Path Check
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call fetch-status from your client
- Claude Code File Path Check fetch-status run in your project directory
- Claude Desktop File Path Check fetch-status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor File Path Check fetch-status ~/.cursor/mcp.json
- VS Code File Path Check fetch-status .vscode/mcp.json
- Zed File Path Check fetch-status ~/.config/zed/settings.json
- Windsurf File Path Check fetch-status ~/.codeium/windsurf/mcp_config.json
- Cline File Path Check fetch-status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI File Path Check fetch-status ~/.gemini/settings.json
- Grok File Path Check fetch-status .mcp.json (in your project root)
- ChatGPT File Path Check fetch-status Settings → Connectors → Advanced → Developer mode
- Claude.ai File Path Check fetch-status Settings → Connectors → Add custom connector
- LangChain File Path Check fetch-status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http file-path-ok https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/file-path-ok/mcp
Other tools on this server
- file-path-ok
- utc-time
- timezone
- validate-json
- normalize-url
- inspect-robots
- domain-shape
- citation
- compatibility
- status-catalog
- iana-zones
- web-fetch
- github-repo-shape
- weather-hint
- memory-key-count
- 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
- 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.