Coordmcp MCP Server

coordmcp PyPI v0.1.2

Published by siddiquesahabaj — 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.

A FastMCP-based Model Context Protocol server for intelligent multi-agent code coordination

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/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
Moderate
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 = 96/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 − 4 = 96. 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
−3 capability blast radius (moderate) — 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

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([get_design_patterns]) co-exist with external-action tools ([send_message]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [get_design_patterns] → sinks [send_message]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow get_design_patterns → send_message

Tools 52

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

  • get_design_patternsingests untrusted input
  • send_messagenetwork egress
  • analyze_architectureno sensitive capability
  • assign_taskno sensitive capability
  • broadcast_messageno sensitive capability
  • complete_taskno sensitive capability
  • create_projectno sensitive capability
  • create_taskno sensitive capability
  • delete_taskno sensitive capability
  • discover_projectno sensitive capability
Show 42 more tools ↓
  • end_contextno sensitive capability
  • get_active_agentsno sensitive capability
  • get_agent_contextno sensitive capability
  • get_agent_profileno sensitive capability
  • get_agents_in_projectno sensitive capability
  • get_agents_listno sensitive capability
  • get_architecture_recommendationno sensitive capability
  • get_context_historyno sensitive capability
  • get_file_dependenciesno sensitive capability
  • get_locked_filesno sensitive capability
  • get_messagesno sensitive capability
  • get_module_infono sensitive capability
  • get_my_tasksno sensitive capability
  • get_projectno sensitive capability
  • get_project_dashboardno sensitive capability
  • get_project_decisionsno sensitive capability
  • get_project_infono sensitive capability
  • get_project_onboarding_context_toolno sensitive capability
  • get_project_tasksno sensitive capability
  • get_recent_changesno sensitive capability
  • get_sent_messagesno sensitive capability
  • get_session_logno sensitive capability
  • get_system_prompt_toolno sensitive capability
  • get_taskno sensitive capability
  • get_tech_stackno sensitive capability
  • get_workflow_guidance_toolno sensitive capability
  • list_projectsno sensitive capability
  • lock_filesno sensitive capability
  • log_changeno sensitive capability
  • mark_message_readno sensitive capability
  • register_agentno sensitive capability
  • save_decisionno sensitive capability
  • search_decisionsno sensitive capability
  • start_contextno sensitive capability
  • switch_contextno sensitive capability
  • unlock_filesno sensitive capability
  • update_architectureno sensitive capability
  • update_file_metadatano sensitive capability
  • update_task_statusno sensitive capability
  • update_tech_stackno sensitive capability
  • validate_code_structureno sensitive capability
  • validate_workflow_state_toolno 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.1.2 latest A 96/100 1 1.13.0 2026-08-25

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 · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/coordmcp/badge.svg)](https://mcptrustchecker.com/registry/coordmcp)
HTML
<a href="https://mcptrustchecker.com/registry/coordmcp"><img src="https://mcptrustchecker.com/registry/coordmcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/coordmcp/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 coordmcp --online --registry pypi

Use the free API → How scoring works

More in AI, Memory & Reasoning