Is Markdownify MCP safe to use?

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

What is the trust score for Markdownify MCP?

Markdownify MCP scores 50.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 3.0k GitHub stars and is categorized under MCP Servers.

Markdownify MCP

zcaceres/markdownify-mcp

A Model Context Protocol server for converting almost anything to Markdown

MCP Servers TypeScript Listed MIT

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

OSSF Scorecard 2.7 / 10

Provenance None

Signed commits 59%

Last push yesterday

Compare Markdownify MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Markdownify MCP scores 50.1/100 (Grade C), ranked #934 of 1325 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.7/10; 59% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →

How Markdownify MCP compares in MCP Servers

Bars show each HVTrust score; the tick marks Markdownify MCP’s 50.1.

Where the 50.1 comes from

HVTrust dimensions vs the MCP Servers average

50.1 / 100 · 100.0% confidence

Markdownify MCP MCP Servers average (775 agents)

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

6.3 / 25

4.0 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.8 / 17

1.4 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

11.9 / 20

in line with avg 12.1

AdoptionLog-scaled stars · package downloads

8.3 / 20

1.1 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

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank dropped 369 spots (#554 → #923)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 2.7/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.

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

57.0

Activity sub-score · out of 100

#535

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 C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

3.0k

Forks

255

Last Push

2026-09-25

yesterday

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #933

Analysis

Activity Inputs

57.0 / 100

StarsRepository reach

20.9 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

11.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

2.7 / 10

OpenSSF Scorecard · scanned Sep 16, 2026

Signed Commits

59%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 0

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow -1

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 0

Common questions about Markdownify MCP

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

No published build provenance is currently detected for Markdownify 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 Markdownify MCP have an OpenSSF Scorecard?

Markdownify MCP has an OpenSSF Scorecard score of 2.7/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 Markdownify MCP actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Markdownify MCP use?

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

Are Markdownify MCP's commits signed?

59% of the last 100 commits to Markdownify 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

Markdownify 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

N/A

No package source configured

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

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

Maintain Markdownify MCP?

For maintainers

HVTrust scores Markdownify 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

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank dropped 369 spots (#554 → #923)

2026-09-23

HVTrust Changed

HVTrust up 13.3pts (36.8 → 50.1)

2026-09-22

Newly Listed

First tracked at rank #554

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-18

Grade Changed

Trust grade C → D

2026-09-09

Rank Moved

Rank dropped 17 spots (#896 → #913)

2026-09-07

Grade Changed

Trust grade D → C

2026-09-07

Rank Moved

Rank dropped 28 spots (#859 → #887)

2026-09-06

Rank Moved

Rank dropped 18 spots (#841 → #859)

2026-09-05

Rank Moved

Rank dropped 58 spots (#783 → #841)

2026-09-04

Grade Changed

Trust grade C → D

2026-09-04

Rank Moved

Rank dropped 31 spots (#752 → #783)

2026-09-03

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

2026-09-03

Grade Changed

Trust grade D → C

2026-09-03

Rank Moved

Rank dropped 30 spots (#722 → #752)

2026-09-02

Rank Moved

Rank dropped 32 spots (#690 → #722)

2026-09-01

Rank Moved

Rank dropped 28 spots (#662 → #690)

2026-08-31

Scorecard Added

OSSF Scorecard: 2.7/10

2026-08-31

Rank Moved

Rank rose 490 spots (#1152 → #662)

2026-08-31

HVTrust Changed

HVTrust up 27.0pts (22.6 → 49.6)

2026-08-30

Rank Moved

Rank dropped 39 spots (#1113 → #1152)

2026-08-29

Rank Moved

Rank dropped 38 spots (#1075 → #1113)

2026-08-27

Rank Moved

Rank dropped 23 spots (#1049 → #1072)

2026-08-26

Rank Moved

Rank dropped 79 spots (#970 → #1049)

2026-08-24

Rank Moved

Rank dropped 21 spots (#951 → #972)

2026-08-17

Rank Moved

Rank rose 14 spots (#967 → #953)

2026-08-16

Rank Moved

Rank dropped 25 spots (#942 → #967)

2026-08-12

Rank Moved

Rank rose 15 spots (#941 → #926)

2026-08-10

Newly Listed

First tracked at rank #949

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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