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