io.github.GillMacedo/stuckgo
NPM · STUCKGO
Find what a stuck Go program is waiting on from a goroutine dump, with no connection to it.
Available components
Last scanned (7 hours ago)
Scores higher than 46% of npm servers
Category Monitoring and Observability
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 276 tokens (~138/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 1 Nov 26 71
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/stuckgo@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
go_goroutine_compare Compare two Go goroutine dumps ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| after_total | integer | yes | – |
| before_total | integer | yes | – |
| fixed_findings | null|array | yes | – |
| growing | null|array | yes | – |
| new_findings | null|array | yes | – |
| notes | null|array | – | – |
| parked | null|array | yes | – |
| parked_elsewhere | integer | yes | – |
| remaining_findings | null|array | yes | – |
| shrinking | null|array | yes | – |
No examples provided.
go_goroutine_review Review a Go goroutine dump ~158
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| expected_idle | integer | yes | – |
| fatal | string | – | – |
| findings | null|array | yes | – |
| format | string | yes | – |
| group_count | integer | yes | – |
| groups | null|array | yes | – |
| notes | null|array | – | – |
| signal | string | – | – |
| states | null|array | yes | – |
| total | integer | yes | – |
No examples provided.
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.
npm · stuckgo
claude mcp add gillmacedo-stuckgo -- npx -y stuckgo serve
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.