Is Word MCP Live safe to use?

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

What is the trust score for Word MCP Live?

Word MCP Live scores 44.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 224 GitHub stars and is categorized under MCP Servers.

Word MCP Live

ykarapazar/word-mcp-live

The only MCP server that edits Word documents while they're open — 114 tools, live editing, tracked changes, per-action undo

MCP Servers Python Listed MIT

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

OSSF Scorecard 2.3 / 10

Provenance None

Signed commits 21%

Last push 120d ago

Compare Word MCP Live

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Word MCP Live scores 44.1/100 (Grade D), ranked #1086 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; 21% of recent commits are signed; last pushed 2026-05-29. Every point is earned from checkable signals — never paid placement. How scoring works →

How Word MCP Live compares in MCP Servers

Bars show each HVTrust score; the tick marks Word MCP Live’s 44.1.

Where the 44.1 comes from

HVTrust dimensions vs the MCP Servers average

44.1 / 100 · 100.0% confidence

Word MCP Live MCP Servers average (775 agents)

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

3.9 / 25

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

4.0 / 20

8.1 below avg 12.1

AdoptionLog-scaled stars · package downloads

8.9 / 20

1.7 above 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 150 spots (#1230 → #1080)

2026-09-23

HVTrust Changed

HVTrust up 27.1pts (17.1 → 44.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 120 days ago. Fresh activity helps separate stable projects from stale ones.

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

30.2

Activity sub-score · out of 100

#636

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

224

Forks

Last Push

2026-05-29

120 days ago

Commits (4 wk)

Downloads (7d)

285

pypi

HN mentions (30d)

—

Open Issues

Rank Change

was #1086

Analysis

Activity Inputs

30.2 / 100

StarsRepository reach

14.1 / 30

FreshnessLast push recency

8.3 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

7.6 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

2.3 / 10

OpenSSF Scorecard · scanned Sep 25, 2026

Signed Commits

21%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Common questions about Word MCP Live

Public trust evidence for Word MCP Live 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 Word MCP Live publish package provenance?

No published build provenance is currently detected for Word MCP Live. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Word MCP Live have an OpenSSF Scorecard?

Word MCP Live 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 Word MCP Live actively maintained?

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

What license does Word MCP Live use?

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

Are Word MCP Live's commits signed?

21% of the last 100 commits to Word MCP Live 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

Word MCP Live 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 Word MCP Live'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-08-27

Activity Went Stale

No commits for 90 days

Maintain Word MCP Live?

For maintainers

HVTrust scores Word MCP Live 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 150 spots (#1230 → #1080)

2026-09-23

HVTrust Changed

HVTrust up 27.1pts (17.1 → 44.2)

2026-09-22

Newly Listed

First tracked at rank #1230

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-12

Rank Moved

Rank dropped 11 spots (#1041 → #1052)

2026-09-09

Rank Moved

Rank dropped 19 spots (#1019 → #1038)

2026-09-08

Rank Moved

Rank dropped 10 spots (#1009 → #1019)

2026-09-07

Rank Moved

Rank dropped 35 spots (#974 → #1009)

2026-09-06

Rank Moved

Rank dropped 13 spots (#961 → #974)

2026-09-05

Rank Moved

Rank dropped 48 spots (#913 → #961)

2026-09-04

Scorecard Added

OSSF Scorecard: 2.3/10

2026-09-04

Rank Moved

Rank rose 307 spots (#1220 → #913)

2026-09-04

HVTrust Changed

HVTrust up 16.4pts (29.1 → 45.5)

2026-09-03

Rank Moved

Rank dropped 47 spots (#1173 → #1220)

2026-09-02

Rank Moved

Rank dropped 40 spots (#1133 → #1173)

2026-09-01

Rank Moved

Rank dropped 41 spots (#1092 → #1133)

2026-08-31

Rank Moved

Rank dropped 28 spots (#1064 → #1092)

2026-08-30

Rank Moved

Rank dropped 57 spots (#1007 → #1064)

2026-08-29

Rank Moved

Rank dropped 50 spots (#957 → #1007)

2026-08-28

Rank Moved

Rank dropped 36 spots (#921 → #957)

2026-08-27

Activity Went Stale

No commits for 90 days

2026-08-27

Rank Moved

Rank dropped 25 spots (#896 → #921)

2026-08-26

Rank Moved

Rank dropped 109 spots (#787 → #896)

2026-08-16

Rank Moved

Rank dropped 16 spots (#765 → #781)

2026-08-10

Rank Moved

Rank dropped 41 spots (#722 → #763)

2026-08-08

Newly Listed

First tracked at rank #720

GitHub → PyPI: word-mcp-live

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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