INDIVIDUAL MCP TOOL
incidents_packet
Incident handoff packet: everything a responder needs One compact document: the incident, affected monitors with per-region failing evidence and the last good check, components, recent deploys with timing (suspect = shipped within 30 minutes before), related past incidents and how they were resolved, the AI analysis, the timeline, runbooks, your guardrails and links.
LIVE ENDPOINT
https://upbutler.com/mcp/public
Connect to this endpoint to inspect the live schema for incidents_packet and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.upbutler]
url = "https://upbutler.com/mcp/public"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"upbutler": {
"type": "http",
"url": "https://upbutler.com/mcp/public"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: upbutler
Remote MCP URL: https://upbutler.com/mcp/public
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"upbutler": {
"url": "https://upbutler.com/mcp/public"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"upbutler": {
"type": "http",
"url": "https://upbutler.com/mcp/public"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "upbutler",
"transport": "streamable-http",
"url": "https://upbutler.com/mcp/public"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
agent_bootstrap— Create a workspace + API key with no human in the loop For autonomous agents.services_add— Plug in a service: monitor + status page component in one call The fastest path: creates a monitor for the URL (or a heartbeat when you pass periodSec), creates the status page if needed (statusPage = slug or name), and adds a component that follows the monitor.heartbeat_ping— Send a heartbeat (no API key needed — the token is the secret) Call at least every periodSec.components_push— Push one component status by its push token (no API key needed) (No API key required.)agent_whoami— Identify the calling keyagent_claim— Get a fresh claim link for this unclaimed workspace, and optionally email it to your human Only for agent-bootstrapped workspaces nobody has claimed yet.monitors_list— List monitors All monitors in the workspace with their current state and last check.monitors_create— Create a monitor Create an uptime monitor.