Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/tp322d/lastping-appWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/tp322d/lastping-app/lastping)<a href="https://agentmods.dev/mcp/tp322d/lastping-app/lastping"><img src="https://agentmods.dev/badge/mcp/tp322d/lastping-app/lastping/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/tp322d/lastping-app/lastping"><img src="https://agentmods.dev/badge/mcp/tp322d/lastping-app/lastping.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lastping scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "lastping": { "url": "https://mcp.lastping.dev", "type": "streamable-http" } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 6 lines scan A 2f8cbb5f18b9
lastping is an MCP server published in the GitHub repository tp322d/lastping-app (2 stars, last pushed 7d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
gha-intel
Workflow timing analysis, configuration audit and billing insight for GitHub Actions. Runs locally from the @barissozudogru/gha-intel-mcp npm package. Needs 1 environment variable to run.
github-actions
GitHub Actions MCP — view runs, read logs, re-run jobs, and manage CI/CD. Runs locally from the mcp-server-github-actions npm package.
taskbounty-check
Local GitHub Actions/CI maintenance check (action pinning, token perms). Not a full security audit. Runs locally from the taskbounty-check npm package.
blacksmith
MCP server for Blacksmith CI - query runs, analyze test failures, detect flaky tests. Runs locally from the blacksmith-mcp npm package. Needs 2 environment variables to run.
datasieve
On-chain watches, web-page monitors, dead-man switches, cron, and agent coordination, paid via x402. Runs locally from the datasieve-mcp npm package. Needs 2 environment variables to run.
mcp-llm-eval
MCP server that packages LLM evaluation gates as reusable CI/CD primitives. Runs locally from the mcp-llm-eval Python package.