Ai Team Os MCP Server

ai-team-os PyPI v1.3.4

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

Self-driving AI company OS — turn Claude Code into a persistent, self-managing dev team

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 18

high Reads a sensitive credential path or dumps the environment (hooks/workflow_reminder.py)MTC-SRC-006

In the server's implementation (`hooks/workflow_reminder.py:479`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ck_patterns = [".env", "id_rsa", ".pem", ".key"] for pat in block_patterns: if pat in cmd_

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server hooks/workflow_reminder.py

high Reads a sensitive credential path or dumps the environment (plugin/hooks/workflow_reminder.py)MTC-SRC-006

In the server's implementation (`plugin/hooks/workflow_reminder.py:872`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ck_patterns = [".env", "id_rsa", ".pem", ".key"] for pat in block_patterns: if pat in cmd_

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server plugin/hooks/workflow_reminder.py

high Reads a sensitive credential path or dumps the environment (src/aiteam/hooks/workflow_reminder.py)MTC-SRC-006

In the server's implementation (`src/aiteam/hooks/workflow_reminder.py:872`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ck_patterns = [".env", "id_rsa", ".pem", ".key"] for pat in block_patterns: if pat in cmd_

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/aiteam/hooks/workflow_reminder.py

high Shell/command execution in server code (hooks/session_bootstrap.py)MTC-SRC-002

In the server's implementation (`hooks/session_bootstrap.py:117`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: fetch_result = subprocess.run( ["git", "fetch", "--quiet", "origin"], cwd=str

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server hooks/session_bootstrap.py

high Shell/command execution in server code (install.py)MTC-SRC-002

In the server's implementation (`install.py:18`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: return subprocess.run( args, cwd=cwd, check=True, shell=(sys.platform == "win

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server install.py

high Shell/command execution in server code (plugin/bootstrap.py)MTC-SRC-002

In the server's implementation (`plugin/bootstrap.py:88`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ile=sys.stderr) subprocess.run( [sys.executable, "-m", "venv", str(venv_dir)], capture_o

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server plugin/bootstrap.py

high Shell/command execution in server code (plugin/hooks/session_bootstrap.py)MTC-SRC-002

In the server's implementation (`plugin/hooks/session_bootstrap.py:114`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ain or master).""" subprocess.run( ["git", "fetch", "--quiet", "origin"], cwd=str(project_root),

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server plugin/hooks/session_bootstrap.py

high Shell/command execution in server code (src/aiteam/hooks/session_bootstrap.py)MTC-SRC-002

In the server's implementation (`src/aiteam/hooks/session_bootstrap.py:114`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ain or master).""" subprocess.run( ["git", "fetch", "--quiet", "origin"], cwd=str(project_root),

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/aiteam/hooks/session_bootstrap.py

high Shell/command execution in server code (src/aiteam/mcp/_autostart.py)MTC-SRC-002

In the server's implementation (`src/aiteam/mcp/_autostart.py:171`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: out = subprocess.check_output( ["netstat", "-ano", "-p", "TCP"], text=

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/aiteam/mcp/_autostart.py

high Shell/command execution in server code (src/aiteam/mcp/tools/git_ops.py)MTC-SRC-002

In the server's implementation (`src/aiteam/mcp/tools/git_ops.py:19`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: tderr).""" result = subprocess.run( ["git"] + args, capture_output=True, text=True,

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/aiteam/mcp/tools/git_ops.py

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

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

Evidence: untrusted [cross_project_inbox, meeting_read_messages] → sinks [send_notification, meeting_send_message]

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

Location: flow cross_project_inbox → send_notification

medium Dynamic module load from a non-literal (plugin/dashboard-dist/assets/index-CICd_ipg.js)MTC-SRC-005

In the server's implementation (`plugin/dashboard-dist/assets/index-CICd_ipg.js:11`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: t[e.id];try{let r=await import(e.module);return t[e.id]=r,r}catch(r){return console.error(`Error loading route module \`

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server plugin/dashboard-dist/assets/index-CICd_ipg.js

