Is Teamwork MCP safe to use?

Teamwork MCP has an HVTrust score of 21.3/100 (Grade D), ranked #1002 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Teamwork MCP?

Teamwork MCP scores 21.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 24 GitHub stars and is categorized under MCP Servers.

Teamwork MCP

Teamwork/mcp

Teamwork.com MCP server

MCP Servers Go Grade D Listed MIT

21.3/100

Rank #1002 of 1283

Compare Teamwork MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade D · 1/5 signals

Last push

2026-08-11 · 1d ago

Recent change

Rank +1

Is Teamwork MCP safe? Teamwork MCP scores 21.3/100 (Grade D), ranked #1002 of 1283 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 14% of recent commits are signed; last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#525 Mobile Device MCP — 21.4 (D) → #526 Glidermcp Com — 21.3 (D) → #528 Obsidian Vault MCP — 21.3 (D) → #529 MCP Victoriametrics — 21.2 (D) →

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-08-10

Rank Moved

Rank dropped 49 spots (#953 → #1002)

2026-08-08

Newly Listed

First tracked at rank #943

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for Teamwork MCP View MCP Servers Report missing data

62.0

Activity sub-score · out of 100

#527

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars

Forks

Last Push

2026-08-11

yesterday

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲2

was #1004

Analysis

HVTrust Dimensions vs MCP Servers

21.3 / 100 · 50.0% confidence

Teamwork MCP MCP Servers average (761 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

0.7 / 25

4.3 below avg 5.0

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.5 below avg 13.3

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

in line with avg 8.8

Maintenance60% last-push freshness · 40% commit activity

19.3 / 20

6.9 above avg 12.4

AdoptionLog-scaled stars · package downloads

3.4 / 20

2.4 below avg 5.8

Activity Inputs

62.0 / 100

StarsRepository reach

8.4 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

22.9 / 25

CommunityFork signal

5.7 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

14%

of last 100 commits verified

Is Teamwork MCP safe?

Public trust evidence for Teamwork MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does Teamwork MCP publish package provenance?

No published build provenance is currently detected for Teamwork MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Teamwork MCP have an OpenSSF Scorecard?

No OpenSSF Scorecard data is currently published for Teamwork MCP. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.

Is Teamwork MCP actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Teamwork MCP use?

Teamwork MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Teamwork MCP's commits signed?

14% of the last 100 commits to Teamwork MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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

Scored in HVTrust

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 Server Support

high confidence

Implemented

Teamwork MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

3 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-10

Rank Moved

Rank dropped 49 spots (#953 → #1002)

2026-08-08

Newly Listed

First tracked at rank #943

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/teamwork-mcp.svg)](https://hvtracker.net/agents/teamwork-mcp)
            
HTML:
            <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

Data sources
GitHub REST API (repo, commits, stars, forks, license)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON