# com.loopgantt/mcp-server (npm · @loopgantt/mcp-server)

Create scheduled Gantt charts with critical path from a plain-language plan — no account or key.

- Trust score: 76/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-22

## Components

- remote · `loopgantt.com`: 81/100, [markdown](https://verifymcp.io/servers/com-loopgantt-mcp-server/api-mcp.md), [page](https://verifymcp.io/servers/com-loopgantt-mcp-server/api-mcp)
- npm · `@loopgantt/mcp-server`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-loopgantt-mcp-server/loopgantt-mcp-server.md), [page](https://verifymcp.io/servers/com-loopgantt-mcp-server/loopgantt-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `@loopgantt/mcp-server`
- Version: `1.4.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-09-22.

- **Supply Chain Security**: 98/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.
  - 31 of 95 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 21 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 666 tokens (~166/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 85% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 com.loopgantt/mcp-server server?

com.loopgantt/mcp-server runs locally as an npm package, launched with npx -y @loopgantt/mcp-server. 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 com-loopgantt-mcp-server -- npx -y @loopgantt/mcp-server
```

### Cursor

```json
{
  "mcpServers": {
    "com-loopgantt-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@loopgantt/mcp-server"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-loopgantt-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@loopgantt/mcp-server"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-loopgantt-mcp-server -- npx -y @loopgantt/mcp-server
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-loopgantt-mcp-server --command npx --arg -y --arg @loopgantt/mcp-server
```

### Hermes

```yaml
mcp_servers:
  com-loopgantt-mcp-server:
    command: "npx"
    args: ["-y", "@loopgantt/mcp-server"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-loopgantt-mcp-server": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@loopgantt/mcp-server"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-loopgantt-mcp-server -t stdio -c npx -a -y @loopgantt/mcp-server
```

### Other

```json
{
  "mcpServers": {
    "com-loopgantt-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@loopgantt/mcp-server"
      ]
    }
  }
}
```

## 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-09-22 (score 76, +1)

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

### 2026-09-20 (score 75, +1)

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

### 2026-09-18 (score 74, +1)

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

### 2026-09-16 (score 73, +1)

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

### 2026-09-14 (score 72, +1)

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

### 2026-09-11 (score 71, +1)

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

### 2026-09-09 (score 70, +1)

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

### 2026-09-07 (score 69, +1)

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

## MCP tools (4)

### `create_gantt` (~248 tokens)

Create a Gantt chart from a task list — no account or API key needed. YOU author the plan: list the tasks in execution order with realistic working-day durations and dependencies (0-based positions of earlier tasks; use { task, type, lag } for start-to-start/finish-to-finish links or lag). Milestones have duration 0. Group tasks into top-level phases for a structured plan/WBS: the phase task gets isPhase: true, its tasks get parent = the position of the phase. LoopGantt schedules it with its critical-path engine and returns a picture of the chart, the dates, the critical path and a link where the user can view, export (PNG/PDF) and save the chart. Always show the user the link.

Input parameters:

- `description` (string): Optional one-line description
- `holidays` (array): Non-working dates, YYYY-MM-DD
- `name` (string, required): Project name
- `startDate` (string): YYYY-MM-DD (defaults to today)
- `tasks` (array, required)
- `workDays` (array): Working weekdays as ISO numbers 1 (Mon) … 7 (Sun). Default Mon–Fri.

### `schedule_project` (~163 tokens)

Compute a schedule without storing anything: dates, critical path, float and project end for a task list (same input shape as create_gantt; name optional). Use it to answer "what is the critical path?", "when would this finish?", "how much slack does X have?". Use create_gantt when the user wants a chart they can open.

Input parameters:

- `description` (string): Optional one-line description
- `holidays` (array): Non-working dates, YYYY-MM-DD
- `name` (string): Project name
- `startDate` (string): YYYY-MM-DD (defaults to today)
- `tasks` (array, required)
- `workDays` (array): Working weekdays as ISO numbers 1 (Mon) … 7 (Sun). Default Mon–Fri.

### `list_templates` (~40 tokens)

List LoopGantt's industry project templates with task counts and typical durations. Pick one, fetch it with get_template, adapt it, then create_gantt.

### `get_template` (~43 tokens)

Get one industry template by slug: its task list with durations, ready to adapt and pass to create_gantt.

Input parameters:

- `slug` (string, required): Template slug from list_templates

## Diagnostics

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

## Score history

- 2026-09-22: 76
- 2026-09-21: 75
- 2026-09-20: 75
- 2026-09-19: 74
- 2026-09-18: 74
- 2026-09-17: 73
- 2026-09-16: 73
- 2026-09-15: 72
- 2026-09-14: 72
- 2026-09-13: 71
- 2026-09-12: 71
- 2026-09-11: 71
- 2026-09-10: 70
- 2026-09-09: 70
- 2026-09-08: 69
- 2026-09-07: 69
- 2026-09-06: 68
- 2026-09-05: 68
- 2026-09-04: 67
- 2026-09-03: 67
- 2026-09-02: 66
- 2026-09-01: 66
- 2026-08-31: 51

## Common questions

### What is the com.loopgantt/mcp-server server?

com.loopgantt/mcp-server is listed in the public MCP registry as com.loopgantt/mcp-server. Create scheduled Gantt charts with critical path from a plain-language plan, no account or key. This page covers its npm package (@loopgantt/mcp-server).

### Is the com.loopgantt/mcp-server server safe to use?

com.loopgantt/mcp-server scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 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 com.loopgantt/mcp-server server expose?

com.loopgantt/mcp-server exposes 4 tools: create_gantt, schedule_project, list_templates, get_template. Their descriptions and schemas cost roughly 494 tokens of context every time the server is loaded.

### Is the com.loopgantt/mcp-server server still maintained?

com.loopgantt/mcp-server is still listed as active in the MCP registry. We last reached this channel on 22 September 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 com.loopgantt/mcp-server server under?

com.loopgantt/mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@loopgantt/mcp-server
- Socket report: https://socket.dev/npm/package/@loopgantt/mcp-server
- Website: https://loopgantt.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-loopgantt-mcp-server/loopgantt-mcp-server.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-loopgantt-mcp-server/loopgantt-mcp-server.json
- HTML version of this page: https://verifymcp.io/servers/com-loopgantt-mcp-server/loopgantt-mcp-server