Skip to content

loopgantt.com MCP server

com.loopgantt/mcp-serverloopgantt.comstreamable-httpv1.4.0Scanned

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

21 tools: 1 can delete or cancel things, 12 change things and 8 only read.

Tools: 1 delete, 0 irreversible, 12 write, 8 read.
  • Reads private data · 2
  • Reads text others write · 3
  • Can send data out · 3
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the loopgantt.com MCP server can do

The loopgantt.com MCP server is published by loopgantt.com, a domain the MCP Registry verified. It has 21 tools. It can delete or cancel things (1 tool: delete_task) and create or change data (12 tools: create_gantt, schedule_project, create_project, update_task and 8 more). 8 tools only read.

2 tools read private data (list_meetings and list_links); 3 tools bring in text other people can write (list_comments, list_links and find_by_link); 3 tools can send data out of your system (add_comment, link_external and find_by_link). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 13, 2026, version 1.4.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

21 tools

Deletes or cancels 1Claude Code: deny
  • delete_taskDelete one task in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key) - and every task under it when it is a phase.No findings

    Why it is in this group

    • The name "delete_task" says "delete": a word for removing or ending something.
    Description, as the server wrote it
    Delete one task in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key) - and every task under it when it is a phase. DESTRUCTIVE: ask the user before calling, and pass confirm: true only after they agreed; without it nothing is deleted. The task goes to the project trash (restorable in the app for 30 days).
Changes things 12Claude Code: ask
  • add_commentLeave a comment on a task in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key) — notes, handoffs between agents, questions for a person.Can send data outNo findings

    Why it is in this group

    • The name "add_comment" says "add": a word for a change.

    What it can reach

    • outboundThe name "add_comment" says "add" and "comment": it writes something other people read.
    Description, as the server wrote it
    Leave a comment on a task in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key) — notes, handoffs between agents, questions for a person. It shows in the task timeline, notifies the task watchers and @-mentioned people, and fires the comment.posted webhook.
  • complete_taskMark one task done in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key).No findings

    Why it is in this group

    • The description's first verb is "mark": a word for a change.
    Description, as the server wrote it
    Mark one task done in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key). LoopGantt treats done as status AND 100 % together, so this sets both through the same rule the app uses - never set progress to 100 by hand with update_task and hope the status follows.
  • create_ganttCreate a Gantt chart from a task list — no account or API key needed.No findings

    Why it is in this group

    • The name "create_gantt" says "create": a word for a change.
    Description, as the server wrote it
    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.
  • create_meetingBook a meeting in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key); the key owner is the organizer.No findings

    Why it is in this group

    • The name "create_meeting" says "create": a word for a change.
    Description, as the server wrote it
    Book a meeting in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key); the key owner is the organizer. Every invitee gets a calendar invitation (.ics, works with Apple, Google, Outlook and any other calendar); members with Google or Outlook sync get it straight in that calendar. Link it to a project (and a task) so the team sees it there. videoProvider picks the call: google_meet, teams or zoom only when the account has that connection, custom = the link you put in location, none = no call.
  • create_projectCreate a project in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key).No findings

    Why it is in this group

    • The name "create_project" says "create": a word for a change.
    Description, as the server wrote it
    Create a project in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key). For a keyless chart use create_gantt instead. Pass workflow: "agent_board" for a board a team of agents works on - stages todo, in_progress, blocked, waiting_approval, done (done is the finished stage).
  • create_taskAdd one task to an existing project in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key).No findings

    Why it is in this group

    • The name "create_task" says "create": a word for a change.
    Description, as the server wrote it
    Add one task to an existing project in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key). Put it under a phase with parentId, make it wait for other tasks with dependencies, and hand it to a person with assigneeId or to a bot with agentLabel (e.g. "qa-bot"). Returns the new task id.
  • list_due_soonOpen tasks scheduled to end within the next N days (today included), in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key), earliest end first.No findings

    Why it is in this group

    • The name "list_due_soon" says "list": a word for reading.
    • The description's first verb is "open": a word for a change.
    Description, as the server wrote it
    Open tasks scheduled to end within the next N days (today included), in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key), earliest end first.
  • list_overdueOpen tasks whose scheduled end has passed, in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key), most overdue first.No findings

    Why it is in this group

    • The name "list_overdue" says "list": a word for reading.
    • The description's first verb is "open": a word for a change.
    Description, as the server wrote it
    Open tasks whose scheduled end has passed, in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key), most overdue first.
  • schedule_projectCompute a schedule without storing anything: dates, critical path, float and project end for a task list (same input shape as create_gantt; name optional).No findings

    Why it is in this group

    • The name "schedule_project" says "schedule": a word for a change.
    Description, as the server wrote it
    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.
  • update_taskChange one task in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key).No findings

    Why it is in this group

    • The name "update_task" says "update": a word for a change.
    Description, as the server wrote it
    Change one task in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key). Pass the taskId from list_tasks and only the fields to change. To mark a task done use complete_task — LoopGantt couples status and progress, and complete_task says exactly that. Set agentLabel to claim a task for a bot (null releases it); assigneeId is for a real person.
