check_provider_availability — availability MCP Tool Read-only
check_provider_availability
(check provider availability) is one of 2 tools on the
availability
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_provider_availability from your client
- Claude Code availability check_provider_availability run in your project directory
- Claude Desktop availability check_provider_availability ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor availability check_provider_availability ~/.cursor/mcp.json
- VS Code availability check_provider_availability .vscode/mcp.json
- Zed availability check_provider_availability ~/.config/zed/settings.json
- Windsurf availability check_provider_availability ~/.codeium/windsurf/mcp_config.json
- Cline availability check_provider_availability ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI availability check_provider_availability ~/.gemini/settings.json
- Grok availability check_provider_availability .mcp.json (in your project root)
- ChatGPT availability check_provider_availability Settings → Connectors → Advanced → Developer mode
- Claude.ai availability check_provider_availability Settings → Connectors → Add custom connector
- LangChain availability check_provider_availability pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http availability https://www.speedi.co.uk/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 13 October 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.