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