Only reads 8Show 8 read-only tools
  • get_changesWhat changed in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key) since an instant: tasks created, tasks now done and tasks otherwise updated.No findings

    Why it is in this group

    • The name "get_changes" says "get": a word for reading.
    Description, as the server wrote it
    What changed in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key) since an instant: tasks created, tasks now done and tasks otherwise updated. Built for agents that poll: the first time pass since (e.g. when you last looked); after that pass back BOTH the since and the cursor the previous reply gave you. The cursor resumes exactly after the last task reported, so no task is reported twice and none written in the same millisecond is skipped. Deleted tasks are not reported.
  • get_templateGet one industry template by slug: its task list with durations, ready to adapt and pass to create_gantt.No findings

    Why it is in this group

    • The name "get_template" says "get": a word for reading.
    Description, as the server wrote it
    Get one industry template by slug: its task list with durations, ready to adapt and pass to create_gantt.
  • list_commentsRead the comments on one task in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key), newest first — to pick up a handoff or see what a person decided…Reads text others writeNo findings

    Why it is in this group

    • The name "list_comments" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe name "list_comments" says "list" and "comment": it reads comments, which other people can write.
    • untrusted-inputThe description's first sentence says "read" and "comment": it reads comments, which other people can write.
    Description, as the server wrote it
    Read the comments on one task in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key), newest first — to pick up a handoff or see what a person decided.
  • list_meetingsMeetings in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key): the key owner's meetings in a window, a project's meetings in a window, or the upcomi…Reads private dataNo findings

    Why it is in this group

    • The name "list_meetings" says "list": a word for reading.

    What it can reach

    • private-dataThe name "list_meetings" says "list" and "meeting": it reads calendars.
    • private-dataThe description's first sentence says "meeting": it reads calendars.
    Description, as the server wrote it
    Meetings in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key): the key owner's meetings in a window, a project's meetings in a window, or the upcoming meetings about one task.
  • list_projectsList the projects in the connected LoopGantt account (requires signing in to LoopGantt, or an API key), with each project's workflow stages: use one of those stage ids as a task's …No findings

    Why it is in this group

    • The name "list_projects" says "list": a word for reading.
    Description, as the server wrote it
    List the projects in the connected LoopGantt account (requires signing in to LoopGantt, or an API key), with each project's workflow stages: use one of those stage ids as a task's status.
  • list_tasksList tasks in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key), across every project the account can reach, most recently changed first.No findings

    Why it is in this group

    • The name "list_tasks" says "list": a word for reading.
    Description, as the server wrote it
    List tasks in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key), across every project the account can reach, most recently changed first. Use it to answer "what am I working on", to find a task before changing it, or to catch up on what moved: pass updatedSince (ISO timestamp) for "since I last looked". Each row carries the task id that update_task and complete_task take.
  • list_templatesList LoopGantt's industry project templates with task counts and typical durations.No findings

    Why it is in this group

    • The name "list_templates" says "list": a word for reading.
    Description, as the server wrote it
    List LoopGantt's industry project templates with task counts and typical durations. Pick one, fetch it with get_template, adapt it, then create_gantt.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

