Is Teamwork MCP safe to use?

Teamwork MCP has an HVTrust score of 55.0/100 (Grade C), ranked #751 of 1328 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 55.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 25 GitHub stars and is categorized under MCP Servers.

Teamwork MCP

Teamwork/mcp

Teamwork.com MCP server

MCP Servers Go Grade C Listed MIT

55.0/100

Rank #751 of 1328

Compare Teamwork MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-09-08 · 0d ago

Recent change

Grade Changed +11

Is Teamwork MCP safe? Teamwork MCP scores 55.0/100 (Grade C), ranked #751 of 1328 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.4/10; 20% of recent commits are signed; last pushed 2026-09-08. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#406 Local FAISS MCP Server — 55.2 (C) → #407 Lighthouse MCP — 55.2 (C) → #409 Genieacs MCP — 55.0 (C) → #410 Wavyrai reMarkable MCP Server — 54.9 (C) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-08

Grade Changed

Trust grade D → C

2026-09-08

Rank Moved

Rank rose 431 spots (#1182 → #751)

2026-09-08

HVTrust Changed

HVTrust up 18.3pts (36.7 → 55.0)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.4/10. Tighten the weakest checks to improve public safety evidence.

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

64.1

Activity sub-score · out of 100

#408

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 C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-08

Activity & Reach

Stars

Forks

Last Push

2026-09-08

today

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲431

was #1182

Analysis

HVTrust Dimensions vs MCP Servers

55.0 / 100 · 100.0% confidence

Teamwork MCP MCP Servers average (778 agents)

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

7.8 / 25

2.1 below avg 9.9

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

13.1 / 17

1.1 above avg 12.0

Maintenance60% last-push freshness · 40% commit activity

19.9 / 20

7.7 above avg 12.2

AdoptionLog-scaled stars · package downloads

3.4 / 20

3.5 below avg 6.9

Activity Inputs

64.1 / 100

StarsRepository reach

8.5 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

24.8 / 25

CommunityFork signal

5.8 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.4 / 10

OpenSSF Scorecard · scanned Sep 5, 2026

Signed Commits

20%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 4

CI-Tests 7

CII-Best-Practices 0

Code-Review 2

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 7

Is Teamwork MCP safe?

Teamwork MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

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?

Teamwork MCP has an OpenSSF Scorecard score of 5.4/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

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?

20% 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-09-08

Grade Changed

Trust grade D → C

2026-09-08

Rank Moved

Rank rose 431 spots (#1182 → #751)

2026-09-08

HVTrust Changed

HVTrust up 18.3pts (36.7 → 55.0)

2026-09-07

Grade Changed

Trust grade C → D

2026-09-07

Rank Moved

Rank dropped 478 spots (#704 → #1182)

2026-09-07

HVTrust Changed

HVTrust down 18.2pts (54.9 → 36.7)

2026-09-06

Rank Moved

Rank dropped 12 spots (#692 → #704)

2026-09-05

Rank Moved

Rank dropped 78 spots (#614 → #692)

2026-09-04

Rank Moved

Rank dropped 16 spots (#598 → #614)

2026-09-03

Rank Moved

Rank dropped 25 spots (#573 → #598)

2026-09-02

Rank Moved

Rank dropped 16 spots (#557 → #573)

2026-09-01

Rank Moved

Rank dropped 12 spots (#545 → #557)

2026-08-31

Rank Moved

Rank dropped 35 spots (#510 → #545)

2026-08-29

Scorecard Added

OSSF Scorecard: 5.4/10

2026-08-29

Grade Changed

Trust grade D → C

2026-08-29

Rank Moved

Rank rose 604 spots (#1117 → #513)

2026-08-29

HVTrust Changed

HVTrust up 33.0pts (21.7 → 54.7)

2026-08-28

Rank Moved

Rank dropped 24 spots (#1093 → #1117)

2026-08-27

Rank Moved

Rank dropped 16 spots (#1077 → #1093)

2026-08-26

Rank Moved

Rank dropped 62 spots (#1015 → #1077)

2026-08-24

Rank Moved

Rank dropped 15 spots (#996 → #1011)

2026-08-17

Rank Moved

Rank rose 21 spots (#1026 → #1005)

2026-08-16

Rank Moved

Rank dropped 33 spots (#993 → #1026)

2026-08-13

Rank Moved

Rank dropped 12 spots (#985 → #997)

2026-08-12

Rank Moved

Rank rose 19 spots (#1004 → #985)

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) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON