health — Vibe Springs MCP Tool
health
(health) is one of 25 tools on the
Vibe Springs
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call health from your client
- Claude Code Vibe Springs health run in your project directory
- Claude Desktop Vibe Springs health ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Vibe Springs health ~/.cursor/mcp.json
- VS Code Vibe Springs health .vscode/mcp.json
- Zed Vibe Springs health ~/.config/zed/settings.json
- Windsurf Vibe Springs health ~/.codeium/windsurf/mcp_config.json
- Cline Vibe Springs health ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Vibe Springs health ~/.gemini/settings.json
- Grok Vibe Springs health .mcp.json (in your project root)
- ChatGPT Vibe Springs health Settings → Connectors → Advanced → Developer mode
- Claude.ai Vibe Springs health Settings → Connectors → Add custom connector
- LangChain Vibe Springs health pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http x402-tools https://vibesprings.net/mcpOther tools on this server
- search_services
- get_forecast
- get_weather_history
- get_delay_risk
- get_delay_risk_demo
- get_exchange_rates
- convert_currency
- get_crypto_prices
- get_crypto_news
- get_defi_yields
- get_gas_prices
- get_wallet_intel
- get_risk_report
- get_market_pulse
- get_travel_brief
- register_watch
- check_watch
- check_watches_batch
- get_bazaar_category_trends
- get_bazaar_competitors
- audit_agent_visibility
- get_listing_intel
- get_market_history
- check_listing_health
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.