com.loopgantt/mcp-server
REMOTE · LOOPGANTT.COM · 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 against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1384 tokens (~51/item across 27 items; 4 tools + 23 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 87% 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 6 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 is a hosted endpoint at https://loopgantt.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · loopgantt.com
claude mcp add --transport http com-loopgantt-mcp-server 'https://loopgantt.com/api/mcp'
{
"mcpServers": {
"com-loopgantt-mcp-server": {
"url": "https://loopgantt.com/api/mcp"
}
}
} {
"servers": {
"com-loopgantt-mcp-server": {
"type": "http",
"url": "https://loopgantt.com/api/mcp"
}
}
} [mcp_servers.com-loopgantt-mcp-server] url = "https://loopgantt.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-loopgantt-mcp-server": {
"type": "remote",
"url": "https://loopgantt.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-loopgantt-mcp-server --url 'https://loopgantt.com/api/mcp' --transport streamable-http
mcp_servers:
com-loopgantt-mcp-server:
url: "https://loopgantt.com/api/mcp" {
"McpServers": {
"com-loopgantt-mcp-server": {
"Transport": "http",
"Url": "https://loopgantt.com/api/mcp"
}
}
} assistant mcp add com-loopgantt-mcp-server -t streamable-http -u 'https://loopgantt.com/api/mcp'
{
"mcpServers": {
"com-loopgantt-mcp-server": {
"type": "http",
"url": "https://loopgantt.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 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 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.
- 12 Sept 26 +1
- Server version: 1.5.0 → 1.6.0 functional
- 10 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.
- 8 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.
- 6 Sept 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.
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 · Probed https://loopgantt.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=loopgantt.com | CN=WE1,O=Google Trust Services,C=US | 8 Sept 2026 | 7 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 73d44df3b2114e8c0eb4bf3be4f3714a |
| SANs: loopgantt.com, *.loopgantt.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of loopgantt.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| loopgantt.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://*.lemonsqueezy.com https://www.googletagmanager.com https://accounts.google.com https://apis.google.com https://www.gstatic.com https://js.stripe.com https://stats.loopends.com; style-src 'self' 'unsafe-inline' https://accounts.google.com; img-src 'self' data: blob: https:; font-src 'self' data:; connect-src 'self' https://db.loopgantt.com wss://db.loopgantt.com https://*.supabase.co wss://*.supabase.co https://api.groq.com https://*.lemonsqueezy.com https://api.minimax.io https://www.google-analytics.com https://*.google-analytics.com https://*.analytics.google.com https://www.googletagmanager.com https://www.google.com https://accounts.google.com https://oauth2.googleapis.com https://www.googleapis.com https://stats.loopends.com; frame-src 'self' https://*.lemonsqueezy.com https://accounts.google.com https://js.stripe.com; worker-src 'self' blob:; media-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'none'; form-act |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://loopgantt.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://loopgantt.com/api/mcp | HTTPS enforced | 302 | https://loopgantt.com/api/mcp |
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 ~375
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 project start). 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. Tasks with a due date take deadline: YYYY-MM-DD (a marker - the reply reports the fit). Use create_gantt when the user wants a chart to open, export or save; use schedule_project instead for what-if date math where nothing should be stored.
| Name | Type | Req | Description |
|---|---|---|---|
| deadline | string | – | Optional deadline YYYY-MM-DD - drawn on the chart; compare with the returned projectEndDate and warn the user if the plan overshoots |
| 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 ~198
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 |
|---|---|---|---|
| deadline | string | – | Optional deadline YYYY-MM-DD - drawn on the chart; compare with the returned projectEndDate and warn the user if the plan overshoots |
| 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 hosted endpoint (https://loopgantt.com/api/mcp).
Is the com.loopgantt/mcp-server server safe to use?
com.loopgantt/mcp-server scores 81 out of 100 on VerifyMCP. 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 656 tokens of context every time the server is loaded.
Does the com.loopgantt/mcp-server server require authentication?
No. We connected to com.loopgantt/mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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.