# io.github.GillMacedo/stuckgo (npm · stuckgo)

Find what a stuck Go program is waiting on from a goroutine dump, with no connection to it.

- Trust score: 73/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `stuckgo`: 73/100 (this document), [markdown](https://verifymcp.io/servers/gillmacedo-stuckgo/stuckgo.md), [page](https://verifymcp.io/servers/gillmacedo-stuckgo/stuckgo)

## Channel facts

- Registry: `npm`
- Package: `stuckgo`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 276 tokens (~138/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the io.github.GillMacedo/stuckgo MCP server?

io.github.GillMacedo/stuckgo runs locally as an npm package, launched with npx -y stuckgo serve. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add gillmacedo-stuckgo -- npx -y stuckgo serve
```

### Cursor

```json
{
  "mcpServers": {
    "gillmacedo-stuckgo": {
      "command": "npx",
      "args": [
        "-y",
        "stuckgo",
        "serve"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "gillmacedo-stuckgo": {
      "command": "npx",
      "args": [
        "-y",
        "stuckgo",
        "serve"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add gillmacedo-stuckgo -- npx -y stuckgo serve
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "gillmacedo-stuckgo": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "stuckgo",
        "serve"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add gillmacedo-stuckgo --command npx --arg -y --arg stuckgo --arg serve
```

### Hermes

```yaml
mcp_servers:
  gillmacedo-stuckgo:
    command: "npx"
    args: ["-y", "stuckgo", "serve"]
```

### Netclaw

```json
{
  "McpServers": {
    "gillmacedo-stuckgo": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "stuckgo",
        "serve"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add gillmacedo-stuckgo -t stdio -c npx -a -y stuckgo serve
```

### Other

```json
{
  "mcpServers": {
    "gillmacedo-stuckgo": {
      "command": "npx",
      "args": [
        "-y",
        "stuckgo",
        "serve"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 71)

First indexed and scored.

## MCP tools (2)

### `go_goroutine_compare` (~118 tokens)

Compare two Go goroutine dumps

Compares two goroutine dumps of one Go program taken some time apart, and shows which stacks are growing and which goroutine IDs never moved, which is stronger evidence of a leak than one dump. It never connects to the program.

Input parameters:

- `after` (string): The later goroutine dump's text
- `after_path` (string): Path to a file with the later dump
- `before` (string): The earlier goroutine dump's text
- `before_path` (string): Path to a file with the earlier dump

Output parameters:

- `after_total` (integer)
- `before_total` (integer)
- `fixed_findings` (null|array)
- `growing` (null|array)
- `new_findings` (null|array)
- `notes` (null|array)
- `parked` (null|array)
- `parked_elsewhere` (integer)
- `remaining_findings` (null|array)
- `shrinking` (null|array)

### `go_goroutine_review` (~158 tokens)

Review a Go goroutine dump

Finds what a stuck or leaking Go program is waiting on, from a goroutine dump: /debug/pprof/goroutine?debug=2 or debug=1, a panic traceback, or SIGQUIT output. Groups identical stacks, separates normal idle goroutines, and flags channel leaks, lock pile-ups with possible holders, WaitGroups that never finish, full database pools, HTTP calls with no timeout and nil channels. It only reads the text you give it and never connects to the program. Findings are leads.

Input parameters:

- `dump` (string): Goroutine dump text. Give this or path
- `path` (string): Path to a file holding a goroutine dump. Prefer this for large dumps. Give this or dump

Output parameters:

- `expected_idle` (integer)
- `fatal` (string)
- `findings` (null|array)
- `format` (string)
- `group_count` (integer)
- `groups` (null|array)
- `notes` (null|array)
- `signal` (string)
- `states` (null|array)
- `total` (integer)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/gillmacedo-stuckgo/stuckgo#diagnostics

## Score history

- 2026-11-05: 73
- 2026-11-04: 73
- 2026-11-03: 72
- 2026-11-02: 72
- 2026-11-01: 71

## Common questions

### What is the io.github.GillMacedo/stuckgo MCP server?

io.github.GillMacedo/stuckgo is an MCP server listed in the public MCP registry as io.github.GillMacedo/stuckgo. Find what a stuck Go program is waiting on from a goroutine dump, with no connection to it. This page covers its npm package (stuckgo).

### Is the io.github.GillMacedo/stuckgo MCP server safe to use?

io.github.GillMacedo/stuckgo scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.GillMacedo/stuckgo MCP server expose?

io.github.GillMacedo/stuckgo exposes 2 tools: go_goroutine_compare, go_goroutine_review. Their descriptions and schemas cost roughly 276 tokens of context every time the server is loaded.

### Is the io.github.GillMacedo/stuckgo MCP server still maintained?

io.github.GillMacedo/stuckgo is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.GillMacedo/stuckgo MCP server under?

io.github.GillMacedo/stuckgo declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.GillMacedo/stuckgo MCP server?

VerifyMCP ran 16 checks on io.github.GillMacedo/stuckgo, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/stuckgo
- Socket report: https://socket.dev/npm/package/stuckgo
- Repository: https://github.com/GillMacedo/stuckgo
- Changelog RSS feed: https://verifymcp.io/servers/gillmacedo-stuckgo/stuckgo.xml
- Changelog JSON feed: https://verifymcp.io/servers/gillmacedo-stuckgo/stuckgo/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/gillmacedo-stuckgo/stuckgo.json
- HTML version of this page: https://verifymcp.io/servers/gillmacedo-stuckgo/stuckgo