mcp-registry/com.loopgantt/mcp-server · v1.6.0
As of 2026-10-19 22:21 UTC, the Loopgantt MCP server is up with a Glimind reliability score of 83/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 8 outages in 90 days, with a median recovery of 6 minutes.
Create scheduled Gantt charts with critical path from a plain-language plan — no account or key.
Claude Code
claude mcp add --transport http loopgantt-mcp-server https://loopgantt.com/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"loopgantt-mcp-server": {
"type": "http",
"url": "https://loopgantt.com/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
4 of 4 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
2 parameter(s) across 2 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Handshake + tools/list takes ~1,880 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.loopgantt%2Fmcp-server/fixes
{
"name": "create_gantt",
"description": "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. Only add a dependency where a task truly needs another one finished - independent tasks should run in PARALLEL (share a predecessor, or take no dependencies at all and start at the ",
"inputSchema": {
"type": "object",
"required": [
"name",
"tasks"
],
"properties": {
"name": {
"type": "string",
"description": "Project name"
},
"tasks": {
"type": "array",
"items": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"description": "Task name"
},
"parent": {
"type": "integer",
"minimum": 0,
"description": "Position (0-based) of an EARLIER task with isPhase=true that this task belongs to"
},
"isPhase": {
"type": "boolean",
"description": "Top-level phase (a group). Tasks join it with parent = this position. Phases take no dependencies and no parent; their dates become the envelope of their tasks."
},
"deadline": {
"type": "string",
"description": "Finish-by date YYYY-MM-DD for a task with a due date (essay due, exam day, launch). A MARKER: the task is still scheduled normally and the reply reports its fit - buffer or days late."
},
"duration": {
"type": "integer",
"minimum": 0,
"description": "Working days (default 1). 0 makes the task a milestone."
},
"description": {
"type": "string"
},
"isMilestone": {
"type": "boolean",
"description": "Milestone (zero duration, drawn as a diamond)"
},
"dependencies": {
"type": "array",
"items": {
"oneOf": [
{
"type": "integer",
"minimum": 0
},
{
"type": "object",
"required": [
"task"
],
"properties": {
"lag": {
"type": "integer"
},
"task": {
"type": "integer",
"minimum": 0
},
"type": {
"enum": [
"FS",
"SS",
"FF",
"SF"
],
"type": "string"
}
}
}
]
},
"description": "Predecessors: positions (0-based) of EARLIER tasks in this list, or objects { task, type: FS|SS|FF|SF, lag } for typed links / lag in days"
}
}
},
"maxItems": 300,
"minItems": 1
},
"deadline": {
"type": "string",
"description": "Optional deadline YYYY-MM-DD - drawn on the chart; compare with the returned projectEndDate and warn the user if the plan overshoots"
},
"holidays": {
"type": "array",
"items": {
"type": "string"
},
"description": "Non-working dates, YYYY-MM-DD"
},
"workDays": {
"type": "array",
"items": {
"type": "integer",
"maximum": 7,
"minimum": 1
},
"description": "Working weekdays as ISO numbers 1 (Mon) … 7 (Sun). Default Mon–Fri."
},
"startDate": {
"type": "string",
"description": "YYYY-MM-DD (defaults to today)"
},
"description": {
"type": "string",
"description": "Optional one-line description"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "get_template",
"description": "Get one industry template by slug: its task list with durations, ready to adapt and pass to create_gantt.",
"inputSchema": {
"type": "object",
"required": [
"slug"
],
"properties": {
"slug": {
"type": "string",
"description": "Template slug from list_templates"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "list_templates",
"description": "List LoopGantt's industry project templates with task counts and typical durations. Pick one, fetch it with get_template, adapt it, then create_gantt.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.loopgantt/mcp-server"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.loopgantt/mcp-server"}) over MCP.
create_gantt ~737 tokensschedule_project ~688 tokensget_template ~80 tokenslist_templates ~67 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.loopgantt%2Fmcp-server?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.loopgantt%2Fmcp-server?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.loopgantt%2Fmcp-server.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.loopgantt%2Fmcp-server.svg :target: https://glimind.com/server/mcp-registry%2Fcom.loopgantt%2Fmcp-server?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:b1af1394581b0f98…, first seen 2026-10-17, included at leaf 14054 of 29,124. Version history · verify what your client received.
Compare: most reliable productivity servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-19 22:21 UTC, the Loopgantt MCP server is up with a Glimind reliability score of 83/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 8 outages in 90 days, with a median recovery of 6 minutes.
Loopgantt MCP server advertises 4 tools, including create_gantt, get_template, list_templates, schedule_project.
Point your MCP client at this streamable-http endpoint: https://loopgantt.com/api/mcp
Glimind scanned all 4 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.