Is Taskade MCP safe to use?

Taskade MCP has an HVTrust score of 71.9/100 (Grade B), ranked #320 of 1378 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Taskade MCP?

Taskade MCP scores 71.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 169 GitHub stars and is categorized under MCP Servers.

Taskade MCP

Repository

Website

🤖 Taskade MCP · Official MCP server and OpenAPI to MCP codegen. Build AI agent tools from any OpenAPI API and connect to Claude, Cursor, and more.

MCP Servers TypeScript Listed MIT

Is Taskade MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.1 / 10

Provenance Attested

Signed commits 62%

Last push today

Advisories None known

Compare Taskade MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Taskade MCP scores 71.9/100 (Grade B), ranked #320 of 1378 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.1/10; 62% of recent commits are signed; no published advisory affects its latest release (@taskade/mcp-server); last pushed 2026-10-17. Every point is earned from checkable signals — never paid placement. How scoring works →

How Taskade 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 4.1 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +10.3 → 82.2 A · #49 of 781
Sign every commit62% signed today +1.9 → 73.8 B · #160 of 781

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Taskade MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Partly signed

github.com/taskade/mcp, MIT, last pushed 2026-10-17. 62% 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 4.1/10 (scanned Oct 15, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 9

CII-Best-Practices 0

Code-Review 0

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 0

SAST 3

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0
Published packages Linked and attested
- npm @taskade/mcp-server Source link points back to this repo Build provenance attested
What you install today No known advisories

Latest release checked: @taskade/mcp-server 0.1.2. No published advisory affects it (OSV, checked 2026-10-17).

Changes to this chain

2026-09-23 Package provenance attestation detected
2026-09-11 Package provenance attestation detected
2026-08-28 OSSF Scorecard: 3.9/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 Taskade 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.

Signed credential (JSON) How to verify

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 Taskade MCP compares in MCP Servers

Bars show each HVTrust score; the tick marks Taskade MCP’s 71.9.

Where the 71.9 comes from

HVTrust dimensions vs the MCP Servers average

71.9 / 100 · 100.0% confidence

Taskade MCP MCP Servers average (781 agents)

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

15.7 / 25

5.2 above avg 10.5

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.5 above avg 13.5

Transparency50% declared license · 50% OSSF Scorecard

12.0 / 17

in line with avg 12.3

Maintenance60% last-push freshness · 40% commit activity

13.4 / 20

1.1 above avg 12.3

AdoptionLog-scaled stars · package downloads

8.1 / 20

0.7 above avg 7.4

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

2026-10-17

Rank Moved

Rank rose 17 spots (#337 → #320)

2026-10-11

Rank Moved

Rank dropped 22 spots (#297 → #319)

2026-10-10

Rank Moved

Rank dropped 40 spots (#257 → #297)

Maintainer Checklist

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

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

55.2

Activity sub-score · out of 100

#189

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 B 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

2026-09-29 2026-10-17

Activity & Reach

Stars

169

Forks

Last Push

2026-10-17

today

Commits (4 wk)

Downloads (7d)

117

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲17

was #337

Analysis

Activity Inputs

55.2 / 100

StarsRepository reach

13.4 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

8.7 / 25

CommunityFork signal

8.1 / 20

Common questions about Taskade MCP

Taskade 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 Taskade MCP publish package provenance?

Yes. Taskade MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Taskade MCP have an OpenSSF Scorecard?

Taskade MCP has an OpenSSF Scorecard score of 4.1/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 Taskade MCP actively maintained?

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

What license does Taskade MCP use?

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

Are Taskade MCP's commits signed?

62% of the last 100 commits to Taskade 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

Taskade MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

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

How this surface has changed

Detected changes to Taskade 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.

2026-09-24

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-11

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-11

Provenance Added

Package provenance attestation detected

Maintain Taskade MCP?

For maintainers

HVTrust scores Taskade 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-10-17

Rank Moved

Rank rose 17 spots (#337 → #320)

2026-10-11

Rank Moved

Rank dropped 22 spots (#297 → #319)

2026-10-10

Rank Moved

Rank dropped 40 spots (#257 → #297)

2026-10-09

Rank Moved

Rank rose 27 spots (#284 → #257)

2026-09-24

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-24

Rank Moved

Rank dropped 40 spots (#261 → #301)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 656 spots (#917 → #261)

2026-09-23

HVTrust Changed

HVTrust up 46.5pts (26.5 → 73.0)

2026-09-22

Newly Listed

First tracked at rank #917

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank rose 10 spots (#298 → #288)

2026-09-17

Rank Moved

Rank rose 10 spots (#308 → #298)

2026-09-11

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-11

Provenance Added

Package provenance attestation detected

2026-09-11

Grade Changed

Trust grade C → B

2026-09-11

Rank Moved

Rank rose 457 spots (#752 → #295)

2026-09-11

HVTrust Changed

HVTrust up 16.1pts (55.3 → 71.4)

2026-09-11

Activity Score Changed

Activity score up 10pts (46 → 56)

2026-09-10

Rank Moved

Rank rose 30 spots (#782 → #752)

2026-09-09

Rank Moved

Rank dropped 14 spots (#768 → #782)

2026-09-07

Rank Moved

Rank dropped 55 spots (#708 → #763)

2026-09-05

Rank Moved

Rank dropped 76 spots (#623 → #699)

2026-09-04

Rank Moved

Rank dropped 22 spots (#601 → #623)

2026-09-03

Grade Changed

Trust grade D → C

2026-09-03

Rank Moved

Rank rose 451 spots (#1052 → #601)

2026-09-03

HVTrust Changed

HVTrust up 18.5pts (36.5 → 55.0)

2026-09-02

Rank Moved

Rank dropped 45 spots (#1007 → #1052)

2026-09-01

Rank Moved

Rank dropped 42 spots (#965 → #1007)

2026-08-31

Rank Moved

Rank dropped 34 spots (#931 → #965)

2026-08-30

Rank Moved

Rank dropped 45 spots (#886 → #931)

2026-08-29

Rank Moved

Rank dropped 48 spots (#838 → #886)

2026-08-28

Scorecard Added

OSSF Scorecard: 3.9/10

2026-08-28

Rank Moved

Rank rose 283 spots (#1121 → #838)

2026-08-28

HVTrust Changed

HVTrust up 15.9pts (20.8 → 36.7)

2026-08-27

Rank Moved

Rank dropped 66 spots (#1055 → #1121)

2026-08-27

Activity Score Changed

Activity score down 12pts (57 → 46)

2026-08-26

Rank Moved

Rank dropped 82 spots (#973 → #1055)

2026-08-25

Rank Moved

Rank rose 33 spots (#1006 → #973)

2026-08-16

Rank Moved

Rank dropped 31 spots (#977 → #1008)

2026-08-12

Rank Moved

Rank rose 11 spots (#980 → #969)

2026-08-10

Rank Moved

Rank dropped 63 spots (#911 → #974)

2026-08-08

Newly Listed

First tracked at rank #901

GitHub → Website → npm: @taskade/mcp-server

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/taskade-mcp.svg)](https://hvtracker.net/agents/taskade-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/taskade-mcp"><img src="https://hvtracker.net/badge/taskade-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON

Taskade MCP

How Taskade MCP could raise its score

Chain of custody

Source Partly signed

Review and release Mixed

Published packages Linked and attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Taskade MCP compares in MCP Servers

Where the 71.9 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Taskade MCP

AI agent surface

Maintain Taskade MCP?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers