updated 2026-10-16 20:06 UTC

Markdownify MCP

Repository

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 21d ago
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 48.8/100 (Grade D), ranked #1043 of 1378 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 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 Markdownify MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/zcaceres/markdownify-mcp, MIT, last pushed 2026-09-25. 59% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 2.7/10 (scanned Oct 16, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection3
    • Signed Releasesn/a
    • Dangerous Workflown/a
    • Token Permissionsn/a
    • Pinned Dependencies0
    All 18 Scorecard checks
    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

  3. Published packages None

    No registry package. Markdownify MCP is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-08-31 OSSF Scorecard: 2.7/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Markdownify 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 Markdownify MCP compares in MCP Servers

  1. #593 Notebooklm MCP Secure 48.8 ±0
  2. #594 Wechat Devtools MCP 48.8 ±0
  3. #595 Markdownify MCP 48.8 this agent
  4. #596 Apple Rag MCP 48.8 ±0
  5. #597 CometChat Docs 48.6 −0.2

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

Where the 48.8 comes from

HVTrust dimensions vs the MCP Servers average

48.8 / 100 · 100.0% confidence

Markdownify MCP MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.3 / 25
4.2 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.8 / 17
1.5 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
10.6 / 20
1.7 below avg 12.3
AdoptionLog-scaled stars · package downloads
8.3 / 20
0.9 above 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-11
Rank Moved
Rank dropped 11 spots (#1004 → #1015)
2026-10-10
Rank Moved
Rank dropped 13 spots (#991 → #1004)
2026-10-09
Rank Moved
Rank dropped 14 spots (#977 → #991)
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
54.2
Activity sub-score · out of 100
#595
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 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 →

Signals refreshed 2026-10-16 20:06 UTC · Repo last pushed 21 days ago

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
3.0k
Forks
255
Last Push
2026-09-25
21 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
11
Rank Change
▼3
was #1040

Analysis

Activity Inputs

54.2 / 100
StarsRepository reach
20.9 / 30
FreshnessLast push recency
22.1 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
11.2 / 20

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?
Maintained. Last push was 21 days ago.
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
Rank 22Grade 5Listed 2HVTrust 2Scorecard 1Surface 1Delisted 1MCP 1
2026-10-11
Rank Moved
Rank dropped 11 spots (#1004 → #1015)
2026-10-10
Rank Moved
Rank dropped 13 spots (#991 → #1004)
2026-10-09
Rank Moved
Rank dropped 14 spots (#977 → #991)
2026-09-30
Rank Moved
Rank dropped 14 spots (#944 → #958)
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
HVTrust 48.8 Grade D
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.4 · Raw JSON