io.github.mrfentmen/goose-mcp
NPM · GOOSE-MCP
MCP server for the Goose programming language MCP: real tools for real work.
Available components
Last scanned (19 hours ago)
Scores higher than 37% of npm servers
Category Developer Tools
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 19 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 876 tokens (~51/item across 17 items; 17 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
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.
- 9 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 8 Nov 26 50
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 21 Nov 2026 · Analysed npm/goose-mcp@1.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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| 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 →
find_pattern ~86
Translate a C++/Rust idiom to Goose: searches the 'Goose for C++ and Rust Programmers' doc for RAII, smart pointers, templates, move semantics and similar patterns.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max sections (default 3). |
| query | string | yes | Pattern or concept, e.g. RAII, smart pointer, template, move, destructor |
No output schema declared.
No examples provided.
get_operator_precedence ~26
The real operator precedence table from the Goose language reference, tightest binding first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_sample ~48
Return the real source of one bundled sample program, in a code block.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Sample file name, with or without .goose, e.g. 07_sieve |
No output schema declared.
No examples provided.
get_section ~48
Read one full doc section by id. This is how you get the authoritative text of a language rule.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Section id from list_sections, e.g. reference#12 |
No output schema declared.
No examples provided.
list_docs ~22
List every bundled Goose document with its section count and internal doc id.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_keywords ~38
List Goose reserved keywords and contextual keywords, optionally filtered by kind.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Filter: keyword or contextual. Omit for both. |
No output schema declared.
No examples provided.
list_samples ~25
List the bundled sample programs. The numbered ones are the tutorial chapters, in order.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_sections ~56
List section ids and titles, either for one document or for the whole corpus.
| Name | Type | Req | Description |
|---|---|---|---|
| doc | string | – | Document id or title, e.g. tutorial, reference, stdlib, spec, cpp_rust. Omit for all. |
No output schema declared.
No examples provided.
list_stdlib_modules ~27
List the standard-library modules with their symbol counts and the kinds of symbol each exposes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_symbols_in_module ~50
List every stdlib symbol in one module, as kind + name + signature.
| Name | Type | Req | Description |
|---|---|---|---|
| module | string | yes | Module name, e.g. std, vec, math, os, json, regex |
No output schema declared.
No examples provided.
lookup_symbol ~49
Look up a standard-library symbol by exact name and get its real signatures, grouped by module.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Exact symbol name, e.g. push, length, sqrt, json_parse |
No output schema declared.
No examples provided.
overview ~33
What the bundled Goose dataset contains: upstream repo, source commit, counts of doc sections, stdlib symbols, keywords and samples.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
run_code ~127
Compile and run a Goose program with the locally installed toolchain. Writes the code to a temporary directory, runs `goose main.goose` there, and returns the exit code, stdout and stderr. Requires Goose to be installed on the machine (see toolchain_status). Times out after 10s by default.
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | – | Arguments passed to the program after `--`. |
| code | string | yes | Complete Goose source code to compile and run. |
| timeoutMs | integer | – | Kill the process after this many milliseconds. Default 10000, max 60000. |
No output schema declared.
No examples provided.
search_docs ~60
Case-insensitive full-text search across every Goose doc. Title matches rank first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max matches (default 5). |
| query | string | yes | Word or phrase, e.g. defer, data stack, guard, thread_fn |
No output schema declared.
No examples provided.
search_samples ~60
Search inside the bundled sample programs' source code and return a window around each hit.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max samples (default 5). |
| query | string | yes | Code substring, e.g. defer, thread_fn, json_parse, match |
No output schema declared.
No examples provided.
search_symbols ~79
Search stdlib symbol names and signatures, optionally restricted to one module.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 10). |
| module | string | – | Restrict to a stdlib module, e.g. std, vec, json. |
| query | string | yes | Substring to find, e.g. sort, utf8, pool |
No output schema declared.
No examples provided.
toolchain_status ~42
Check whether the Goose toolchain is installed and reachable. Reports the binary it would use (GOOSE_BIN or `goose` on PATH) without compiling anything.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.mrfentmen/goose-mcp server?
io.github.mrfentmen/goose-mcp runs locally as an npm package, launched with npx -y goose-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · goose-mcp
claude mcp add mrfentmen-goose-mcp -- npx -y goose-mcp
What is the io.github.mrfentmen/goose-mcp server?
io.github.mrfentmen/goose-mcp is listed in the public MCP registry as io.github.mrfentmen/goose-mcp. MCP server for the Goose programming language MCP: real tools for real work. This page covers its npm package (goose-mcp).
Is the io.github.mrfentmen/goose-mcp server safe to use?
io.github.mrfentmen/goose-mcp scores 65 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 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.mrfentmen/goose-mcp server expose?
io.github.mrfentmen/goose-mcp exposes 17 tools: overview, list_docs, list_sections, get_section, search_docs, and 12 more. Their descriptions and schemas cost roughly 876 tokens of context every time the server is loaded.
Is the io.github.mrfentmen/goose-mcp server still maintained?
io.github.mrfentmen/goose-mcp is still listed as active in the MCP registry. We last reached this channel on 21 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.mrfentmen/goose-mcp server under?
io.github.mrfentmen/goose-mcp 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.mrfentmen/goose-mcp server?
VerifyMCP ran 15 checks on io.github.mrfentmen/goose-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.mrfentmen/goose-mcp: Stability. One category scores 0 for that reason, because we only credit what we can confirm. 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.