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