Workopia MCP

Workopia MCP Server — free job search, resume builder & career advice for Claude, ChatGPT, Cursor.

MCP Servers JavaScript Listed MIT

Is Workopia MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 1.6 / 10
Provenance None
Signed commits 54%
Last push 72d ago
Compare Workopia MCP
Suggest a correction

In detail: Workopia MCP scores 37.2/100 (Grade D), ranked #1260 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 1.6/10; 54% of recent commits are signed; last pushed 2026-08-31. Every point is earned from checkable signals — never paid placement. How scoring works →

How Workopia 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.

Chain of custody

Scanners check what the code says. This traces who ships Workopia 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.

  1. Source Partly signed

    github.com/workopia/workopia-mcp, MIT, last pushed 2026-08-31. 54% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 1.6/10 (scanned Nov 5, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflown/a
    • Token Permissionsn/a
    • Pinned Dependenciesn/a
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests -1
    CII-Best-Practices 0
    Code-Review 0
    Contributors 3
    Dangerous-Workflow -1
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging -1
    Pinned-Dependencies -1
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions -1
    Vulnerabilities 0
  3. Published packages Source mismatch

    A package whose source link names another repository may belong to a different project, or the project may have moved. HVTracker treats it as a mismatch until that is confirmed. Know which? Suggest a correction

Changes to this chain

  • 2026-09-23 Package-provenance drift warning: package metadata no longer clearly points at this repo
  • 2026-08-29 OSSF Scorecard: 1.6/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 Workopia 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 Workopia MCP compares in MCP Servers

  1. #723 MCP Power Automate 38.0 +0.8
  2. #724 Patsnap Patent & Literature Search 37.3 +0.1
  3. #725 Workopia MCP 37.2 this agent
  4. #726 MCP Funnel 37.1 −0.1
  5. #727 JustCall MCP Server 36.9 −0.3

Bars show each HVTrust score; the tick marks Workopia MCP’s 37.2.

Where the 37.2 comes from

HVTrust dimensions vs the MCP Servers average

37.2 / 100 · 100.0% confidence

Workopia MCP MCP Servers average (779 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.7 / 25
6.1 below avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
9.9 / 17
2.4 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
7.2 / 20
5.1 below avg 12.3
AdoptionLog-scaled stars · package downloads
7.9 / 20
in line with avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-01
Rank Moved
Rank rose 10 spots (#1257 → #1247)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 1.6/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.
Refresh maintenance signals The repo was last pushed 72 days ago. Fresh activity helps separate stable projects from stale ones.
36.3
Activity sub-score · out of 100
#725

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

Signals refreshed 2026-11-11 00:08 UTC · Repo last pushed 72 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
312
Forks
21
Last Push
2026-08-31
72 days ago
Commits (4 wk)
0
Downloads (7d)
25
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▼1
was #1259

Analysis

Activity Inputs

36.3 / 100
StarsRepository reach
15.0 / 30
FreshnessLast push recency
15.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
6.2 / 20

Common questions about Workopia MCP

Public trust evidence for Workopia 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 Workopia MCP publish package provenance?
No published build provenance is currently detected for Workopia 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 Workopia MCP have an OpenSSF Scorecard?
Workopia MCP has an OpenSSF Scorecard score of 1.6/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 Workopia MCP actively maintained?
Slowing down. Last push was 72 days ago — keep an eye on whether activity resumes.
What license does Workopia MCP use?
Workopia MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Workopia MCP's commits signed?
53% of the last 100 commits to Workopia 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
medium confidence
Implemented
Workopia MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
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
Warning
1 package source mismatch detected
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 Workopia 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-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Drift Warning Raised
Package-provenance drift warning: package metadata no longer clearly points at this repo
2026-08-31
Activity Resumed
Activity resumed
2026-08-28
Activity Went Stale
No commits for 90 days

Maintain Workopia MCP?

For maintainers

HVTrust scores Workopia 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
Rank 17HVTrust 4Stale 1Scorecard 1Score 1Fresh 1Delisted 1Listed 1Drift 1MCP 1Surface 1Surface 1
2026-11-01
Rank Moved
Rank rose 10 spots (#1257 → #1247)
2026-10-09
Rank Moved
Rank dropped 10 spots (#1194 → #1204)
2026-09-30
Rank Moved
Rank dropped 33 spots (#1161 → #1194)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Drift Warning Raised
Package-provenance drift warning: package metadata no longer clearly points at this repo
2026-09-23
Rank Moved
Rank dropped 15 spots (#1134 → #1149)
2026-09-23
HVTrust Changed
HVTrust up 19.5pts (21.3 → 40.8)
2026-09-22
Newly Listed
First tracked at rank #1134
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-12
Rank Moved
Rank dropped 15 spots (#1109 → #1124)
2026-09-09
Rank Moved
Rank dropped 16 spots (#1086 → #1102)
2026-09-07
Rank Moved
Rank dropped 28 spots (#1051 → #1079)
2026-09-06
Rank Moved
Rank dropped 18 spots (#1033 → #1051)
2026-09-05
Rank Moved
Rank dropped 37 spots (#996 → #1033)
2026-09-04
Rank Moved
Rank dropped 26 spots (#970 → #996)
2026-09-03
Rank Moved
Rank rose 232 spots (#1202 → #970)
2026-09-03
HVTrust Changed
HVTrust up 16.2pts (26.5 → 42.7)
2026-09-02
Rank Moved
Rank dropped 36 spots (#1166 → #1202)
2026-09-01
Rank Moved
Rank dropped 45 spots (#1121 → #1166)
2026-08-31
Activity Resumed
Activity resumed
2026-08-31
Rank Moved
Rank rose 56 spots (#1177 → #1121)
2026-08-31
HVTrust Changed
HVTrust up 4.9pts (21.7 → 26.6)
2026-08-31
Activity Score Changed
Activity score up 17pts (33 → 50)
2026-08-30
Rank Moved
Rank dropped 30 spots (#1147 → #1177)
2026-08-29
Scorecard Added
OSSF Scorecard: 1.6/10
2026-08-29
Rank Moved
Rank rose 168 spots (#1315 → #1147)
2026-08-29
HVTrust Changed
HVTrust up 11.3pts (10.3 → 21.6)
2026-08-28
Activity Went Stale
No commits for 90 days
2026-08-16
Rank Moved
Rank dropped 25 spots (#1281 → #1306)

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 37.2 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/workopia-mcp.svg)](https://hvtracker.net/agents/workopia-mcp)
HTML:
<a href="https://hvtracker.net/agents/workopia-mcp"><img src="https://hvtracker.net/badge/workopia-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