Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.mrfentmen/lobster-mcp

NPM · LOBSTER-MCP

MCP server for the Lobster programming langua MCP: real tools for real work.

Available components

+3 this week 71 Trust /100

Last scanned (19 hours ago)

Scores higher than 42% of npm servers

Category Developer Tools

Trust breakdown (7 categories)

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
Schema Quality & AI Usability77
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 844 tokens (~52/item across 16 items; 16 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 16 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
What we tested

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 →

Changelog

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.

  • 20 Nov 26 +1

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

  • 18 Nov 26 +1

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

  • 16 Nov 26 +1

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

  • 13 Nov 26 +1

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

  • 12 Nov 26 +2
    • Stability: unverified → 0.13 ▲ functional
  • 9 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 8 Nov 26 50

    First indexed and scored.

Diagnostics

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/lobster-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 →

MCP tools · 16 exposed · ~844 tokens

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 →

Tool Tokens
get_cheatsheet ~41

The full "C-style language cheat sheet for Lobster" from the official docs, useful for translating code from C, C#, Java or JavaScript.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_sample ~52

Return the source of one sample program, matched case-insensitively with or without the .lobster extension.

NameTypeReqDescription
namestringyesSample name, e.g. cube.lobster or knights_tour.

No output schema declared.

No examples provided.

get_section ~43

Read one documentation section in full by its id (ids come from list_sections or search_docs).

NameTypeReqDescription
idstringyesSection id, for example language_reference#4.

No output schema declared.

No examples provided.

list_builtin_categories ~23

List the Lobster builtin categories with the number of functions in each.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_builtins_in_category ~42

List every builtin signature and description inside one category.

NameTypeReqDescription
categorystringyesCategory name, e.g. graphics or builtin (case-insensitive).

No output schema declared.

No examples provided.

list_docs ~19

List the Lobster documentation documents with their section counts.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_keywords ~49

List Lobster's reserved keywords grouped by kind (type, declaration, control, module, operator, literal, expression).

NameTypeReqDescription
kindstring–Only show one kind, for example declaration or control.

No output schema declared.

No examples provided.

list_samples ~23

List the bundled real Lobster sample programs with their size and repository path.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_sections ~47

List documentation sections (id + title) for every document, or for one document.

NameTypeReqDescription
docstring–Document id such as language_reference, language_spec, memory_management or cheat_sheet.

No output schema declared.

No examples provided.

lookup_builtin ~55

Look up a Lobster builtin function by exact name, showing every overload, its signature, category and description.

NameTypeReqDescription
namestringyesBuiltin name exactly as written in Lobster, e.g. print, map, length.

No output schema declared.

No examples provided.

overview ~35

What this server knows about Lobster: source repo and commit, document list, and how many builtins, keywords and samples are bundled.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

run_code ~151

Compile and run a Lobster program with the locally installed toolchain. Writes the code to a temporary directory, runs `lobster main.lobster` there, and returns the exit code, stdout and stderr. Requires Lobster to be installed on the machine (see toolchain_status). Times out after 10s by default and the reference data never leaves the machine.

NameTypeReqDescription
argsarray–Arguments passed to the program after `--` (Lobster exposes them via command_line_arguments()).
codestringyesComplete Lobster source code to compile and run.
timeoutMsinteger–Kill the process after this many milliseconds. Default 10000, max 60000.

No output schema declared.

No examples provided.

search_builtins ~88

Search the 879 Lobster builtin functions by name or description, optionally within one category.

NameTypeReqDescription
categorystring–Restrict to one category such as builtin, graphics, imgui, file, sound, physics, meshgen.
limitinteger–How many results to return (default 10).
querystringyesText to match against builtin names and descriptions.

No output schema declared.

No examples provided.

search_docs ~69

Full-text search over every Lobster document. Title matches rank first, with a snippet from the body.

NameTypeReqDescription
limitinteger–How many results to return (default 5).
querystringyesWord or phrase to look for, e.g. "memory management" or "switch".

No output schema declared.

No examples provided.

search_samples ~64

Search inside the bundled sample programs for a piece of Lobster code.

NameTypeReqDescription
limitinteger–How many samples to return (default 5).
querystringyesSubstring to find in the sample source, e.g. "for(" or "gl.window".

No output schema declared.

No examples provided.

toolchain_status ~43

Check whether the Lobster toolchain is installed and reachable. Reports the binary it would use (LOBSTER_BIN or `lobster` on PATH) without compiling anything.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the io.github.mrfentmen/lobster-mcp server?

io.github.mrfentmen/lobster-mcp runs locally as an npm package, launched with npx -y lobster-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 · lobster-mcp

# add to Claude Code
claude mcp add mrfentmen-lobster-mcp -- npx -y lobster-mcp
Common questions

What is the io.github.mrfentmen/lobster-mcp server?

io.github.mrfentmen/lobster-mcp is listed in the public MCP registry as io.github.mrfentmen/lobster-mcp. MCP server for the Lobster programming langua MCP: real tools for real work. This page covers its npm package (lobster-mcp).

Is the io.github.mrfentmen/lobster-mcp server safe to use?

io.github.mrfentmen/lobster-mcp scores 71 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/lobster-mcp server expose?

io.github.mrfentmen/lobster-mcp exposes 16 tools: overview, list_docs, list_sections, get_section, search_docs, and 11 more. Their descriptions and schemas cost roughly 844 tokens of context every time the server is loaded.

Is the io.github.mrfentmen/lobster-mcp server still maintained?

io.github.mrfentmen/lobster-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/lobster-mcp server under?

io.github.mrfentmen/lobster-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/lobster-mcp server?

VerifyMCP ran 16 checks on io.github.mrfentmen/lobster-mcp, 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.