Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Todour

REMOTE · TODOUR.COM

Manage and search todo.txt tasks, projects, and comments through TodourWeb.

Available components

77 Trust /100

Last scanned (13 hours ago)

Scores higher than 67% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Productivity and Notes

Trust breakdown (7 categories)

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 Security91
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 870 tokens (~66/item across 13 items; 13 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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 Nov 26 +1
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 20 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 19 Nov 26 +1
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 18 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 17 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 16 Nov 26 +38
    • Transport: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Authorization: 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. security
    • MCP protocol: unverified → fail ▼ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Schema quality: fail functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: good functional
    • First check of Tool coverage: 100 functional
  • 15 Nov 26 36

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://todour.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=todour.com CN=YE1,O=Let's Encrypt,C=US 14 Oct 2026 12 Jan 2027 ECDSA 256 ECDSA-SHA384 50a152d1aad741648c74525fcd70b9d9e1d
SANs: todour.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of todour.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
todour.com. DS published 2371 13 Verified
todour.com. Verified address RRset verified with the apex keys
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
Header Value
strict-transport-security max-age=63072000; includeSubDomains

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://todour.com/mcp Verified 200
http (plaintext) http://todour.com/mcp HTTPS enforced
MCP tools · 13 exposed · ~870 tokens

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 →

Tool Tokens
add_comment ~37

Add a comment to a task the caller can see.

NameTypeReqDescription
bodystringyesComment text
idstringyesTask id

No output schema declared.

No examples provided.

complete_task ~36

Complete or reopen a task. Completing a task with a rec: token generates the next recurrence.

NameTypeReqDescription
idstringyesTask id

No output schema declared.

No examples provided.

create_task ~102

Create a new task from todo.txt content. The content must be a valid todo.txt formatted string. Examples: '(A) Call dentist @phone +personal due:2025-12-31', 'Buy groceries @errands +home', 'Weekly report +work rec:+1w'. The server will parse and normalize the content (shorthand like d:→due:, date format conversion, etc.).

NameTypeReqDescription
contentstringyestodo.txt formatted task content

No output schema declared.

No examples provided.

get_export ~79

Return all visible open tasks as a single block for context injection. Pass include_completed: true to also include completed and skipped tasks.

NameTypeReqDescription
formatstring–'json' (default), 'md' (Markdown checklist), or 'txt' (todo.txt)
include_completedboolean–Set to true to also include completed and skipped tasks

No output schema declared.

No examples provided.

get_task ~24

Get a single task by id.

NameTypeReqDescription
idstringyesTask id

No output schema declared.

No examples provided.

list_comments ~27

List comments on a task the caller can see.

NameTypeReqDescription
idstringyesTask id

No output schema declared.

No examples provided.

list_tasks ~140

List the current user's visible (own + shared) tasks, optionally filtered. By default only open (incomplete) tasks are returned; pass include_completed: true to also include completed and skipped tasks. Filter uses the same syntax as the app: '+project', '@context', 'due:YYYY-MM-DD', negation with '!'. Returns tasks as JSON array with id, content, projects, contexts, due_on, and other fields.

NameTypeReqDescription
filterstring–Optional filter expression, e.g. '@work +trip due:2025-01-01'
include_completedboolean–Set to true to also return completed and skipped tasks

No output schema declared.

No examples provided.

procrastinate_task ~32

Push a task's threshold forward by the user's configured procrastinate interval.

NameTypeReqDescription
idstringyesTask id

No output schema declared.

No examples provided.

search_tasks ~178

Search the current user's tasks by free-text query, project, or context. By default only open (incomplete) tasks are searched; pass include_completed: true to also search completed and skipped tasks. Supports: plain text (e.g. 'dentist'), projects (e.g. '+work'), contexts (e.g. '@office'), due dates (e.g. 'due:today', 'due:overdue', 'due:2025-12-01'), negation (e.g. '!+archived'), OR groups (e.g. '+work || +personal'), and combined queries (e.g. '+work @office dentist').

NameTypeReqDescription
include_completedboolean–Set to true to also search completed and skipped tasks
querystringyesSearch expression, e.g. 'buy @home' or '+work'

No output schema declared.

No examples provided.

set_threshold ~75

Set the caller's threshold (hide-until date) for a task. Supports absolute dates and relative shorthands like '+2d' or '+1w'.

NameTypeReqDescription
datestringyesThreshold value, e.g. '2025-12-31' or '+2d'
idstringyesTask id

No output schema declared.

No examples provided.

share_project ~66

Share a +project with another user by email (read or edit permission).

NameTypeReqDescription
emailstringyesRecipient email address
permissionstring–'read' or 'edit' (default 'edit')
projectstringyesProject name (with or without leading +)

No output schema declared.

No examples provided.

skip_task ~29

Mark a task as skipped (defers it without completing).

NameTypeReqDescription
idstringyesTask id

No output schema declared.

No examples provided.

update_task ~45

Update a task's content (todo.txt). Only the task owner may update.

NameTypeReqDescription
contentstringyesNew todo.txt formatted content
idstringyesTask id

No output schema declared.

No examples provided.

Install

How do I install the Todour MCP server?

Todour is a hosted endpoint at https://todour.com/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 · todour.com

# add to Claude Code
claude mcp add --transport http sverrirvalgeirsson-todourweb 'https://todour.com/mcp'
Common questions

What is the Todour MCP server?

Todour is an MCP server listed in the public MCP registry as io.github.SverrirValgeirsson/todourweb. Manage and search todo.txt tasks, projects, and comments through TodourWeb. This page covers its hosted endpoint (https://todour.com/mcp).

Is the Todour MCP server safe to use?

Todour scores 77 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 Todour MCP server expose?

Todour exposes 13 tools: update_task, skip_task, share_project, set_threshold, search_tasks, and 8 more. Their descriptions and schemas cost roughly 870 tokens of context every time the server is loaded.

Does the Todour MCP server require authentication?

Yes. Todour 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 Todour MCP server still maintained?

Todour is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Todour MCP server?

VerifyMCP ran 13 checks on Todour, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.