moo-tasks (shekarsiri/moo-tasks) is an MCP server listed on the M8ven Trust Index. It scores 64 out of 100, grade C. It declares 54 tools. No publisher has claimed this listing.

C
Caution
64/100

moo-tasks

MCP server for agentic task orchestration and management, enabling AI agents to create goals, plan tasks with acceptance criteria, track dependencies, request human input, and provide proof of completion.

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

shekarsiri

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 →

Install from

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: 2 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
⚠️
Tests do not pass
Either the test suite is broken or the code regressed. Either way the published behaviour can’t be verified by the publisher’s own tests.
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.
// tools this server exposes54 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.

moo_create_goal

Record a human user request verbatim as an overarching Goal with rich Markdown PRD/spec. Tasks will link back to this goal. Caps open tasks to prevent over-planning.

moo_get_goal

Get full details of a goal including rich markdown PRD/spec, status metrics, and all child tasks.

moo_update_goal

Update goal details: rich markdown PRD/specification, title, verbatim prompt, max open tasks cap, or status.

moo_list_goals

List all project goals and their statuses (active, completed, dropped).

moo_get_goal_status

Check goal coverage, open tasks vs cap, loose ends (uncompleted tasks), and completion metrics.

moo_kill_goal

Drop an entire goal and cascade drop all open tasks under it in one action with a mandatory reason.

moo_reopen_goal

Reopen a dropped or completed goal and optionally reopen its tasks.

moo_create_task

Create a task under a goal (or standalone) with detailed technical description, acceptance criteria, type, tags, priority, declared files, and dependencies.

moo_create_tasks_batch

Batch create multiple tasks under a goal with full technical descriptions, criteria, types, tags, and dependencies in a single operation.

moo_update_task

Update task properties: title, description, type, tags, priority, acceptance criteria, declared files, goal, or deferred state.

moo_link_dependencies

Link one or more prerequisite blocker tasks to a task with cycle validation.

moo_unlink_dependencies

Unlink a prerequisite blocker task from a task.

moo_get_next_task

Auto-surface the next unblocked, highest-priority task ready for execution from the active ready queue, with optional file conflict avoidance for parallel agent swarms.

moo_get_task

Retrieve full task details, subtasks, dependencies, notes, and evidence.

moo_list_tasks

List and filter tasks by goal, status, priority, type, tag, agent, deferred state, or search text.

moo_claim_task

Claim a task exclusively before starting work. Verifies lease, agent concurrency limit, loop count, and file touch conflicts.

moo_heartbeat_task

Renew active lease on claimed task while performing long-running work.

moo_release_task

Voluntarily release a claimed task back to the todo queue with optional progress notes.

moo_handoff_task

Handoff an in-flight claimed task from one agent to another with handoff summary.

moo_complete_task

Close a task with mandatory proof of work: commands run, output logs, modified files, and test proofs. Optionally auto-claim next unblocked task.

moo_complete_and_claim_next

Atomically complete a task with proof and immediately claim the next unblocked ready task under the same goal in a single LLM tool call.

moo_verify_task

Mark a task verified done by human or verification subagent.

moo_reject_task

Reject a closed task with a mandatory reason, moving it back to todo and incrementing reopen counter.

moo_ask_human

Escalate a question/blocker to the human user with optional selectable choices and transition task to waiting-on-human.

moo_get_human_inbox

Get the queue of all tasks currently waiting on human answers or decisions.

moo_answer_human

Provide an answer to a task waiting on human guidance, automatically resuming it into the ready queue.

moo_capture_discovered_work

Capture unexpected work found mid-task without dropping current claim. Can be marked must-fix-now (blocker) or deferred.

moo_add_task_note

Append an immutable, timestamped note to a task (e.g. what was tried, reason for failure, architecture insight).

moo_list_task_notes

List all timestamped notes and attempt logs for a task.

moo_log_attempt_failure

Log a structured attempt failure note with error snippet, failure category, hypothesis, and next plan. Increments task attempt counter and automatically escalates to human if loop threshold is exceeded.

moo_drop_task

Drop a task with a mandatory reason (no approval step required).

moo_reopen_task

Reopen a done or dropped task without losing history, incrementing reopen counter.

moo_undo_status_change

