get_monitor_history — Uptimepage MCP Tool Read-only
get_monitor_history
(get monitor history) is one of 31 tools on the
Uptimepage
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_monitor_history from your client
- Claude Code Uptimepage get_monitor_history run in your project directory
- Claude Desktop Uptimepage get_monitor_history ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Uptimepage get_monitor_history ~/.cursor/mcp.json
- VS Code Uptimepage get_monitor_history .vscode/mcp.json
- Zed Uptimepage get_monitor_history ~/.config/zed/settings.json
- Windsurf Uptimepage get_monitor_history ~/.codeium/windsurf/mcp_config.json
- Cline Uptimepage get_monitor_history ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Uptimepage get_monitor_history ~/.gemini/settings.json
- Grok Uptimepage get_monitor_history .mcp.json (in your project root)
- ChatGPT Uptimepage get_monitor_history Settings → Connectors → Advanced → Developer mode
- Claude.ai Uptimepage get_monitor_history Settings → Connectors → Add custom connector
- LangChain Uptimepage get_monitor_history pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http uptimepage https://mcp.uptimepage.dev/mcpOther tools on this server
- acknowledge_incident
- add_status_page_components
- create_monitor
- create_monitors
- create_status_page
- get_flow_runs
- get_flow_step_trend
- get_incident
- get_incident_metrics
- get_monitor
- get_org_health
- get_org_usage
- get_status_page
- list_incidents
- list_monitors
- list_notification_channels
- list_regions
- list_status_pages
- list_tags
- list_variables
- pause_monitor
- post_incident_update
- publish_incident
- resolve_incident
- resume_monitor
- run_check_now
- unpublish_incident
- update_monitor
- update_status_page
- update_status_page_component
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.