get_run_history — LastPing MCP Tool Read-only
get_run_history
(get run history) is one of 39 tools on the
LastPing
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_run_history from your client
- Claude Code LastPing get_run_history run in your project directory
- Claude Desktop LastPing get_run_history ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor LastPing get_run_history ~/.cursor/mcp.json
- VS Code LastPing get_run_history .vscode/mcp.json
- Zed LastPing get_run_history ~/.config/zed/settings.json
- Windsurf LastPing get_run_history ~/.codeium/windsurf/mcp_config.json
- Cline LastPing get_run_history ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI LastPing get_run_history ~/.gemini/settings.json
- Grok LastPing get_run_history .mcp.json (in your project root)
- ChatGPT LastPing get_run_history Settings → Connectors → Advanced → Developer mode
- Claude.ai LastPing get_run_history Settings → Connectors → Add custom connector
- LangChain LastPing get_run_history pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http lastping https://mcp.lastping.devOther tools on this server
- add_incident_note
- create_api_key
- create_destination
- create_monitor
- create_status_page
- declare_run_expectations
- delete_agent
- delete_destination
- delete_monitor
- delete_status_page
- discover_monitors_reconcile
- export_terraform
- get_agent
- get_alert_templates
- get_incident
- get_monitor
- get_ping_instructions
- get_run
- list_agents
- list_api_keys
- list_deliveries
- list_destinations
- list_incidents
- list_monitors
- list_open_incidents
- list_status_pages
- pause_monitor
- register_agent
- resume_monitor
- revoke_api_key
- set_alert_template
- set_route
- snooze_monitor
- test_destination
- update_agent
- update_destination
- update_monitor
- update_status_page
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.