Teamwork MCP
Website
Teamwork.com MCP server
Is Teamwork MCP safe? Promising trust profile, but some evidence still deserves review.
Compare Teamwork MCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Teamwork MCP scores 59.3/100 (Grade C), ranked #715 of 1387 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.8/10; 4% of recent commits are signed; last pushed 2026-11-06. Every point is earned from checkable signals — never paid placement. How scoring works →
How Teamwork MCP could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Raise the OSSF Scorecard from 5.8 to 9.0lowest checks: CII-Best-Practices 0, Fuzzing 0, Pinned-Dependencies 0 +6.8 → 66.1 B · #285 of 779
- Sign every commit4% signed today +4.8 → 64.1 C · #322 of 779
Chain of custody
Scanners check what the code says. This traces who ships Teamwork MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Partly signed
github.com/Teamwork/mcp, MIT, last pushed 2026-11-06. 4% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 5.8/10 (scanned Nov 4, 2026). The checks that decide who can get a change released:
- Code Review5
- Branch Protection5
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 5CI-Tests 7CII-Best-Practices 0Code-Review 5Contributors 6Dangerous-Workflow 10Dependency-Update-Tool 10Fuzzing 0License 10Maintained 10Packaging -1Pinned-Dependencies 0SAST 0Security-Policy 10Signed-Releases 0Token-Permissions 0Vulnerabilities 9 -
Published packages None
Distributed as the container image docker.io/teamwork/mcp:v1.26.5; HVTracker doesn't check that registry's source link yet.
Changes to this chain
- 2026-08-29 OSSF Scorecard: 5.4/10
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues Teamwork MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How Teamwork MCP compares in MCP Servers
- #386 MCP Server for OSCAL 59.7 +0.4
- #387 MCP Sqlite Tools 59.4 +0.1
- #388 Teamwork MCP 59.3 this agent
- #389 Drawio MCP 59.3 ±0
- #390 MCP Imagenate 59.2 −0.1
Bars show each HVTrust score; the tick marks Teamwork MCP’s 59.3.
Where the 59.3 comes from
HVTrust dimensions vs the MCP Servers average
59.3 / 100 · 100.0% confidenceTeamwork MCP MCP Servers average (779 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
59.4 / 100Common questions about Teamwork MCP
Does Teamwork MCP publish package provenance?
Does Teamwork MCP have an OpenSSF Scorecard?
Is Teamwork MCP actively maintained?
What license does Teamwork MCP use?
Are Teamwork MCP's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Teamwork MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Teamwork MCP?
For maintainers
HVTrust scores Teamwork MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/teamwork-mcp)
<a href="https://hvtracker.net/agents/teamwork-mcp"><img src="https://hvtracker.net/badge/teamwork-mcp.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON