Is Opendocswork MCP safe to use?

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

What is the trust score for Opendocswork MCP?

Opendocswork MCP scores 43.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 163 GitHub stars and is categorized under MCP Servers.

Opendocswork MCP

Aimino-Tech/opendocswork-mcp

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 102d ago

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 43.0/100 (Grade D), ranked #1102 of 1325 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; last pushed 2026-06-16. Every point is earned from checkable signals — never paid placement. How scoring works →

How Opendocswork MCP compares in MCP Servers

#645 MCP Ip2location Io 43.2 +0.2
#646 Microsoft MCP Server for Enterprise 43.0 ±0
#647 Opendocswork MCP 43.0 this agent
#648 Ux MCP Server 42.9 −0.1
#649 Apple Docs MCP 42.8 −0.2

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

Where the 43.0 comes from

HVTrust dimensions vs the MCP Servers average

43.0 / 100 · 100.0% confidence

Opendocswork MCP MCP Servers average (775 agents)

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

2.9 / 25

7.4 below avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

10.5 / 17

1.7 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

5.2 / 20

6.9 below avg 12.1

AdoptionLog-scaled stars · package downloads

7.6 / 20

in line with avg 7.2

Quick Trust Read

What Would Improve It

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

Recent Changes

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)

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.

Refresh maintenance signals The repo was last pushed 102 days ago. Fresh activity helps separate stable projects from stale ones.

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

30.0

Activity sub-score · out of 100

#647

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 →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

163

Forks

Last Push

2026-06-16

102 days ago

Commits (4 wk)

Downloads (7d)

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #1101

Analysis

Activity Inputs

30.0 / 100

StarsRepository reach

13.3 / 30

FreshnessLast push recency

10.8 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

5.7 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

2.3 / 10

OpenSSF Scorecard · scanned Sep 20, 2026

Signed Commits

of last 100 commits verified

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

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?

Slowing down. Last push was 102 days ago — keep an eye on whether activity resumes.

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

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

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.3 · Raw JSON