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