updated 2026-11-10 04:07 UTC

Aigroup Mdtoword MCP

Repository

Markdown-to-Word MCP server with advanced styling, formulas, tables, Mermaid rendering, and HTTP deployment support.

MCP Servers JavaScript Listed MIT

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

OSSF Scorecard 2.5 / 10
Provenance None
Signed commits 0%
Last push 200d ago
Advisories None known
Compare Aigroup Mdtoword MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Aigroup Mdtoword MCP scores 35.7/100 (Grade D), ranked #1282 of 1374 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.5/10; recent commits are unsigned; no published advisory affects its latest release (aigroup-mdtoword-mcp); last pushed 2026-04-24. Every point is earned from checkable signals — never paid placement. How scoring works →

How Aigroup Mdtoword 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 Aigroup Mdtoword 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/jackdark425/aigroup-mdtoword-mcp, MIT, last pushed 2026-04-24. 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.5/10 (scanned Nov 3, 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 9
    Branch-Protection 0
    CI-Tests -1
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    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 10

  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: aigroup-mdtoword-mcp 4.0.4. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

  • 2026-08-28 OSSF Scorecard: 2.5/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 Aigroup Mdtoword 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 Aigroup Mdtoword MCP compares in MCP Servers

  1. #739 Flowbite MCP 35.8 +0.1
  2. #740 Unreal MCP Ue4 35.8 +0.1
  3. #741 Aigroup Mdtoword MCP 35.7 this agent
  4. #742 SignNow Api Helper MCP 35.6 −0.1
  5. #743 Pcb MCP 35.6 −0.1

Bars show each HVTrust score; the tick marks Aigroup Mdtoword MCP’s 35.7.

Where the 35.7 comes from

HVTrust dimensions vs the MCP Servers average

35.7 / 100 · 100.0% confidence

Aigroup Mdtoword MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.1 / 25
7.7 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
10.6 / 17
1.7 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
0 / 20
12.2 below avg 12.2
AdoptionLog-scaled stars · package downloads
5.2 / 20
2.4 below avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.5/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 200 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent
View MCP Servers Report missing data
9.3
Activity sub-score · out of 100
#741
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-11-10 04:07 UTC · Repo last pushed 200 days ago — may be stale

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
14
Forks
2
Last Push
2026-04-24
200 days ago
Commits (4 wk)
0
Downloads (7d)
61
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▲1
was #1283

Analysis

Activity Inputs

9.3 / 100
StarsRepository reach
7.1 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
2.2 / 20

Common questions about Aigroup Mdtoword MCP

Public trust evidence for Aigroup Mdtoword 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 Aigroup Mdtoword MCP publish package provenance?
No published build provenance is currently detected for Aigroup Mdtoword 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 Aigroup Mdtoword MCP have an OpenSSF Scorecard?
Aigroup Mdtoword MCP has an OpenSSF Scorecard score of 2.5/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 Aigroup Mdtoword MCP actively maintained?
Stale. The repository has not been pushed to in 200 days. Consider whether the project is still being maintained.
What license does Aigroup Mdtoword MCP use?
Aigroup Mdtoword MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Aigroup Mdtoword MCP's commits signed?
0% of the last 100 commits to Aigroup Mdtoword 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
Aigroup Mdtoword 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 Aigroup Mdtoword 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

Maintain Aigroup Mdtoword MCP?

For maintainers

HVTrust scores Aigroup Mdtoword 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 17HVTrust 5Scorecard 1Delisted 1Listed 1MCP 1
2026-10-09
Rank Moved
Rank dropped 12 spots (#1237 → #1249)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 83 spots (#1285 → #1202)
2026-09-23
HVTrust Changed
HVTrust up 23.9pts (13.8 → 37.7)
2026-09-22
Newly Listed
First tracked at rank #1285
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-09
Rank Moved
Rank dropped 16 spots (#1161 → #1177)
2026-09-08
Rank Moved
Rank dropped 11 spots (#1150 → #1161)
2026-09-07
Rank Moved
Rank dropped 20 spots (#1130 → #1150)
2026-09-06
Rank Moved
Rank dropped 16 spots (#1114 → #1130)
2026-09-05
Rank Moved
Rank rose 140 spots (#1254 → #1114)
2026-09-05
HVTrust Changed
HVTrust up 12.7pts (26.3 → 39.0)
2026-09-04
Rank Moved
Rank dropped 204 spots (#1050 → #1254)
2026-09-04
HVTrust Changed
HVTrust down 12.8pts (39.1 → 26.3)
2026-09-03
Rank Moved
Rank dropped 59 spots (#991 → #1050)
2026-09-02
Rank Moved
Rank rose 177 spots (#1168 → #991)
2026-09-02
HVTrust Changed
HVTrust up 12.8pts (26.4 → 39.2)
2026-09-01
Rank Moved
Rank dropped 45 spots (#1123 → #1168)
2026-08-31
Rank Moved
Rank dropped 30 spots (#1093 → #1123)
2026-08-30
Rank Moved
Rank dropped 48 spots (#1045 → #1093)
2026-08-29
Rank Moved
Rank dropped 51 spots (#994 → #1045)
2026-08-28
Scorecard Added
OSSF Scorecard: 2.5/10
2026-08-28
Rank Moved
Rank rose 270 spots (#1264 → #994)
2026-08-28
HVTrust Changed
HVTrust up 10.3pts (16.3 → 26.6)
2026-08-26
Rank Moved
Rank dropped 27 spots (#1229 → #1256)
2026-08-16
Rank Moved
Rank dropped 26 spots (#1202 → #1228)
GitHub → npm: aigroup-mdtoword-mcp

Embed Badge Badge guide for maintainers →

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