verify_sickslip_note — verify MCP Tool
verify_sickslip_note
(verify sickslip note) is one of 5 tools on the
verify
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call verify_sickslip_note from your client
- Claude Code verify verify_sickslip_note run in your project directory
- Claude Desktop verify verify_sickslip_note ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor verify verify_sickslip_note ~/.cursor/mcp.json
- VS Code verify verify_sickslip_note .vscode/mcp.json
- Zed verify verify_sickslip_note ~/.config/zed/settings.json
- Windsurf verify verify_sickslip_note ~/.codeium/windsurf/mcp_config.json
- Cline verify verify_sickslip_note ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI verify verify_sickslip_note ~/.gemini/settings.json
- Grok verify verify_sickslip_note .mcp.json (in your project root)
- ChatGPT verify verify_sickslip_note Settings → Connectors → Advanced → Developer mode
- Claude.ai verify verify_sickslip_note Settings → Connectors → Add custom connector
- LangChain verify verify_sickslip_note pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http verify https://sickslip.onrender.com/api/mcpOther tools on this server
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.