# io.github.mrfentmen/lobster-mcp (npm · lobster-mcp)

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

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `lobster-mcp`: 71/100 (this document), [markdown](https://verifymcp.io/servers/mrfentmen-lobster-mcp/lobster-mcp.md), [page](https://verifymcp.io/servers/mrfentmen-lobster-mcp/lobster-mcp)

## Channel facts

- Registry: `npm`
- Package: `lobster-mcp`
- Version: `1.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-21.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 31 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/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 19 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 844 tokens (~52/item across 16 items; 16 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add mrfentmen-lobster-mcp -- npx -y lobster-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "mrfentmen-lobster-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "lobster-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mrfentmen-lobster-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "lobster-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add mrfentmen-lobster-mcp -- npx -y lobster-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add mrfentmen-lobster-mcp --command npx --arg -y --arg lobster-mcp
```

### Hermes

```yaml
mcp_servers:
  mrfentmen-lobster-mcp:
    command: "npx"
    args: ["-y", "lobster-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "mrfentmen-lobster-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "lobster-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add mrfentmen-lobster-mcp -t stdio -c npx -a -y lobster-mcp
```

### Other

```json
{
  "mcpServers": {
    "mrfentmen-lobster-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "lobster-mcp"
      ]
    }
  }
}
```

## 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-20 (score 71, +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.

### 2026-11-18 (score 70, +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.

### 2026-11-16 (score 69, +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.

### 2026-11-13 (score 68, +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.

### 2026-11-12 (score 67, +2)

- [functional improvement] Stability: unverified → 0.13

### 2026-11-09 (score 65, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-08 (score 50)

First indexed and scored.

## MCP tools (16)

### `overview` (~35 tokens)

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

### `list_docs` (~19 tokens)

List the Lobster documentation documents with their section counts.

### `list_sections` (~47 tokens)

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

Input parameters:

- `doc` (string): Document id such as language_reference, language_spec, memory_management or cheat_sheet.

### `get_section` (~43 tokens)

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

Input parameters:

- `id` (string, required): Section id, for example language_reference#4.

### `search_docs` (~69 tokens)

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

Input parameters:

- `limit` (integer): How many results to return (default 5).
- `query` (string, required): Word or phrase to look for, e.g. "memory management" or "switch".

### `lookup_builtin` (~55 tokens)

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

Input parameters:

- `name` (string, required): Builtin name exactly as written in Lobster, e.g. print, map, length.

### `search_builtins` (~88 tokens)

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

Input parameters:

- `category` (string): Restrict to one category such as builtin, graphics, imgui, file, sound, physics, meshgen.
- `limit` (integer): How many results to return (default 10).
- `query` (string, required): Text to match against builtin names and descriptions.

### `list_builtin_categories` (~23 tokens)

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

### `list_builtins_in_category` (~42 tokens)

List every builtin signature and description inside one category.

Input parameters:

- `category` (string, required): Category name, e.g. graphics or builtin (case-insensitive).

### `list_keywords` (~49 tokens)

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

Input parameters:

- `kind` (string): Only show one kind, for example declaration or control.

### `get_cheatsheet` (~41 tokens)

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

### `list_samples` (~23 tokens)

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

### `get_sample` (~52 tokens)

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

Input parameters:

- `name` (string, required): Sample name, e.g. cube.lobster or knights_tour.

### `search_samples` (~64 tokens)

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

Input parameters:

- `limit` (integer): How many samples to return (default 5).
- `query` (string, required): Substring to find in the sample source, e.g. "for(" or "gl.window".

### `toolchain_status` (~43 tokens)

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

### `run_code` (~151 tokens)

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.

Input parameters:

- `args` (array): Arguments passed to the program after `--` (Lobster exposes them via command_line_arguments()).
- `code` (string, required): Complete Lobster source code to compile and run.
- `timeoutMs` (integer): Kill the process after this many milliseconds. Default 10000, max 60000.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/mrfentmen-lobster-mcp/lobster-mcp#diagnostics

## Score history

- 2026-11-21: 71
- 2026-11-20: 71
- 2026-11-19: 70
- 2026-11-18: 70
- 2026-11-17: 69
- 2026-11-16: 69
- 2026-11-15: 68
- 2026-11-14: 68
- 2026-11-13: 68
- 2026-11-12: 67
- 2026-11-11: 65
- 2026-11-10: 65
- 2026-11-09: 65
- 2026-11-08: 50

## 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.

## Links

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