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