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