LastPing

dev.lastping由 lastping.dev 发布官方发布者v0.2.2更新于 Oct 24, 2026

AI agent monitoring: alerts when your agents fail, stall or need you

已验证Streamable HTTP可网页运行云端与基础设施开发者工具安全与监控

概览

AI 生成的概览

LastPing 是托管监控服务，其 MCP 服务器让 AI 助手为代理和任务创建、查看并管理签到监控、事件与告警。

可以做什么
创建、查看、更新、暂停、暂停提醒和删除监控，并发现已有监控以便与助手自身配置核对。获取上报指令并声明运行预期，让代理把上报接入自己的工作流程。查看事件、运行历史、单次运行的时间线与跨度，列出未解决事件并添加备注。配置追踪：获取追踪设置步骤、创建绑定到监控的摄取密钥、诊断被拒绝的跨度。管理告警路由、目标、告警模板、投递日志、状态页和 API 密钥，并将配置导出为 Terraform。注册和跟踪代理及其依赖与用量，并采纳已发现的代理。
适用场景
当你运行 AI 代理、定时任务或 CI/CD 流水线，并希望在它们失败、停滞、等待批准或从未启动时收到告警时使用。也适合让助手在一次对话中自行设置和查看监控，而无需打开仪表盘。
运行要求
通过 streamable HTTP 连接 mcp.lastping.dev 的远程 MCP 端点，使用 OAuth 登录或携带 LastPing API 密钥的 Authorization 头。需要 LastPing 账户，密钥在应用设置中创建。部分客户端需要 mcp-remote 桥接和 Node.js，或 Claude Desktop 扩展。也提供可自行运行的 stdio 二进制。
安装前请注意
Authorization 头携带 LastPing API 密钥，README 建议使用写权限密钥；可通过工具创建、重新生成和撤销密钥，撤销会级联到它创建的密钥。许多工具会写入、更改或删除数据，包括监控、目标、状态页、代理和告警路由。服务为托管式，监控和运行数据会发送到 lastping.dev。

安装

在 SourceWeft 中

  1. 打开 控制台中的 LastPing，将其添加到工作区。
  2. 连接 所需的 凭据。它们会被私密存储，绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/dev.lastping%2Flastping/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。

{
  "mcpServers": {
    "lastping": {
      "type": "http",
      "url": "https://mcp.lastping.dev/mcp"
    }
  }
}

README

[LastPing. AI agent monitoring: alerts when your agents fail, stall or need you. Also cron jobs and CI/CD. Free for individuals.]

[Website] [MCP server docs] [API docs] [Status]

[Release] [License: MIT] [Go 1.26] [Terraform: lastping-dev/lastping] [Free for individuals]

LastPing alerts you when your AI agents fail, stall, wait for your approval or never start, and watches the cron jobs and CI/CD pipelines around them. Free for individuals.

Most monitoring watches a thing and tells you when it looks wrong. LastPing waits for a thing to check in and tells you when it doesn't. That inversion is the whole product: a job that breaks can't send you an error, but it can fail to send you anything, and absence is the one signal a broken process can still produce.

This repository holds the client pieces: the lastping CLI, which wraps any command and reports its start, exit code and traces, and the MCP server, which lets an AI agent set up and read its own monitoring. The hosted service they talk to is at lastping.dev, free for individuals.

Quick start

sh
# 1. Install the CLI (macOS and Linux, amd64 and arm64)curl -fsSL https://raw.githubusercontent.com/lastping-dev/lastping-app/main/install.sh | sh
# 2. Wrap a job: a start ping, your command untouched, then its exit codelastping run --monitor <monitor-id> -- ./backup.sh
text
# 3. Or give your AI assistant the hosted MCP server, and sign inhttps://mcp.lastping.dev/mcp

Create the monitor, and get its id, at app.lastping.dev, or let your assistant do it over MCP. Connect steps for each client are at lastping.dev/mcp/.

Install

sh
curl -fsSL https://raw.githubusercontent.com/lastping-dev/lastping-app/main/install.sh | sh

No Go toolchain needed — that pulls a prebuilt binary for macOS and Linux, on amd64 and arm64, and verifies its checksum. Windows builds are on the releases page.

If you do have Go:

sh
go install github.com/lastping-dev/lastping-app/cmd/lastping@latest

lastping run — reporting you can't forget

Put it in front of whatever you already run:

