# LastPing [Health: Active]

**Category:** 📊 Monitoring  
**Repository:** https://github.com/tp322d/lastping-app  
**GitHub Stars:** 2  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/lastping

## Description
Monitoring that agents set up for themselves — cron jobs, CI/CD pipelines and AI agent runs.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "lastping": {
    "url": "https://lastping.dev/mcp/"
  }
}
```

## Documentation

## What LastPing MCP server does

The LastPing MCP server gives an AI assistant access to monitoring based on expected check-ins. Instead of waiting for a process to report that something went wrong, LastPing tracks whether a job sends its expected signal. This approach fits scheduled tasks, deployment pipelines, backups, and AI agent runs that may stop without producing an error message.

The hosted service is available at `https://mcp.lastping.dev/mcp`. An assistant can use MCP to create monitoring and inspect the resulting monitoring information. Monitors can also be created from the LastPing web application at `app.lastping.dev`.

The repository includes more than the MCP interface. Its `lastping` command-line wrapper surrounds an existing command, sends a start ping, runs the command unchanged, and reports the final exit status. A zero exit status is treated as success; any other status is treated as failure, with the end of stderr attached to the report.

## How it works

For most clients, connect to the hosted MCP endpoint and authenticate with LastPing. The hosted route is the recommended way to obtain the current tool set and avoids installing the server locally. Claude Desktop can use the packaged extension, a custom connector, or the `mcp-remote` bridge. Claude Code connects directly over HTTP, while Cursor and Windsurf use the endpoint with an API key.

The command wrapper is independent of the assistant connection. It preserves the wrapped process's exit code, passes stdin and stdout through for interactive commands, and allows the original job to run even if a ping cannot reach LastPing. This makes it suitable for adding monitoring without changing the command's normal CI or shell behavior.

When `lastping run` launches a command, it also configures OpenTelemetry trace settings in that command's environment. The settings associate exported spans with the monitor and run IDs. Existing OpenTelemetry endpoint, resource, and header values are preserved rather than overwritten.

## Setup and configuration

Install the CLI on macOS or Linux with the repository's install script; prebuilt binaries are available for amd64 and arm64, and no Go toolchain is required. A Go installation can alternatively install the command with `go install`. Windows builds are published on the releases page.

To use the MCP service, create a monitor and obtain a write-scope API key from LastPing settings, or let an assistant create the monitor through MCP. Client-specific connection instructions are published at `lastping.dev/mcp/`. The Claude Desktop extension stores its key in the system keychain and does not require Node.js. The bridge configuration requires Node.js and an absolute path to `npx`.

The local MCP executable can be installed with `go install github.com/tp322d/lastping-app/cmd/lastping-mcp@latest`. The material also documents `LASTPING_API_KEY` for authenticated trace export behavior in wrapped commands; it is not used to authenticate the ping itself.

## Tools and capabilities

The LastPing MCP server supports agent-managed monitoring setup and monitoring reads. The repository excerpt does not provide the individual tool names or schemas, so applications should consult the linked MCP documentation for the exact interface.

The CLI provides these operational capabilities:

- Wrap an existing command without changing its arguments or normal output flow.
- Send a start signal and report the command's completion status.
- Attach the tail of stderr to failure reporting.
- Preserve the wrapped command's exit code for CI and shell scripts.
- Expose monitor and run identifiers to OpenTelemetry instrumentation.

LastPing is appropriate when the key failure signal is that a process stopped checking in. It does not replace application-specific metrics or conventional error reporting when those signals are available and required.

_Full upstream README: https://allmcps.com/mcp/lastping/readme_