Git-Based MCP Todo Server (thijs-hakkenberg/mcp_todo) is an MCP server listed on the M8ven Trust Index. It scores 56 out of 100, grade D. It declares 17 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
56/100

Git-Based MCP Todo Server

A Model Context Protocol server that uses Git as a backend for a collaborative todo system, enabling natural language interaction with Claude Desktop/Claude Code. It features a web-based Kanban board and Telegram bot for multi-interface todo management.

→ thijs-hakkenberg/mcp_todo· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

thijs-hakkenberg

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Known vulnerabilities in dependencies: 16 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 1 credential: TELEGRAM_BOT_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes17 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

list_todos

List todos with optional filters and field selection

get_todo

Get a single todo by ID

create_todo

Create a new todo

update_todo

Update an existing todo

delete_todo

Delete (archive) a todo

complete_todo

Mark a todo as done

add_comment

Add a comment to a todo

search_todos

Search todos by text

get_stats

Get todo statistics

sync_repository

Manually trigger repository sync

get_history

Get Git history for todos

batch_create_todos

Create multiple todos in a single operation (supports hierarchical creation)

get_projects

Get list of distinct projects

get_tags

Get list of distinct tags

get_assignees

Get list of distinct assignees

get_priorities

Get list of all priorities

get_filter_options

Get all filter options (projects, tags, assignees, priorities) in one call

// known CVEs in dependencies16 high5 medium9 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.20.2GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.20.2GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.20.2GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

highaxios@1.7.9GHSA-35jp-ww65-95wh

axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`

highaxios@1.7.9GHSA-3g43-6gmg-66jw

axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollution Gadget in Config Merge

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configAUTO_SYNC"": "true",
configCORS_ORIGINCORS origin for web frontend (default: http://localhost:31415)
configGIT_USER_EMAIL"": "you@example.com",
configGIT_USER_NAME"": "Your Name",
configMCP_SERVER_PATH
configSYNC_INTERVAL_SECONDSSync interval in seconds (default: 300)
configTELEGRAM_AUTHORIZED_USER_ID
🔐 secretTELEGRAM_BOT_TOKEN
configTODO_REPO_PATH"": "/Users/you/my-todos",
configTODO_REPO_URL"": "https://github.com/you/my-todos.git",
configVITEST
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

17/17 tools missing one or more hints — list_todos (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_todo (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); create_todo (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +14 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

11/17 tools referenced in tests (65%)

Write tests that reference each tool by name so every tool has at least one test.

Production dependencies are patched

0 critical, 16 high severity in production deps — @modelcontextprotocol/sdk@1.20.2 (high), @modelcontextprotocol/sdk@1.20.2 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/thijs-hakkenberg/mcp_todo?variant=verified)](https://m8ven.ai/mcp/thijs-hakkenberg/mcp_todo)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 029ca210a2846783300cd7b85f9edaf921222b53
code hash: b5ba2d61d929e3f898826f8794f6e1e9c24034abb45784cdbe92958b154f20be
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client