lastping

MCP开发工具

提供方 LastPing · 包名 mcp-remote

开发工具 HTTP · 远程 OAuth 授权 社区 / 第三方 Claude DesktopClaudeCursorVS Code
查看接入方式

由 LastPing 提供的 MCP 服务器,HTTP · 远程。

一句话选型结论

按资料字段整理

lastping 属于开发工具类 MCP 服务器,HTTP · 远程,OAuth 授权,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接复制的远程端点配置。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式HTTP · 远程 鉴权OAuth 授权 部署方式远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

monitoringcronci cd

安装与配置

HTTP · 远程 OAuth 授权
连远程 HTTPS 端点,通常为 Streamable HTTP
npx -y mcp-remote https://mcp.lastping.dev/mcp --header Authorization: Bearer ${LASTPING_API_KEY}

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
lastping当前 未标注 HTTP · 远程 远程部署 有 未标注
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方LastPing上游标注的维护方 LastPing
分类开发工具本站按上游分类展示
连接方式HTTP · 远程连远程 HTTPS 端点,通常为 Streamable HTTP
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时mcp-remote · 未标注本地安装时用到的包标识与运行时
部署类型远程部署上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

11.0 KB
来自项目仓库与上游目录的原文,未做删改

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 code

lastping run --monitor <monitor-id> -- ./backup.sh
``````text

3. Or give your AI assistant the hosted MCP server, and sign in

https://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&#x27;t forget

Put it in front of whatever you already run:```sh
lastping run --monitor &lt;monitor-id&gt; -- python nightly_etl.py
lastping run --monitor &lt;monitor-id&gt; -- ./backup.sh
lastping run --monitor &lt;monitor-id&gt; -- 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
    (/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=,lastping.run_id=
    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, 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&#x27;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 &quot;Authorization: Bearer &quot;`.
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 happened Request
finished successfully POST
started a run POST /start
failed POST /fail with the error as the body
exited with a code POST /
waiting on a human POST /blocked
progress worth recording POST /note

Add ?rid= 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 /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 &quot;lastping_monitor&quot; &quot;nightly_etl&quot; {
  name          = &quot;nightly-etl&quot;
  slug          = &quot;nightly-etl&quot;
  schedule_kind = &quot;cron&quot;
  cron_expr     = &quot;0 3 * * *&quot;
  tz            = &quot;Europe/Berlin&quot;
  grace_s       = 900
}

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

Links

  • lastping.dev — the hosted service, free for individuals
  • AI agent monitoring — the agent-first guide
  • MCP server — connect configs per client
  • Terraform provider — monitoring as code
  • Integration guides — cron, Kubernetes, systemd, GitHub Actions, Python, Node

License

MIT. See LICENSE.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
lastping 怎么安装?

在客户端按下面的安装命令接入:npx -y mcp-remote https://mcp.lastping.dev/mcp --header Authorization: Bearer ${LASTPING_API_KEY}。对应的包名是 mcp-remote。装完在客户端配置里引用同一个包或端点。

lastping 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是HTTP · 远程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

lastping 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

lastping 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

lastping 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Windsurf、Codex;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

lastping 能提供哪些能力?

资料显示能力标签包括 monitoring、cron、ci cd、ai agents、observability、alerting。具体工具清单以官方文档为准。

lastping 需要什么运行环境?

属于远程端点,不需要在本地装运行时。

lastping 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为HTTP · 远程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。