com.loopgantt/mcp-server
NPM · @LOOPGANTT/MCP-SERVER · 2 COMPONENTS · SCANNED SEP 22
Create scheduled Gantt charts with critical path from a plain-language plan — no account or key.
Available components
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 Security98
- 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
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- 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 21 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 85% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
npm · @loopgantt/mcp-server
claude mcp add com-loopgantt-mcp-server -- npx -y @loopgantt/mcp-server
{
"mcpServers": {
"com-loopgantt-mcp-server": {
"command": "npx",
"args": [
"-y",
"@loopgantt/mcp-server"
]
}
}
} {
"servers": {
"com-loopgantt-mcp-server": {
"command": "npx",
"args": [
"-y",
"@loopgantt/mcp-server"
]
}
}
} codex mcp add com-loopgantt-mcp-server -- npx -y @loopgantt/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-loopgantt-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@loopgantt/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add com-loopgantt-mcp-server --command npx --arg -y --arg @loopgantt/mcp-server
mcp_servers:
com-loopgantt-mcp-server:
command: "npx"
args: ["-y", "@loopgantt/mcp-server"] {
"McpServers": {
"com-loopgantt-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@loopgantt/mcp-server"
]
}
}
} assistant mcp add com-loopgantt-mcp-server -t stdio -c npx -a -y @loopgantt/mcp-server
{
"mcpServers": {
"com-loopgantt-mcp-server": {
"command": "npx",
"args": [
"-y",
"@loopgantt/mcp-server"
]
}
}
} 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.
- 22 Sept 26 +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.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 11 Sept 26 +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.
- 9 Sept 26 +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.
- 7 Sept 26 +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.
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 22 Sept 2026 · Analysed npm/@loopgantt/mcp-server@1.4.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 95 packages
| Packages resolved | 95 |
|---|---|
| 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 →
create_gantt ~248
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional one-line description |
| holidays | array | – | Non-working dates, YYYY-MM-DD |
| name | string | yes | Project name |
| startDate | string | – | YYYY-MM-DD (defaults to today) |
| tasks | array | yes | – |
| workDays | array | – | Working weekdays as ISO numbers 1 (Mon) … 7 (Sun). Default Mon–Fri. |
No output schema declared.
No examples provided.
get_template ~43
Get one industry template by slug: its task list with durations, ready to adapt and pass to create_gantt.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Template slug from list_templates |
No output schema declared.
No examples provided.
list_templates ~40
List LoopGantt's industry project templates with task counts and typical durations. Pick one, fetch it with get_template, adapt it, then create_gantt.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
schedule_project ~163
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| workDays | array | – | Working weekdays as ISO numbers 1 (Mon) … 7 (Sun). Default Mon–Fri. |
No output schema declared.
No examples provided.
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.