Agent Team MCP Server

agent-team-mcp npm v1.5.4

Published by richardlemmon — 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 reusable AI software development team built on MCP. 13 specialized agents collaborate through SQLite, orchestrated by a Project Manager.

Trust grade
A
98/100
Last scanned get badge →
Trust
A · 98/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
Minimal
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 99 − adoption risk = 98/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 − 1.2 = 99. What the published surface and source actually contain:

PointsWhat was foundCategory
−1.2 Package runs install-time scripts MTC-SUP-010 supply-chain

2. Client adoption risk — 99 − 1 = 98. 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
−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

low Package runs install-time scripts (postinstall)MTC-SUP-010

"agent-team-mcp" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.

Evidence: node -e "const fs=require('fs'),p=require('path'),d=p.join(require('os').homedir(),'.claude','skills','agent-team');try{fs.mkdirSync(d,{recursive:true});fs.copy

Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.

Location: package agent-team-mcp

Tools 46

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

  • add_discussion_messageno sensitive capability
  • add_discussion_participantno sensitive capability
  • add_task_commentno sensitive capability
  • add_team_memberno sensitive capability
  • answer_user_questionno sensitive capability
  • ask_user_questionno sensitive capability
  • create_discussionno sensitive capability
  • create_projectno sensitive capability
  • create_taskno sensitive capability
  • delete_projectno sensitive capability
Show 36 more tools ↓
  • get_agent_promptno sensitive capability
  • get_artifactno sensitive capability
  • get_decisionno sensitive capability
  • get_discussionno sensitive capability
  • get_my_workno sensitive capability
  • get_orchestration_instructionsno sensitive capability
  • get_projectno sensitive capability
  • get_project_summaryno sensitive capability
  • get_summary_versionno sensitive capability
  • get_taskno sensitive capability
  • get_team_protocolno sensitive capability
  • get_work_historyno sensitive capability
  • list_artifactsno sensitive capability
  • list_decisionsno sensitive capability
  • list_discussionsno sensitive capability
  • list_expansion_requestsno sensitive capability
  • list_journal_entriesno sensitive capability
  • list_my_commentsno sensitive capability
  • list_projectsno sensitive capability
  • list_summary_historyno sensitive capability
  • list_task_commentsno sensitive capability
  • list_tasksno sensitive capability
  • list_team_membersno sensitive capability
  • list_user_questionsno sensitive capability
  • log_decisionno sensitive capability
  • log_journal_entryno sensitive capability
  • log_workno sensitive capability
  • remove_team_memberno sensitive capability
  • request_team_expansionno sensitive capability
  • resolve_expansion_requestno sensitive capability
  • share_artifactno sensitive capability
  • update_artifactno sensitive capability
  • update_discussion_summaryno sensitive capability
  • update_project_statusno sensitive capability
  • update_project_summaryno sensitive capability
  • update_taskno sensitive capability

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.5.4 latest A 98/100 1 1.13.0 2026-09-07

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

Use the free API → How scoring works

More in Databases