C+

npm:gopeak

https://www.npmjs.com/package/gopeak
78/100 · MCP Trust Grade · checked 2h ago · MCP 2.3.7

What it offers — 12 tools · Developer Tools

dap_get_output
dap_set_breakpoint
dap_remove_breakpoint
dap_continue
dap_pause
dap_step_over
dap_get_stack_trace
gopeak
lsp_get_diagnostics
lsp_get_completions
lsp_get_hover
lsp_get_symbols
Spec / packaging20%100
Security (OWASP MCP)30%55
Maintenance / popularity20%100
Tool hygiene15%55
Transparency / provenance15%90

Findings

WARN Runs an install/postinstall script — supply-chain surface to review.
INFO Static analysis of npm package gopeak@2.3.7 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.
Grade another server

We re-grade npm:gopeak 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:gopeak grade C+
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 C+ · wmcp.sh
[![MCP Trust Grade C+](https://wmcp.sh/mcp/grade/npm%3Agopeak/badge.svg)](https://wmcp.sh/mcp/grade/npm%3Agopeak)
<a href="https://wmcp.sh/mcp/grade/npm%3Agopeak"><img src="https://wmcp.sh/mcp/grade/npm%3Agopeak/badge.svg" alt="MCP Trust Grade C+ · 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.