low Reads a sensitive credential path or dumps the environment in packaging/dev tooling (tests/test_workflow_reminder.py)MTC-SRC-006

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_workflow_reminder.py:999`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: lf): """git add id_rsa (SSH key) must call sys.exit(2).""" state: dict = {} event = {"tool_name"

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_workflow_reminder.py

low Dynamic code execution in packaging/dev tooling (tests/integration/test_cross_feature.py)MTC-SRC-001

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/integration/test_cross_feature.py:316`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ): """POST with eval() injection → 400.""" client = integration_client resp = client.post(

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/integration/test_cross_feature.py

low Dynamic code execution in packaging/dev tooling (tests/test_api_comprehensive.py)MTC-SRC-001

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_api_comprehensive.py:68`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: 在性检查 if not eval(assertion, {"body": body}): # noqa: S307 assertion_failures.append(asserti

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_api_comprehensive.py

low Shell/command execution in packaging/dev tooling (scripts/install.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/install.py:327`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: package") result = subprocess.run( [sys.executable, "-m", "pip", "install", "-e", "."], cwd=str(p

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server scripts/install.py

low Shell/command execution in packaging/dev tooling (scripts/uninstall.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/uninstall.py:50`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: y: result = subprocess.run( ["powershell", "-NoProfile", "-Command", "(Get-

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server scripts/uninstall.py

low Shell/command execution in packaging/dev tooling (scripts/update.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/update.py:22`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: return subprocess.run( args, cwd=cwd, check=True, shell

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server scripts/update.py

Tools 109

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

  • cross_project_inboxingests untrusted input
  • meeting_read_messagesingests untrusted input
  • meeting_send_messagenetwork egress
  • send_notificationnetwork egress
  • agent_activity_queryno sensitive capability
  • agent_heartbeatno sensitive capability
  • agent_listno sensitive capability
  • agent_registerno sensitive capability
  • agent_template_listno sensitive capability
  • agent_template_recommendno sensitive capability
Show 99 more tools ↓
  • agent_trust_scoresno sensitive capability
  • agent_trust_updateno sensitive capability
  • agent_update_statusno sensitive capability
  • briefing_addno sensitive capability
  • briefing_dismissno sensitive capability
  • briefing_listno sensitive capability
  • briefing_resolveno sensitive capability
  • budget_statusno sensitive capability
  • cache_clearno sensitive capability
  • cache_statsno sensitive capability
  • channel_mentionsno sensitive capability
  • channel_readno sensitive capability
  • channel_sendno sensitive capability
  • context_resolveno sensitive capability
  • cross_project_sendno sensitive capability
  • debate_code_reviewno sensitive capability
  • debate_startno sensitive capability
  • decision_logno sensitive capability
  • diagnose_task_failureno sensitive capability
  • dismiss_project_registrationno sensitive capability
  • ecosystem_recipesno sensitive capability
  • error_budget_statusno sensitive capability
  • error_budget_updateno sensitive capability
  • event_listno sensitive capability
  • failure_analysisno sensitive capability
  • file_lock_acquireno sensitive capability
  • file_lock_checkno sensitive capability
  • file_lock_listno sensitive capability
  • file_lock_releaseno sensitive capability
  • find_skillno sensitive capability
  • git_auto_commitno sensitive capability
  • git_create_prno sensitive capability
  • git_status_checkno sensitive capability
  • guardrail_checkno sensitive capability
  • guardrail_check_payloadno sensitive capability
  • loop_advanceno sensitive capability
  • loop_next_taskno sensitive capability
  • loop_pauseno sensitive capability
  • loop_resumeno sensitive capability
  • loop_reviewno sensitive capability
  • loop_startno sensitive capability
  • loop_statusno sensitive capability
  • meeting_attendance_checkno sensitive capability
  • meeting_concludeno sensitive capability
  • meeting_createno sensitive capability
  • meeting_listno sensitive capability
  • meeting_template_listno sensitive capability
  • meeting_updateno sensitive capability
  • memory_searchno sensitive capability
  • os_health_checkno sensitive capability
  • os_report_issueno sensitive capability
  • os_resolve_issueno sensitive capability
  • pattern_recordno sensitive capability
  • pattern_searchno sensitive capability
  • phase_createno sensitive capability
  • phase_listno sensitive capability
  • pipeline_advanceno sensitive capability
  • pipeline_createno sensitive capability
  • pipeline_statusno sensitive capability
  • project_createno sensitive capability
  • project_deleteno sensitive capability
  • project_listno sensitive capability
  • project_summaryno sensitive capability
  • project_updateno sensitive capability
  • prompt_effectivenessno sensitive capability
  • prompt_version_listno sensitive capability
  • report_listno sensitive capability
  • report_readno sensitive capability
  • report_saveno sensitive capability
  • scheduler_createno sensitive capability
  • scheduler_deleteno sensitive capability
  • scheduler_listno sensitive capability
  • scheduler_pauseno sensitive capability
  • task_auto_matchno sensitive capability
  • task_compareno sensitive capability
  • task_createno sensitive capability
  • task_decomposeno sensitive capability
  • task_execution_traceno sensitive capability
  • task_list_projectno sensitive capability
  • task_memo_addno sensitive capability
  • task_memo_readno sensitive capability
  • task_replayno sensitive capability
  • task_runno sensitive capability
  • task_statusno sensitive capability
  • task_subtasksno sensitive capability
  • task_updateno sensitive capability
  • taskwall_viewno sensitive capability
  • team_briefingno sensitive capability
  • team_closeno sensitive capability
  • team_createno sensitive capability
  • team_deleteno sensitive capability
  • team_knowledgeno sensitive capability
  • team_listno sensitive capability
  • team_setup_guideno sensitive capability
  • team_statusno sensitive capability
  • token_costsno sensitive capability
  • verify_completionno sensitive capability
  • watchdog_checkno sensitive capability
  • what_if_analysisno 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
v1.3.4 latest A 93/100 18 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 · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/ai-team-os/badge.svg)](https://mcptrustchecker.com/registry/ai-team-os)
HTML
<a href="https://mcptrustchecker.com/registry/ai-team-os"><img src="https://mcptrustchecker.com/registry/ai-team-os/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/ai-team-os/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 ai-team-os --online --registry pypi

Use the free API → How scoring works

More in Productivity & Workflow