Lastest runs on your own machine — the client starts it, so there is no endpoint to ping. 50 installs a week from npm. Last commit 10 Sep 2026.
Run visual regression tests, review diffs, and manage baselines on a Lastest instance.
We read the source, 4 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
ENV LASTEST_API_KEY=introspection-only
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
new Function(body);
return execSync(`git ${cmd}`, { encoding: "utf-8" }).trim();
const filePath = path.join(tmpDir, safeName);
{onDelete &&
regions.map((r) => {
const leftPct = ((r.x + r.width) / dims.width) * 100;
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add lastest -- npx -y @lastest/mcp-server
{
"mcpServers": {
"lastest": {
"command": "npx",
"args": [
"-y",
"@lastest/mcp-server"
]
}
}
}
[mcp_servers.lastest]
command = "npx"
args = ["-y", "@lastest/mcp-server"]
{
"mcpServers": {
"lastest": {
"command": "npx",
"args": [
"-y",
"@lastest/mcp-server"
]
}
}
}
{
"servers": {
"lastest": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@lastest/mcp-server"
]
}
}
}
Visual regression & snapshot testing for AI agents — list runs, read semantic diffs, review.
Ask your AI agent why your tests are failing. Instant analysis on failures and regressions.
Visual regression testing over MCP: upload screenshots, review diffs, approve. No CI needed.
Manage test suites, run tests, view results, and automate QA workflows via AI with testRigor.
Regression testing for AI agents. Golden baselines, CI/CD, LangGraph, CrewAI, OpenAI, Claude.
Create and manage test cases, test runs and results in Testiny from your AI assistant.
Local-first visual regression for AI agents: verdicts, diff images, explain_snapshot. No API key.
Evidence-oriented code questions, diff review and test selection via a Jev endpoint.
Answers built from our own checks of this server.