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