sh
lastping run --monitor <monitor-id> -- python nightly_etl.pylastping run --monitor <monitor-id> -- ./backup.shlastping run --monitor <monitor-id> -- claude

It sends a start ping, runs your command untouched, and reports the exit code when it finishes — success on 0, failure on anything else, with the tail of stderr attached so the alert says why.

Three properties worth knowing, because they are the difference between a monitoring wrapper you can trust in production and one you remove after a bad night:

  • Your exit code always propagates. The wrapper exits with whatever your command exited with, so CI behaves exactly as it did before you added it.
  • A failed ping never touches your command. If LastPing is unreachable, your job still runs, still writes its output, still exits normally.
  • Interactive stays interactive. stdin and stdout are handed over as file descriptors, so wrapping a REPL or an agent session works.

Why a wrapper rather than an instruction? Because anything advisory decays. An AI agent told to report on every task will stop doing it, and a cron line you meant to add a curl to never gets it. A wrapper reports from the process lifecycle, so nothing depends on anybody remembering.

Traces

lastping run always configures your wrapped command's OpenTelemetry exporter, in its environment only, so an auto-instrumented agent can export its own trace spans with no code change:

  • OTEL_EXPORTER_OTLP_TRACES_ENDPOINT — the header-free monitor-URL form (<ping url>/v1/traces) when LASTPING_API_KEY is not set, so a headerless exporter can still authenticate; the ping host's /v1/traces (the Bearer form) when it is set.
  • OTEL_RESOURCE_ATTRIBUTES — lastping.monitor_id=<id>,lastping.run_id=<rid> appended to whatever you already set, so a trace's spans join the same run the surrounding pings report.
  • OTEL_EXPORTER_OTLP_HEADERS — Authorization=Bearer <your key>, only when LASTPING_API_KEY is set and you have not already set that variable yourself.

Any of the three you already set is left alone. The key is never used to authenticate a ping; the ping URL stays unauthenticated by design, as above.

MCP server — let an agent set up its own monitoring

Claude Desktop extension

A one-click install for Claude Desktop on macOS and Windows that keeps your key in the system keychain. It needs no Node.js.

  1. Download lastping.mcpb.
  2. Double-click it; Claude Desktop opens its install dialog.
  3. Paste a write-scope key from Settings, API keys at app.lastping.dev.

The extension runs this repository's stdio binary (below) on your computer. It is built by mcpb/build.sh when a version is tagged, and every release is signed; the release build fails rather than ship an unsigned bundle. The certificate is self-signed, so Claude Desktop shows the extension as unverified. The signature still proves the bundle came from this repository's release pipeline and was not altered after it was signed. A local build of mcpb/build.sh without the signing secrets is unsigned and says so. MCPB_CERT_CA_ISSUED is kept for a future certificate from a public CA.

Claude Desktop through the mcp-remote bridge

Claude Desktop's config file runs local programs only, so LastPing connects through the mcp-remote bridge. Add this to claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\):

