Scrumdo MCP Server

scrumdo-mcp PyPI v0.4.5

Published by scrumdollc — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

critical Completed toxic-flow trifecta across toolsMTC-FLOW-002

This server (without client built-ins) exposes a complete data-exfiltration chain: get_agent_run → update_loop_state → create_webhook. Untrusted input is ingested, private data is read, and it can be sent to an external sink via the agent composing the tools (→). Static analysis proves the primitive exists, not that a specific run will occur.

Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.

Location: flow get_agent_run → update_loop_state → create_webhook

Tools 132

Each tool and what it can reach — statically extracted from the published source.

  • create_webhooknetwork egress
  • delete_webhooknetwork egress
  • get_agent_runingests untrusted input
  • get_boardingests untrusted input
  • get_loop_statusingests untrusted input
  • notification_countsingests untrusted input
  • update_loop_statereads sensitive data
  • accept_proofno sensitive capability
  • accept_spec_proposalno sensitive capability
  • add_attachmentno sensitive capability
Show 122 more tools ↓
  • add_card_labelno sensitive capability
  • add_card_memoryno sensitive capability
  • add_commentno sensitive capability
  • add_room_contextno sensitive capability
  • approve_agent_planno sensitive capability
  • archive_cardno sensitive capability
  • assign_cardno sensitive capability
  • attach_evidenceno sensitive capability
  • attest_spec_understoodno sensitive capability
  • block_cardno sensitive capability
  • cancel_agent_runno sensitive capability
  • cancel_loopno sensitive capability
  • card_schemano sensitive capability
  • check_spec_driftno sensitive capability
  • clear_card_memoryno sensitive capability
  • cockpit_helpno sensitive capability
  • complete_taskno sensitive capability
  • create_cardno sensitive capability
  • create_taskno sensitive capability
  • curate_room_contextno sensitive capability
  • delete_commentno sensitive capability
  • delete_taskno sensitive capability
  • draft_spec_from_cardno sensitive capability
  • drop_blackboard_noteno sensitive capability
  • execute_taskno sensitive capability
  • find_cardno sensitive capability
  • find_memberno sensitive capability
  • generate_spec_proposalno sensitive capability
  • get_activity_logno sensitive capability
  • get_agent_identityno sensitive capability
  • get_all_card_fieldsno sensitive capability
  • get_board_cellsno sensitive capability
  • get_cardno sensitive capability
  • get_card_cockpit_contextno sensitive capability
  • get_card_fieldno sensitive capability
  • get_card_memoryno sensitive capability
  • get_card_specno sensitive capability
  • get_decision_inboxno sensitive capability
  • get_effective_governanceno sensitive capability
  • get_github_reposno sensitive capability
  • get_handoff_briefno sensitive capability
  • get_loop_stateno sensitive capability
  • get_mcp_capabilitiesno sensitive capability
  • get_room_contextno sensitive capability
  • get_spec_complexityno sensitive capability
  • get_spec_historyno sensitive capability
  • get_velocity_forecastno sensitive capability
  • get_verification_statusno sensitive capability
  • get_workspace_activityno sensitive capability
  • invoke_cockpit_commandno sensitive capability
  • link_github_commitno sensitive capability
  • link_github_issueno sensitive capability
  • link_github_prno sensitive capability
  • list_active_loopsno sensitive capability
  • list_agent_accountsno sensitive capability
  • list_agent_runsno sensitive capability
  • list_blockersno sensitive capability
  • list_boardsno sensitive capability
  • list_card_github_linksno sensitive capability
  • list_card_spec_documentsno sensitive capability
  • list_cardsno sensitive capability
  • list_commentsno sensitive capability
  • list_custom_fieldsno sensitive capability
  • list_epicsno sensitive capability
  • list_iterationsno sensitive capability
  • list_labelsno sensitive capability
  • list_membersno sensitive capability
  • list_memory_disputesno sensitive capability
  • list_milestonesno sensitive capability
  • list_notificationsno sensitive capability
  • list_skillsno sensitive capability
  • list_spec_proposalsno sensitive capability
  • list_tasksno sensitive capability
  • list_time_entriesno sensitive capability
  • list_webhooksno sensitive capability
  • load_skillno sensitive capability
  • log_activityno sensitive capability
  • log_loop_stepno sensitive capability
  • log_timeno sensitive capability
  • mark_all_notifications_readno sensitive capability
  • mark_notificationno sensitive capability
  • move_cardno sensitive capability
  • move_card_to_iterationno sensitive capability
  • patch_card_specno sensitive capability
  • pause_loopno sensitive capability
  • post_blackboard_noteno sensitive capability
  • preview_spec_decisionno sensitive capability
  • promote_blackboard_noteno sensitive capability
  • read_blackboardno sensitive capability
  • read_spec_proposalno sensitive capability
  • reject_spec_proposalno sensitive capability
  • remove_card_labelno sensitive capability
  • reopen_taskno sensitive capability
  • report_agent_progressno sensitive capability
  • request_agent_replanno sensitive capability
  • request_spec_proposal_changesno sensitive capability
  • research_cardno sensitive capability
  • resolve_memory_disputeno sensitive capability
  • restore_spec_versionno sensitive capability
  • resume_loopno sensitive capability
  • revise_spec_proposalno sensitive capability
  • route_to_agentno sensitive capability
  • run_card_testsno sensitive capability
  • run_distillerno sensitive capability
  • run_verifierno sensitive capability
  • search_by_field_valueno sensitive capability
  • search_cardsno sensitive capability
  • send_cockpit_chatno sensitive capability
  • set_card_fieldno sensitive capability
  • set_card_fieldsno sensitive capability
  • set_card_specno sensitive capability
  • set_card_spec_documentno sensitive capability
  • start_agent_runno sensitive capability
  • start_loopno sensitive capability
  • start_verification_loopno sensitive capability
  • tasks_from_specno sensitive capability
  • unblock_cardno sensitive capability
  • update_cardno sensitive capability
  • update_taskno sensitive capability
  • verify_behavior_contractno sensitive capability
  • verify_cardno sensitive capability
  • wait_for_notificationsno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.4.5 latest A 93/100 1 1.9.0 2026-07-23

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/scrumdo-mcp/badge.svg)](https://mcptrustchecker.com/registry/scrumdo-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/scrumdo-mcp"><img src="https://mcptrustchecker.com/registry/scrumdo-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/scrumdo-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan scrumdo-mcp --online --registry pypi

Use the free API → How scoring works

More in Productivity & Workflow