Ganty MCP
REMOTE · GANTY.APP · SCANNED SEP 20
Gantt chart SaaS with server-side critical path and dependency-aware shift-impact tools, plus CRUD.
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1526 tokens (~101/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 62% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_project" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Ganty MCP server?
Ganty MCP is a hosted endpoint at https://ganty.app/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 · ganty.app
claude mcp add --transport http app-ganty-mcp-server 'https://ganty.app/api/mcp'
{
"mcpServers": {
"app-ganty-mcp-server": {
"url": "https://ganty.app/api/mcp"
}
}
} {
"servers": {
"app-ganty-mcp-server": {
"type": "http",
"url": "https://ganty.app/api/mcp"
}
}
} [mcp_servers.app-ganty-mcp-server] url = "https://ganty.app/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-ganty-mcp-server": {
"type": "remote",
"url": "https://ganty.app/api/mcp",
"enabled": true
}
}
} openclaw mcp add app-ganty-mcp-server --url 'https://ganty.app/api/mcp' --transport streamable-http
mcp_servers:
app-ganty-mcp-server:
url: "https://ganty.app/api/mcp" {
"McpServers": {
"app-ganty-mcp-server": {
"Transport": "http",
"Url": "https://ganty.app/api/mcp"
}
}
} assistant mcp add app-ganty-mcp-server -t streamable-http -u 'https://ganty.app/api/mcp'
{
"mcpServers": {
"app-ganty-mcp-server": {
"type": "http",
"url": "https://ganty.app/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.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
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 20 Sept 2026 · Probed https://ganty.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ganty.app | CN=YR1,O=Let's Encrypt,C=US | 19 Sept 2026 | 18 Dec 2026 | RSA 2048 | SHA256-RSA | 6b065e90ab56bda77ee02bc1173508bdac6 |
| SANs: ganty.app | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ganty.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| ganty.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="Ganty MCP", resource_metadata="https://ganty.app/.well-known/oauth-protected-resource/api/mcp"
Bearer realm="Ganty MCP", resource_metadata="https://ganty.app/.well-known/oauth-protected-resource/api/mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Protected resource metadata
| Document | https://ganty.app/.well-known/oauth-protected-resource/api/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://ganty.app/api/mcp |
| Authorisation server | https://ganty.app |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ganty.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://ganty.app/api/mcp | HTTPS enforced | 308 | https://ganty.app/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 →
add_dependency ~65
Add a finish-to-start dependency between two tasks in the same project.
| Name | Type | Req | Description |
|---|---|---|---|
| lagDays | number | – | Optional lag in days after predecessor finishes |
| predecessorId | string | yes | Task that must finish first |
| successorId | string | yes | Task that can start after predecessor finishes |
No output schema declared.
No examples provided.
create_milestone ~64
Add a milestone (key date) to a project.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | – | Hex color (defaults to #f59e0b) |
| date | string | yes | YYYY-MM-DD |
| name | string | yes | – |
| projectId | string | yes | – |
No output schema declared.
No examples provided.
create_project ~108
Create a new project in a workspace. Returns the created project. Subject to plan-based project count limits.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | – | Hex color (e.g. #3b82f6). Defaults to blue. |
| description | string | – | – |
| endDate | string | – | YYYY-MM-DD. Optional. |
| name | string | yes | Project name |
| startDate | string | – | YYYY-MM-DD. Defaults to today. |
| workspaceId | string | yes | Workspace ID (UUID) |
No output schema declared.
No examples provided.
create_task ~152
Create a new task in a project. Dates must be in YYYY-MM-DD format. End date is exclusive (a 1-day task has end = start + 1 day).
| Name | Type | Req | Description |
|---|---|---|---|
| assigneeId | string | – | Profile ID of the assignee |
| color | string | – | Hex color (e.g. #3b82f6) |
| description | string | – | – |
| endDate | string | yes | YYYY-MM-DD (exclusive end) |
| name | string | yes | – |
| parentId | string | – | Parent task ID for hierarchy |
| progress | number | – | – |
| projectId | string | yes | – |
| startDate | string | yes | YYYY-MM-DD |
| status | string | – | – |
No output schema declared.
No examples provided.
delete_project ~41
Permanently delete a project. All tasks, milestones, and dependencies inside the project are also removed. This cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | – |
No output schema declared.
No examples provided.
delete_task ~29
Delete a task. Child tasks and dependencies are removed as well.
| Name | Type | Req | Description |
|---|---|---|---|
| taskId | string | yes | – |
No output schema declared.
No examples provided.
get_critical_path ~212
Calculate the critical path of a project on the Ganty side and return it as data (don't ask the model to reason over raw task lists). Uses forward/backward CPM with progress-aware remaining duration. Returns critical_path tasks in order, per-task earliest/latest start/finish + slack, project_end_date, and total_duration_days. v1 limitations: Finish-to-Start dependencies only (Ganty has no other types), calendar days by default (business_days=true skips Sat/Sun but no holiday table), ignores multi-period segments, no resource calendars. Returns { error: 'cyclic_dependency', cycle } if a cycle is detected.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of_date | string | – | YYYY-MM-DD. Start point for projecting remaining work. Defaults to today. |
| business_days | boolean | – | If true, skip Saturday and Sunday in duration calculations. National holidays are still treated as working days (v1 has no holiday table). Defaults to false. |
| project_id | string | yes | Project ID (UUID) |
No output schema declared.
No examples provided.
get_task ~35
Get detailed information about a single task, including assignees and dependencies.
| Name | Type | Req | Description |
|---|---|---|---|
| taskId | string | yes | Task ID (UUID) |
No output schema declared.
No examples provided.
list_milestones ~33
List milestones in a project (key dates such as launch or review gates).
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | – |
No output schema declared.
No examples provided.
list_projects ~30
List all projects in a workspace (excluding archived).
| Name | Type | Req | Description |
|---|---|---|---|
| workspaceId | string | yes | Workspace ID (UUID) |
No output schema declared.
No examples provided.
list_tasks ~77
List tasks in a project. Supports optional filtering by name (search), status, and assignee.
| Name | Type | Req | Description |
|---|---|---|---|
| assigneeId | string | – | Filter by assignee profile ID |
| projectId | string | yes | Project ID (UUID) |
| search | string | – | Filter task name by case-insensitive substring |
| status | string | – | – |
No output schema declared.
No examples provided.
list_workspaces ~21
Get all workspaces the authenticated user is a member of.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
reschedule_and_propagate ~343
Compute the downstream impact of shifting a single task. Default is dry_run (no DB writes); set mode='commit' to actually persist the changes. Cascades forward only (no pull): successors are pushed only if their predecessor's new end + lag would violate their current start. Tasks with progress=100 are treated as pinned; pass pinned_task_ids for additional pins. When a pin would be violated, the change is recorded in 'conflicts' and not propagated further. In mode='commit', if any conflicts exist nothing is written (all-or-nothing transaction). Same v1 limitations as get_critical_path: FS only, calendar days by default, no holiday table, ignores multi-period segments.
| Name | Type | Req | Description |
|---|---|---|---|
| business_days | boolean | – | If true, skip Sat/Sun in duration math. Defaults to false. |
| mode | string | – | dry_run (default): compute and return; do not modify DB. commit: write to DB in a single transaction, but only if no conflicts. Audit logged on commit. |
| new_start_date | string | – | Absolute new start date as YYYY-MM-DD. Specify exactly one of shift or new_start_date. |
| pinned_task_ids | array | – | Additional task IDs to treat as pinned (in addition to progress=100 tasks). |
| respect_dependencies | boolean | – | If false, only the named task moves; successors are not cascaded. Default true. |
| shift | string | – | Relative shift like '+3d' (push back) or '-2d' (pull earlier). Specify exactly one of shift or new_start_date. |
| task_id | string | yes | Task ID (UUID) to shift |
No output schema declared.
No examples provided.
set_task_progress ~59
Update the progress percentage of a task (0-100). Status is auto-derived: 0=not_started, 1-99=in_progress, 100=done.
| Name | Type | Req | Description |
|---|---|---|---|
| progress | number | yes | – |
| taskId | string | yes | – |
No output schema declared.
No examples provided.
update_task ~101
Update fields of an existing task. Only provided fields will be modified.
| Name | Type | Req | Description |
|---|---|---|---|
| assigneeId | string|null | – | null to unassign |
| color | string | – | – |
| description | string | – | – |
| endDate | string | – | YYYY-MM-DD |
| name | string | – | – |
| progress | number | – | – |
| startDate | string | – | YYYY-MM-DD |
| status | string | – | – |
| taskId | string | yes | – |
No output schema declared.
No examples provided.
What is the Ganty MCP server?
Ganty MCP is listed in the public MCP registry as app.ganty/mcp-server. Gantt chart SaaS with server-side critical path and dependency-aware shift-impact tools, plus CRUD. This page covers its hosted endpoint (https://ganty.app/api/mcp).
Is the Ganty MCP server safe to use?
Ganty MCP scores 90 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 Ganty MCP server expose?
Ganty MCP exposes 15 tools: list_workspaces, list_projects, create_project, delete_project, list_tasks, and 10 more. Their descriptions and schemas cost roughly 1,370 tokens of context every time the server is loaded.
Does the Ganty MCP server require authentication?
Yes. Ganty MCP asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Ganty MCP server still maintained?
Ganty MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.