json
{  "mcpServers": {    "lastping": {      "command": "/ABSOLUTE/PATH/TO/npx",      "args": [        "-y", "mcp-remote",        "https://mcp.lastping.dev/mcp",        "--header", "Authorization:${LASTPING_AUTH}"      ],      "env": {        "PATH": "/FOLDER/THAT/HOLDS/npx:/usr/bin:/bin",        "LASTPING_AUTH": "Bearer lp_your_key"      }    }  }}
  • Needs Node.js. Claude Desktop does not read your shell's PATH, so give it the full path: run which npx in a terminal and put the result in command (with nvm it looks like /Users/you/.nvm/versions/node/v22.11.0/bin/npx), and its folder at the front of PATH in env.
  • Quit and reopen Claude Desktop; it reads the file only at start-up. Settings, Connectors then lists lastping.
  • Without a key, add LastPing as a custom connector instead (Customize, Connectors, Add custom connector, then paste https://mcp.lastping.dev/mcp) and sign in to LastPing in the browser. The same connector covers claude.ai, the Claude mobile apps and Cowork.

Other clients

Claude Code connects directly, no bridge: claude mcp add --transport http --scope user lastping https://mcp.lastping.dev/mcp --header "Authorization: Bearer <key>". Cursor, Windsurf, Codex CLI, Gemini CLI and other clients: lastping.dev/mcp/#connect.

The hosted server is the recommended path, and it always carries the current tool set. Most clients connect by adding the URL and signing in to LastPing, with nothing to install; Cursor and Windsurf use the URL and an API key. With a key, Claude Desktop connects through the extension or the mcp-remote bridge above.

A stdio binary is also here if you would rather run it yourself:

sh
go install github.com/lastping-dev/lastping-app/cmd/lastping-mcp@latest
Tools in this repository's stdio binary (50)

Monitors: create_monitor · get_monitor · list_monitors · update_monitor · delete_monitor · pause_monitor · resume_monitor · snooze_monitor

Discovery: discover_monitors_reconcile

Reporting: get_ping_instructions · declare_run_expectations

Incidents & runs: list_incidents · get_run_history · get_run (one run's full timeline, assertion verdicts and spans) · list_runs (runs across every monitor, traced runs included, with filters) · get_incident (one incident's recorded timeline)

Tracing: get_trace_setup (the set-up steps for one tool, from the server) · create_ingest_key (a tracing key bound to one monitor; a write key is enough) · get_trace_diagnostics (why a sent span was refused)

Agent observability: get_agent_dependencies · get_agent_usage · list_dependencies · list_discovered_agents · adopt_discovered_agent

The failure loop: list_open_incidents · add_incident_note

Alert routing: set_route · delete_route

Delivery log: list_deliveries, recent alert deliveries across every monitor, no paging

Destinations: list_destinations · create_destination · update_destination · test_destination · delete_destination

Alert templates: get_alert_templates · set_alert_template

Agent registry: register_agent · list_agents · get_agent · update_agent · delete_agent

Status pages: list_status_pages · create_status_page · update_status_page · delete_status_page

API keys: create_api_key (optional scope: read / write / admin / ingest) · list_api_keys · regenerate_api_key (new secret, same key; does not cascade) · revoke_api_key (cascades to every key it created)

Terraform: export_terraform

This binary carries the same tool set as the hosted server at mcp.lastping.dev. It is a thin REST client throughout: every tool is a direct HTTP call to the management API, so it stays free to run yourself with no lag behind the hosted surface beyond a new release.

The one that matters most is get_ping_instructions: an agent calls create_monitor, then asks for its own ping commands, and wires them into its own work — in one conversation, without a human opening a dashboard.

Ping API

Every monitor gets a URL. There is nothing to install and no library to keep current; anything that can make an HTTP request can report.

What happenedRequest
finished successfullyPOST <ping-url>
started a runPOST <ping-url>/start
failedPOST <ping-url>/fail with the error as the body
exited with a codePOST <ping-url>/<exit-code>
waiting on a humanPOST <ping-url>/blocked
progress worth recordingPOST <ping-url>/note

Add ?rid=<id> to pair a run's start with its result, so LastPing can group a run's pings and time it.

sh
# The classic one-liner, at the end of a cron job:curl -fsS -m 10 --retry 3 https://ping.lastping.dev/<monitor-id>

Traces

POST https://ping.lastping.dev/v1/traces accepts an OTLP/HTTP export (application/x-protobuf or application/json, gzip accepted) with a Bearer key (an ingest key bound to the monitor, from create_ingest_key; a write or admin key also works), or POST <ping-url>/v1/traces for exporters that cannot set headers. Spans need the resource attribute lastping.monitor_id; with lastping.run_id they join that run, and without it each trace becomes a run of its own. A payload is capped at 1 MiB decompressed, 500 spans per request and 2,000 spans per run. lastping run sets all of this up for you — see Traces above.

Monitoring as code

hcl
resource "lastping_monitor" "nightly_etl" {  name          = "nightly-etl"  slug          = "nightly-etl"  schedule_kind = "cron"  cron_expr     = "0 3 * * *"  tz            = "Europe/Berlin"  grace_s       = 900}

The provider is on the Terraform Registry as lastping-dev/lastping, with source at lastping-dev/terraform-provider-lastping.

Links

License

MIT. See LICENSE.

来源：README.md，提交 253f01a

工具

0
该服务器需要登录，因此 SourceWeft 无法在没有账号的情况下读取其工具，也未收录。已连接账号所能看到的内容可能因账号及其权限而异。

版本历史

4
  1. v0.2.2最新Oct 13, 2026
  2. v0.2.1Oct 13, 2026
  3. v0.2.0Oct 2, 2026
  4. v0.1.0Sep 16, 2026

评分

已满足适用检查项的 85%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分