Undo the last status transition for a task, rolling back to its previous state.

moo_bulk_drop_tasks

Drop multiple tasks in a single operation with a shared mandatory reason.

moo_bulk_reopen_tasks

Reopen multiple done or dropped tasks back into the todo queue.

moo_record_decision

Record a project-level architectural decision with rationale that outlives individual tasks.

moo_list_decisions

List project architectural decisions so settled questions stay settled during planning.

moo_supersede_decision

Supersede an existing architectural decision with a new choice and rationale.

moo_merge_tasks

Merge two tasks that turn out to be duplicates, moving dependencies and subtasks.

moo_session_resume

Where-did-I-leave-off overview on session start: surfaces abandoned doing tasks, waiting-on-human, ready queue, settled decisions, and orphan tasks.

moo_get_compact_context

Ultra-dense token-optimized context block with active goal, claimed task, acceptance criteria, settled decisions, and file locks. Ideal for system prompt injection.

moo_check_file_lock

Pre-check if specific files are currently locked by another agent holding an active claim, preventing edit collisions.

moo_search

Full-text ranked search (SQLite FTS5) across tasks, acceptance criteria, and architectural decisions (ADR).

moo_get_file_context

Retrieve file-centric historical context: active file locks, past completed tasks, recent notes, and relevant architectural decisions for specific files before modifying code.

moo_quick_start

Fast-path vibe coding tool: Atomically creates a task under a goal and claims it exclusively in a single round-trip, setting declared files, type, tags, and lease duration.

moo_checkpoint

Fast progress checkpoint: Appends a timestamped progress note to the in-flight task and optionally extends lease heartbeat in one call.

moo_import_markdown

Parse a markdown plan, PRD, or task checklist into a Goal and atomic Tasks with dependencies.

moo_export_project

Export all goals, tasks, notes, and decisions in Markdown, JSON, or Plain Text format.

moo_archive_completed

Archive completed and dropped tasks out of the active working list.

moo_list_workspaces

List all registered project workspaces in the global Moo Tasks registry with their paths and git remotes.

moo_get_workspace

Get details of the active workspace or a specific workspace by ID, name, or folder path.

moo_register_workspace

Register a new project directory as a workspace in the global Moo Tasks database.

moo_update_workspace

Update a workspace's display name or git remote URL.

moo_delete_workspace

Unregister/delete a workspace from the global registry.

// known CVEs in dependencies2 high3 low

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

high@fastify/static@7.0.4GHSA-83w8-p2f5-377r

@fastify/static vulnerable to route guard bypass via path traversal

highfastify@4.29.1GHSA-jx2c-rxcm-jvmq

Fastify's Content-Type header tab character allows body validation bypass

low@fastify/static@7.0.4GHSA-8pvw-jcv7-9cmj

@fastify/static vulnerable to Authorization Bypass via Non-Canonical URL Paths

lowfastify@4.29.1GHSA-444r-cwp2-x5xf

fastify: request.protocol and request.host Spoofable via X-Forwarded-Proto/Host from Untrusted Connections

lowfastify@4.29.1GHSA-mrq3-vjjr-p77c

Fastify Vulnerable to DoS via Unbounded Memory Allocation in sendWebStream

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.
configMOO_DB_PATH
configMOO_HOME
// 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

54/54 tools missing one or more hints — moo_create_goal (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); moo_get_goal (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); moo_update_goal (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +51 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

27/54 tools referenced in tests (50%)

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

Tests pass

npm test failed — tests do not pass

Make sure npm test runs cleanly. Common cause: missing build step or missing env vars.

Shell command execution

6 calls in production code run through a shell (src/services/workspace-service.ts:14, src/infrastructure/git/git-context.ts:7, src/infrastructure/git/git-context.ts:13)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Production dependencies are patched

0 critical, 2 high severity in production deps — @fastify/static@7.0.4 (high), fastify@4.29.1 (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 6 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/shekarsiri/moo-tasks?variant=verified)](https://m8ven.ai/mcp/shekarsiri/moo-tasks)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 2423ae1b2c5902b7049b3a5d3874ccb9407d921b
code hash: b0470cc377e59bf08f965ad6f283d275643b01b8fccabbef58d90cd5eed34059
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