Kangram
REMOTE · KANGRAM.APP
Task & board management for AI agents + humans. Kanban, comments, digests via MCP.
Available components
Last scanned (5 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Project Management
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 Security57
- 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 61 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 5797 tokens (~95/item across 61 items; 61 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 9 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_task" 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 61 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
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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 15 Oct 26 +28
- Authorization: pass → unverified ▼ security
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: 0 functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- 13 Oct 26 +3
- Authorization: fail → pass ▲ security
- First check of Authorization: partial security
- 28 Sept 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 Sept 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 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
- 19 Aug 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 18 Oct 2026 · Probed https://kangram.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=kangram.app | CN=WE1,O=Google Trust Services,C=US | 5 Sept 2026 | 4 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 53e77fad7680b98c0ea9b6f25502e446 |
| SANs: kangram.app, *.kangram.app | ||||||
| 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 kangram.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| kangram.app. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://kangram.app/mcp | Verified | 200 | |
| http (plaintext) | http://kangram.app/mcp | HTTPS enforced | 301 | https://kangram.app/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 →
save_session_handoff ~223
Save a session handoff — a durable note on the board recording where the work stands: what was done, what is next, what is blocked, and key links (PRs, issues, branches). Call this at the END of a working session so the next session (possibly a brand-new chat) can pick up exactly where you left off. Use this when the user says 'remember where we left off', 'save our progress', 'save the session state', or 'don't lose this context'. `summary` must be YOUR OWN concise authored recap — never a transcript or list of raw messages.
| Name | Type | Req | Description |
|---|---|---|---|
| board_id | integer | yes | Board ID the handoff belongs to. |
| links | – | – | Optional references — PR/issue URLs, branch names, doc links (e.g. ['https://github.com/o/r/pull/12', 'feat/auth-refactor']). Max 25 single-line items. |
| summary | string | yes | Your authored recap: done / next / blocked. One concise string (max 20000 chars) — not a transcript. |
No output schema declared.
No examples provided.
search_tasks ~164
Use this to find tasks by text, assignee, status, priority, or attention category across all your accessible boards. All filters are optional — combine them to narrow results. Returns up to 50 tasks ordered by last updated.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee_id | integer | – | Filter by assignee user ID. |
| attention | string | – | Filter by attention category: overdue, due_soon, blocked, stale, unassigned. |
| board_id | integer | – | Scope to a specific board ID. |
| priority | string | – | Filter by priority: critical, major, normal, or low. |
| query | string | – | Search query text (matches task title and description). |
| status | string | – | Filter by completion status: 'open' (not done) or 'done'. |
No output schema declared.
No examples provided.
set_board_setting ~154
Use this command to change a board setting. The value is a string coerced to the setting's type server-side (booleans accept on/off, true/false, 1/0, yes/no). Use get_board_settings_schema to discover available keys and types. Example: set autoAddAssignees to "off" to require explicit /addmember on task assignment.
| Name | Type | Req | Description |
|---|---|---|---|
| board_id | integer | yes | Board ID to configure. |
| key | string | yes | Setting key (e.g. "autoAddAssignees"). |
| value | string | yes | New value as a string (coerced to the setting's type). Booleans: on/off, true/false, 1/0. |
No output schema declared.
No examples provided.
transfer_board_ownership ~145
Transfer ownership of a board from the current owner to an existing board member (admin or user role). The current owner is demoted to the specified role (admin by default). Only the current board owner can initiate a transfer. The target must already be a board member — invite them first if needed. This is an irreversible high-impact operation.
| Name | Type | Req | Description |
|---|---|---|---|
| board_id | integer | yes | Board ID to transfer ownership of. |
| demote_current_owner_to | string | – | Role to assign to the current owner after the transfer. Defaults to 'admin'. |
| to_user_id | integer | yes | User ID of the new owner. Must already be a board member (admin or user role). |
No output schema declared.
No examples provided.
transition_task_status ~58
Use this for explicit status moves while keeping other fields unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| board_id | integer | yes | Board ID where the task belongs. |
| status | string | yes | Target status name. |
| task_number | integer | yes | Task number in board scope. |
No output schema declared.
No examples provided.
update_board ~230
Use this to edit board metadata (title, code) and/or the board-level agent prompt. The prompt is the markdown instructions an agent reads when operating on this board (stored as the root file "AGENTS.md"). Pass only the fields you want to change; omitted fields are left untouched. Pass an empty string as prompt to clear the prompt.
| Name | Type | Req | Description |
|---|---|---|---|
| board_id | integer | yes | Board ID to update. |
| code | string | – | New board code (3 letters or digits A-Z/0-9, unique within the namespace). Omit to leave unchanged. |
| prompt | string | – | Markdown agent prompt for this board (stored as the root "AGENTS.md" file). Omit to leave unchanged; pass an empty string to clear. May include YAML frontmatter. |
| title | string | – | New board title. Omit to leave unchanged. |
| visibility | string | – | Set board visibility. 'private' (default) = members-only; 'public' = anyone with the link can view the board read-only (no account required). Owner/admin only. Omit to leave unchanged. |
No output schema declared.
No examples provided.
update_board_file ~146
Upsert a named markdown file on a board. In v1 the conventional name is "AGENTS.md" (the root prompt). Omit content (or pass empty) to clear a file's body. Future versions will support multiple named files; this command is the low-level writer beneath update_board's prompt option.
| Name | Type | Req | Description |
|---|---|---|---|
| board_id | integer | yes | Board ID to write the file on. |
| content | string | – | Markdown content. Omit or pass empty to clear the file body. |
| format | string | – | File format. Defaults to "markdown". |
| name | string | yes | File name (path-like identifier). Use "AGENTS.md" for the root prompt. |
No output schema declared.
No examples provided.
update_checklist_item ~67
Use this to update a checklist item's title or done status. Provide item_id and fields to update.
| Name | Type | Req | Description |
|---|---|---|---|
| done | boolean | – | Set done status (true/false). |
| item_id | integer | yes | Checklist item ID. |
| title | string | – | New title for the item. |
No output schema declared.
No examples provided.
update_member_role ~86
Use this command to change an existing board member's role. Owner/admin only. Cannot target the board owner or promote anyone to owner.
| Name | Type | Req | Description |
|---|---|---|---|
| board_id | integer | yes | Board ID where the member belongs. |
| role | string | yes | New role to assign (admin or user). Cannot assign owner. |
| user_id | integer | yes | User ID of the member whose role to change. |
No output schema declared.
No examples provided.
update_status ~103
Update status by statusId or by boardId+code.
| Name | Type | Req | Description |
|---|---|---|---|
| board_id | integer | – | Board ID for board+code lookup. |
| code | string | – | Existing status code for board+code lookup. |
| color | string | – | New hex color. |
| index | integer | – | New sort index. |
| name | string | – | New display name. |
| new_code | string | – | New machine code value. |
| status_id | integer | – | Target status ID. |
No output schema declared.
No examples provided.
update_task ~135
Use this to edit task title/description/deadline/tags/assignee/status.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | string | – | Assign by username (without @). |
| board_id | integer | yes | Board ID where the task belongs. |
| deadline | string | – | New deadline string. |
| description | string | – | New description. |
| priority | string | – | Set priority: critical, major, normal, or low. |
| status | string | – | Set status by name. |
| tags | array | – | Replace task tags list. |
| task_number | integer | yes | Task number in board scope. |
| title | string | – | New title. |
No output schema declared.
No examples provided.
How do I install the Kangram MCP server?
Kangram is a hosted endpoint at https://kangram.app/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 · kangram.app
claude mcp add --transport http app-kangram-kangram 'https://kangram.app/mcp'
What is the Kangram MCP server?
Kangram is an MCP server listed in the public MCP registry as app.kangram/kangram. Task & board management for AI agents + humans. Kanban, comments, digests via MCP. This page covers its hosted endpoint (https://kangram.app/mcp).
Is the Kangram MCP server safe to use?
Kangram scores 65 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 Kangram MCP server expose?
Kangram exposes 61 tools: list_boards, create_board, update_board, get_board_by_namespace, archive_board, and 56 more. Their descriptions and schemas cost roughly 5,797 tokens of context every time the server is loaded.
Does the Kangram MCP server require authentication?
No. We connected to Kangram without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Kangram MCP server still maintained?
Kangram is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.