Decknote
REMOTE · DECKNOTE.APP
Kanban boards your AI agent can use: add, complete, move and recall tasks with your team.
Available components
Last scanned (7 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 5 Nov 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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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 Usability78
- 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
- Context-footprint check failed: tool/resource definitions use about 28095 tokens (~131/item across 213 items; 211 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% 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
- All 38 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 213 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities73
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
- Supports UI / widget rendering.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.
- 5 Nov 26 +1
- Tool “share_board” rewrote its description, which is the text the model reads security
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 0
- Tool “email_invoice” rewrote its description, which is the text the model reads security
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
- New tool “add_expense_receipt”, which the server declares destructive security
- New tool “approve_time_off”, which the server declares destructive security
- New tool “approve_timesheet”, which the server declares destructive security
- New tool “convert_estimate_to_project”, which the server declares destructive security
- New tool “create_webhook”, which the server declares destructive security
- New tool “delete_expense_receipt”, which the server declares destructive security
- New tool “delete_webhook”, which the server declares destructive security
- New tool “reject_time_off”, which the server declares destructive security
- New tool “reject_timesheet”, which the server declares destructive security
- New tool “submit_timesheet”, which the server declares destructive security
- New tool “test_webhook”, which the server declares destructive security
- New tool “update_webhook”, which the server declares destructive security
- New tool “withdraw_timesheet”, which the server declares destructive security
- Tool “add_time_off” rewrote its description, which is the text the model reads security
- Tool “get_profitability_report” rewrote its description, which is the text the model reads security
- Tool “list_time_off” rewrote its description, which is the text the model reads security
- Tool “update_time_off” rewrote its description, which is the text the model reads security
- Schema quality: 25131 → 28016 ▼ functional
- New tool “get_assignments_report” functional
- New tool “get_invoice_pdf” functional
- New tool “list_timesheets” functional
- New tool “list_webhooks” functional
- “list_time_off” added an optional parameter “status” cosmetic
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 5 Nov 2026 · Probed https://decknote.app/api/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=decknote.app | CN=YR1,O=Let's Encrypt,C=US | 5 Sept 2026 | 4 Dec 2026 | RSA 4096 | SHA256-RSA | 55b40f7bd6ba9822ba45d7f1e82b2b9f873 |
| SANs: decknote.app, notes.devcloudsoftware.com, www.decknote.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 decknote.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| decknote.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="Decknote MCP"
Bearer realm="Decknote MCP"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://challenges.cloudflare.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://www.googletagmanager.com https://www.google-analytics.com; font-src 'self' data:; connect-src 'self' https://www.google-analytics.com https://www.googletagmanager.com https://region1.google-analytics.com https://www.google.com/g/collect https://jentry.devcloudsoftware.com https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com; worker-src 'self'; manifest-src 'self'; frame-ancestors 'self'; base-uri 'self'; form-action 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://decknote.app/api/v1/mcp | Verified | 200 | |
| http (plaintext) | http://decknote.app/api/v1/mcp | HTTPS enforced | 302 | https://decknote.app/api/v1/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 →
update_member Change member role ~57
Changes a member's role on a board the user owns: EDITOR (can change things) or VIEWER (read only).
| Name | Type | Req | Description |
|---|---|---|---|
| boardId | string | yes | – |
| role | string | yes | – |
| userId | string | yes | – |
No output schema declared.
No examples provided.
update_page Update page ~173
Changes a page's title and/or body (Markdown, replacing the whole body). It needs the rev from when the page was read: if somebody saved in between, the save is refused with the reason and nothing is overwritten. Pinning, archiving and comments do not change the rev. A discussion's text is edited by its author and the project owner; an archived page is read-only. A page with images, or with a body longer than 100,000 characters, keeps its body: only its title changes. Needs the editor role on the project.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | The whole new body, in Markdown. |
| pageId | string | yes | The page (a note or a discussion). |
| rev | string | yes | The rev returned when the page was read. |
| title | string | – | – |
No output schema declared.
No examples provided.
update_project_settings Update project settings ~292
Turns a board into a project or changes its settings: client (one of the user's own), status, budget type with its hours or amount, default hourly rate, billable by default, start and due dates. null clears a value. A new rate applies to time logged from then on. Only the board's owner can do this.
| Name | Type | Req | Description |
|---|---|---|---|
| billableByDefault | boolean | – | Whether time is billable unless a task says otherwise. |
| boardId | string | yes | – |
| budgetAmount | number|string|null | – | Money budget. An amount in the currency's main unit, e.g. 85 or "85.50" (not cents). Used when budgetType is money. |
| budgetHours | number|string|null | – | Hours budget, e.g. 40 or "40h". Used when budgetType is hours. |
| budgetType | string | – | What the budget counts: tracked hours, or the billable amount. |
| clientId | string|null | – | One of the user's clients; null unlinks it. |
| dueDate | string|null | – | YYYY-MM-DD. |
| hourlyRate | number|string|null | – | Hourly rate for this project, over the client's. An amount in the currency's main unit, e.g. 85 or "85.50" (not cents). |
| startDate | string|null | – | YYYY-MM-DD. |
| status | string | – | – |
No output schema declared.
No examples provided.
update_recurring_invoice Update recurring invoice ~252
Changes a recurring invoice: how often, the next date (a new cadence counts from it), endAfter (null = no end), what happens to each new invoice, the days to pay, or pauses it (active false) and resumes it (active true; dates missed while paused are skipped). The lines stay as they were copied. Pausing needs nothing more; a change after which new invoices are sent or emailed needs confirm: true, and without it the result is a preview.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | – |
| active | boolean | – | false pauses it, true resumes it. |
| confirm | boolean | – | true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. |
| endAfter | integer|string|null | – | Invoices left to make, 1 to 500; null = no end. |
| every | integer|string | – | 1 to 12. |
| interval | string | – | – |
| nextDate | string | – | The new next date, today or later, YYYY-MM-DD. |
| paymentTermsDays | integer|string | – | – |
| recurringId | string | yes | The recurring invoice. |
No output schema declared.
No examples provided.
update_task Update task ~195
Edits a task: title, description, due date, start date, repeat or cover (a color, or one of the task's image attachments). The description accepts Markdown and replaces the card's whole page. null clears a date, the repeat or the cover.
| Name | Type | Req | Description |
|---|---|---|---|
| cardId | string | yes | – |
| coverColor | string|null | – | A color cover, or null to remove the cover. Replaces an image cover. |
| coverImageAttachmentId | string|null | – | Use one of the card's image attachments as its cover (null removes it). |
| description | string | – | – |
| dueDate | string|null | – | ISO 8601, or null to clear. |
| recurrence | string|null | – | Repeat on archive (Pro), or null to stop repeating. |
| startDate | string|null | – | ISO 8601, or null to clear (shown on the timeline). |
| title | string | – | – |
No output schema declared.
No examples provided.
update_time_entry Update time entry ~195
Changes a finished time entry: its duration, day, note, whether it is billable, or the task it is on (null takes it off any task). A person edits their own entries and the project owner edits anyone's. Time already billed to a client, and a timer still running, cannot be edited.
| Name | Type | Req | Description |
|---|---|---|---|
| billable | boolean | – | – |
| cardId | string|null | – | Move the entry to this task of the same project; null removes the task. |
| day | string | – | The day worked, YYYY-MM-DD. |
| duration | string | – | A duration the way a person writes it: 90, 90m, 1h, 1h30, 1:30 or 1.5h. A bare number is minutes. Up to 24 hours per entry. |
| entryId | string | yes | – |
| note | string | – | Up to 500 characters. |
No output schema declared.
No examples provided.
update_time_off Update time off ~255
Changes the kind, the days, the minutes off each day or the note of a time off; what is not given stays as it was, and null minutes make it the whole working day again. A person changes their own (changing the kind, the days or the minutes of an approved or rejected one asks the owners for approval again); on Pro, the owner of a project changes the time off of its editors (the note stays the person's). The whole result is checked again: at most 366 days, ending on or after the first day.
| Name | Type | Req | Description |
|---|---|---|---|
| endDay | string | – | The last day off, YYYY-MM-DD. |
| kind | string | – | vacation, sick or other. Default vacation. |
| minutesPerDay | integer|null | – | Minutes off each day (240 is half a working day), between 1 and the person's working day. null or missing: the whole working day. |
| note | string | – | Up to 300 characters. Only the person writes it and only they read it back. |
| startDay | string | – | The first day off, YYYY-MM-DD. |
| timeOffId | string | yes | A time off of the user or of an editor of one of the user's projects. |
No output schema declared.
No examples provided.
update_webhook Update webhook ~144
Changes one of the account's webhooks: the event types it sends, turns it off or on (enabled), or replaces its signing secret (rotateSecret: the new one comes back once, and the old one stops verifying). Turning it on needs confirm: true, since events leave Decknote again; without it the result is a preview.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. |
| enabled | boolean | – | – |
| events | array | – | – |
| rotateSecret | boolean | – | – |
| webhookId | string | yes | – |
No output schema declared.
No examples provided.
void_invoice Void invoice ~136
Voids a sent invoice or estimate: it cannot change any more, its number is kept, and the hours and expenses it had taken go back to the project's unbilled work. A draft is not voided (it is deleted). An invoice with payments recorded, and an estimate whose invoice still stands, cannot be voided. Needs confirm: true; without it the result is a preview.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. |
| invoiceId | string | yes | The invoice or estimate. |
No output schema declared.
No examples provided.
watch_task Watch task ~46
Starts or stops watching a task (watchers are notified of new comments on it). Affects only the user.
| Name | Type | Req | Description |
|---|---|---|---|
| cardId | string | yes | – |
| watching | boolean | yes | – |
No output schema declared.
No examples provided.
withdraw_timesheet Withdraw a submitted week ~76
Takes back a week the user submitted that is still waiting for approval: its hours can be changed again and the week can be submitted again later. An approved week can only be reopened by the project owner.
| Name | Type | Req | Description |
|---|---|---|---|
| timesheetId | string | yes | A week handed in for approval (the user's own, or one handed to the user). |
No output schema declared.
No examples provided.
How do I install the Decknote MCP server?
Decknote is a hosted endpoint at https://decknote.app/api/v1/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 · decknote.app
claude mcp add --transport http app-decknote-decknote 'https://decknote.app/api/v1/mcp'
What is the Decknote MCP server?
Decknote is an MCP server listed in the public MCP registry as app.decknote/decknote. Kanban boards your AI agent can use: add, complete, move and recall tasks with your team. This page covers its hosted endpoint (https://decknote.app/api/v1/mcp).
Is the Decknote MCP server safe to use?
Decknote scores 87 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 Decknote MCP server expose?
Decknote exposes 211 tools: overview, list_boards, create_board, create_list, search_tasks, and 206 more. Their descriptions and schemas cost roughly 27,349 tokens of context every time the server is loaded.
Does the Decknote MCP server require authentication?
Yes. Decknote 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 Decknote MCP server still maintained?
Decknote is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.