A

npm:@lastest/mcp-server

https://www.npmjs.com/package/@lastest/mcp-server
95/100 · MCP Trust Grade · checked 2h ago · MCP 0.3.7

What it offers — 30 tools · Developer Tools

lastest_health_check

Check connectivity to the Lastest instance.

lastest_list_active_jobs

List currently active background jobs (builds, AI operations, etc.).

lastest_get_job_status

Get the status and progress of a specific background job.

lastest_list_repos

List all repositories accessible to the current team.

lastest_get_repo

Get details about a specific repository.

lastest_create_repo

Create a new local repository in the current team. Use this when you need a fresh workspace for tests without connecting to GitHub/GitLab. Pass

lastest_update_repo

Update a repository

lastest_get_playwright_settings

Get the repo-level Playwright settings (browser, viewport, timeouts, error modes, stabilization, parallelism caps, etc.). Falls back to the global row

lastest_update_playwright_settings

Upsert repo-level Playwright settings. Pass any subset of fields \u2014 unknown keys are rejected, unspecified ones stay at their current value. Use t

lastest_list_areas

List functional areas (test groupings) for a repository.

lastest_create_area

Create a new functional area for organizing tests.

lastest_update_area

Update a functional area

lastest_delete_area

Soft-delete a functional area. Tests remain but become unassigned.

lastest_list_tests_by_area

List tests within a specific functional area.

lastest_get_test

Get full details of a single test including code, URL, and last run status.

lastest_update_test

Update a test

lastest_delete_test

Soft-delete a test (can be restored). Does not permanently remove test data.

lastest_get_test_run

Get detailed results for a specific test run, including individual test results, errors, and durations.

+12 more tools

Spec / packaging20%100
Security (OWASP MCP)30%90
Maintenance / popularity20%100
Tool hygiene15%95
Transparency / provenance15%90

Findings

INFO Static analysis of npm package @lastest/mcp-server@0.3.7 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.
Grade another server

We re-grade npm:@lastest/mcp-server on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — npm:@lastest/mcp-server grade A
Share on X Open card image

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

MCP Trust Grade A · wmcp.sh
[![MCP Trust Grade A](https://wmcp.sh/mcp/grade/npm%3A%40lastest%2Fmcp-server/badge.svg)](https://wmcp.sh/mcp/grade/npm%3A%40lastest%2Fmcp-server)
<a href="https://wmcp.sh/mcp/grade/npm%3A%40lastest%2Fmcp-server"><img src="https://wmcp.sh/mcp/grade/npm%3A%40lastest%2Fmcp-server/badge.svg" alt="MCP Trust Grade A · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust
How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.