18 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 2 private-data tools breaks every one.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out3
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__loopgantt__list_links",
      "mcp__loopgantt__list_meetings"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:41 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
15
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://loopgantt.com/.well-known/oauth-protected-resource/api/mcp
Authorization servers
https://loopgantt.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 15 tools that change things (2 destructive, 13 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://loopgantt.com/api/mcp: tools/list returned 25 tools to an anonymous client, including delete_task (destructive), delete_attachment (destructive), create_gantt (write), schedule_project (write), create_project (write) and 10 more

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • Tools that change things, listed without credentials: 13 to 15
  2. Nov 13, 2026
    • Tools that change things, listed without credentials: 2 to 13
    • RFC 9728 protected resource metadata: none to https://loopgantt.com/.well-known/oauth-protected-resource/api/mcp
    • Authorization servers: none to https://loopgantt.com
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 13 -> 15.View diff
    • Tools that change things, listed without credentials: 13 to 15
  2. Tools17 added.+17 addedView diff
  3. PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 13; RFC 9728 protected resource metadata: none -> https://loopgantt.com/.well-known/oauth-protected-resource/api/mcp; Authorization servers: none -> https://…View diff
    • Tools that change things, listed without credentials: 2 to 13
    • RFC 9728 protected resource metadata: none to https://loopgantt.com/.well-known/oauth-protected-resource/api/mcp
    • Authorization servers: none to https://loopgantt.com
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes

Install

Pinned to version 1.4.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http loopgantt https://loopgantt.com/api/mcp
claude mcp add --transport http loopgantt https://loopgantt.com/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__loopgantt__list_templates",
      "mcp__loopgantt__get_template",
      "mcp__loopgantt__list_projects",
      "mcp__loopgantt__list_tasks",
      "mcp__loopgantt__list_comments",
      "mcp__loopgantt__get_changes",
      "mcp__loopgantt__list_meetings"
    ],
    "ask": [
      "mcp__loopgantt__create_gantt",
      "mcp__loopgantt__schedule_project",
      "mcp__loopgantt__create_project",
      "mcp__loopgantt__update_task",
      "mcp__loopgantt__complete_task",
      "mcp__loopgantt__create_task",
      "mcp__loopgantt__add_comment",
      "mcp__loopgantt__list_overdue",
      "mcp__loopgantt__list_due_soon",
      "mcp__loopgantt__create_meeting",
      "mcp__loopgantt__link_external",
      "mcp__loopgantt__list_links",
      "mcp__loopgantt__find_by_link"
    ],
    "deny": [
      "mcp__loopgantt__delete_task"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as loopgantt. Review it before you use it.

Capability tags behind 6 rules
  • mcp__loopgantt__add_comment outbound
  • mcp__loopgantt__list_comments untrusted-input
  • mcp__loopgantt__list_meetings private-data
  • mcp__loopgantt__link_external outbound
  • mcp__loopgantt__list_links private-data, untrusted-input
  • mcp__loopgantt__find_by_link untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.loopgantt/mcp-server/verify?hash=1a037b800bf2f59fea60f06abb848ab1211049d2bf9f57502232d85e067eba5c" | jq -e '.changed == false'

Pinned hash 1a037b800bf2, from Nov 13, 2026, 16:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.loopgantt/mcp-server/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.loopgantt/mcp-server
[![Anlyon Radar](https://radar.anlyon.com/badge/com.loopgantt/mcp-server.svg)](https://radar.anlyon.com/servers/com.loopgantt/mcp-server)

Source: MCP Registry. Synced Oct 21, 2026, 17:58 UTC.

loopgantt.com MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the loopgantt.com MCP server safe?

No scan can promise that. What its definitions show: 21 tools, 13 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the loopgantt.com MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: delete_task.

Can the loopgantt.com MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the loopgantt.com MCP server have?

21 tools: 1 destructive, 12 write, 8 read. delete_task, create_gantt, schedule_project, create_project, update_task, complete_task, create_task, add_comment and 13 more.

Does the loopgantt.com MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the loopgantt.com MCP server send data to outside services?

3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): add_comment, link_external and find_by_link.

Has the loopgantt.com MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.