updated 2026-10-16 16:07 UTC

Opendocswork MCP

Repository

Rust-native MCP server for Office document processing (Excel, Word, PowerPoint). Sub-millisecond, local-first, open source.

MCP Servers Rust Listed GPL-3.0

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

OSSF Scorecard 2.3 / 10
Provenance None
Signed commits 0%
Last push 16d ago
Advisories None known
Compare Opendocswork MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Opendocswork MCP scores 48.9/100 (Grade D), ranked #1038 of 1378 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 2.3/10; recent commits are unsigned; no published advisory affects its latest release (@aimino/opendocswork-mcp); last pushed 2026-09-30. Every point is earned from checkable signals — never paid placement. How scoring works →

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

Already done? Suggest a correctionAdd the trust badge

Chain of custody

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

    github.com/Aimino-Tech/opendocswork-mcp, GPL-3.0, last pushed 2026-09-30. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 2.3/10 (scanned Oct 11, 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 Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests -1
    CII-Best-Practices 0
    Code-Review 0
    Contributors 6
    Dangerous-Workflow -1
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions -1
    Vulnerabilities 0

  3. Published packages Linked, not attested

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: @aimino/opendocswork-mcp 0.2.1. No published advisory affects it (OSV, checked 2026-10-16).

Changes to this chain

  • 2026-08-29 OSSF Scorecard: 2.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 Opendocswork 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 Opendocswork MCP compares in MCP Servers

  1. #589 x64dbg MCP Server 49.0 +0.1
  2. #590 MCP Document Converter 49.0 +0.1
  3. #591 Opendocswork MCP 48.9 this agent
  4. #592 Notebooklm MCP Secure 48.8 −0.1
  5. #593 Wechat Devtools MCP 48.8 −0.1

Bars show each HVTrust score; the tick marks Opendocswork MCP’s 48.9.

Where the 48.9 comes from

HVTrust dimensions vs the MCP Servers average

48.9 / 100 · 100.0% confidence

Opendocswork MCP MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
2.9 / 25
7.6 below avg 10.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
10.5 / 17
1.8 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
10.9 / 20
1.4 below avg 12.3
AdoptionLog-scaled stars · package downloads
7.8 / 20
in line with avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-15
Rank Moved
Rank dropped 10 spots (#1026 → #1036)
2026-10-12
Rank Moved
Rank dropped 13 spots (#1009 → #1022)
2026-10-10
Rank Moved
Rank dropped 18 spots (#987 → #1005)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.3/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 Opendocswork MCP View MCP Servers Report missing data
41.9
Activity sub-score · out of 100
#591
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 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-10-16 16:07 UTC · Repo last pushed 16 days ago

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
164
Forks
16
Last Push
2026-09-30
16 days ago
Commits (4 wk)
0
Downloads (7d)
69
npm
HN mentions (30d)
—
Open Issues
1
Rank Change
▼2
was #1036

Analysis

Activity Inputs

41.9 / 100
StarsRepository reach
13.3 / 30
FreshnessLast push recency
22.8 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
5.7 / 20

Common questions about Opendocswork MCP

Public trust evidence for Opendocswork 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 Opendocswork MCP publish package provenance?
No published build provenance is currently detected for Opendocswork 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 Opendocswork MCP have an OpenSSF Scorecard?
Opendocswork MCP has an OpenSSF Scorecard score of 2.3/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 Opendocswork MCP actively maintained?
Maintained. Last push was 16 days ago.
What license does Opendocswork MCP use?
Opendocswork MCP ships under GPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Opendocswork MCP's commits signed?
0% of the last 100 commits to Opendocswork 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
Opendocswork MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
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
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 Opendocswork 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-30
Activity Resumed
Activity resumed
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-14
Activity Went Stale
No commits for 90 days

Maintain Opendocswork MCP?

For maintainers

HVTrust scores Opendocswork 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
Rank 26HVTrust 3Listed 2Grade 2Scorecard 1Stale 1Delisted 1MCP 1Score 1Fresh 1
2026-10-15
Rank Moved
Rank dropped 10 spots (#1026 → #1036)
2026-10-12
Rank Moved
Rank dropped 13 spots (#1009 → #1022)
2026-10-10
Rank Moved
Rank dropped 18 spots (#987 → #1005)
2026-10-09
Rank Moved
Rank dropped 16 spots (#971 → #987)
2026-10-01
Grade Changed
Trust grade C → D
2026-09-30
Activity Resumed
Activity resumed
2026-09-30
Grade Changed
Trust grade D → C
2026-09-30
Rank Moved
Rank rose 155 spots (#1112 → #957)
2026-09-30
HVTrust Changed
HVTrust up 7.1pts (42.9 → 50.0)
2026-09-30
Activity Score Changed
Activity score up 15pts (29 → 44)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 125 spots (#1221 → #1096)
2026-09-23
HVTrust Changed
HVTrust up 25.5pts (17.7 → 43.2)
2026-09-22
Newly Listed
First tracked at rank #1221
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-14
Activity Went Stale
No commits for 90 days
2026-09-13
Rank Moved
Rank dropped 23 spots (#1056 → #1079)
2026-09-12
Rank Moved
Rank dropped 12 spots (#1044 → #1056)
2026-09-09
Rank Moved
Rank dropped 17 spots (#1016 → #1033)
2026-09-08
Rank Moved
Rank dropped 18 spots (#998 → #1016)
2026-09-07
Rank Moved
Rank dropped 32 spots (#966 → #998)
2026-09-06
Rank Moved
Rank dropped 14 spots (#952 → #966)
2026-09-05
Rank Moved
Rank dropped 50 spots (#902 → #952)
2026-09-04
Rank Moved
Rank dropped 26 spots (#876 → #902)
2026-09-03
Rank Moved
Rank dropped 58 spots (#818 → #876)
2026-09-02
Rank Moved
Rank dropped 47 spots (#771 → #818)
2026-09-01
Rank Moved
Rank dropped 32 spots (#739 → #771)
2026-08-31
Rank Moved
Rank dropped 34 spots (#705 → #739)
2026-08-30
Rank Moved
Rank dropped 24 spots (#681 → #705)
2026-08-29
Scorecard Added
OSSF Scorecard: 2.9/10
2026-08-29
Rank Moved
Rank rose 285 spots (#966 → #681)
2026-08-29
HVTrust Changed
HVTrust up 17.5pts (28.8 → 46.3)
2026-08-28
Rank Moved
Rank dropped 34 spots (#932 → #966)
2026-08-27
Rank Moved
Rank dropped 25 spots (#907 → #932)
2026-08-26
Rank Moved
Rank dropped 112 spots (#795 → #907)
2026-08-19
Rank Moved
Rank dropped 11 spots (#784 → #795)
2026-08-16
Rank Moved
Rank dropped 15 spots (#776 → #791)
2026-08-10
Rank Moved
Rank dropped 41 spots (#731 → #772)
2026-08-08
Newly Listed
First tracked at rank #730
GitHub → npm: @aimino/opendocswork-mcp

Embed Badge Badge guide for maintainers →

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