Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MarsDawn

MCPB · MARSDAWN.MCPB

Export Markdown to PDF and open it in the MarsDawn app on macOS, with the marsdawn CLI.

Available components

0 this week 61 Trust /100

Last scanned (4 hours ago)

Scores higher than 94% of MCPB servers

Category Documents and Files

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security23
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs were checked across the 92 of 92 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 26 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 514 tokens (~257/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 1 Nov 26 0
    • Stability: 0.97 → pass security
  • 31 Oct 26 0
    • Stability: pass → 0.97 functional
  • 25 Oct 26 0
    • Stability: 0.97 → pass security
  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed mcpb/https://github.com/redtear1115/marsdawn-mcp/releases/download/v0.2.4/marsdawn.mcpb@0.2.4

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem mcpb
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~514 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
export_markdown_to_pdf ~286

Export a Markdown file to a paginated PDF on this Mac with the marsdawn command-line tool, rendered like MarsDawn's preview, Mermaid diagrams included. Needs marsdawn 0.5.0 or later (`brew install redtear1115/tap/marsdawn`). Writes the PDF beside the input unless `output` is given, and won't replace an existing PDF unless `force` is true. Web images are left out unless `allowRemoteImages` is true. It reads and writes only inside the folders the user allowed, and refuses anything outside them.

NameTypeReqDescription
allowRemoteImagesboolean–Load images from the web while rendering. This reaches the network.
forceboolean–Replace the output file if it already exists.
inputstringyesAbsolute path of the Markdown file to export, inside an allowed folder; a plain absolute path without `.` or `..` components.
outputstring–Absolute path to write the PDF to, inside an allowed folder; a plain absolute path without `.` or `..` components, and it must end in .pdf. Defaults to the input path with a .pdf extension.
paperstring–Paper size. Defaults to a4.
themestring–Preview theme (light palette). Defaults to $MARSDAWN_THEME, or dawn.
NameTypeReqDescription
diagramErrorDetailsarray–The same failures as `diagramErrors`, in the same order, each as `{message, fenceLine, line}`. `fenceLine` is the document line the diagram's fence starts on, present whenever that's known. `line…
diagramErrorsarrayyesOne message per Mermaid diagram that failed to render. The PDF is still written.
ok–yes–
outputstringyesAbsolute path of the PDF that was written.
pagesintegeryesNumber of pages in the PDF.
paper–yesPaper size used for the export.
theme–yesTheme used for the export.

No examples provided.

open_in_marsdawn ~228

Open a Markdown file in the MarsDawn app on this Mac for the user to review, with the marsdawn command-line tool. Needs the MarsDawn app, from the Mac App Store (https://apps.apple.com/app/id6812925073). Call this once per file: the window stays open and follows the file's later edits by itself, so there's no need to call it again after every change, only when a new file needs review or the user should be sent to a different line. `background` opens the file without bringing MarsDawn to the front, so the window the user is already working in keeps focus. It opens only files inside the folders the user allowed, and refuses anything outside them.

NameTypeReqDescription
backgroundboolean–Open without bringing MarsDawn to the front.
lineinteger–Line to land on.
pathstringyesAbsolute path of the Markdown file to open, inside an allowed folder; a plain absolute path without `.` or `..` components. Must be a file, not a folder.
NameTypeReqDescription
appstringyesPath of the MarsDawn app that opened them.
ok–yes–
openedarrayyesThe files that were opened, in the order given.

No examples provided.

Install

How do I install the MarsDawn MCP server?

MarsDawn ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 8925b836c7ab3959f4e7a98452aa0fe60442c38c79055304219998aebbcb5f41; the commands to do that are on this page. If it does not match, do not open it.

mcpb · marsdawn.mcpb

Download bundle

Check the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.

SHA-256

8925b836c7ab3959f4e7a98452aa0fe60442c38c79055304219998aebbcb5f41

macOS / Linux

echo "8925b836c7ab3959f4e7a98452aa0fe60442c38c79055304219998aebbcb5f41  marsdawn.mcpb" | shasum -a 256 -c

Windows (PowerShell)

(Get-FileHash -Algorithm SHA256 .\marsdawn.mcpb).Hash -eq "8925b836c7ab3959f4e7a98452aa0fe60442c38c79055304219998aebbcb5f41"

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.

Common questions

What is the MarsDawn MCP server?

MarsDawn is an MCP server listed in the public MCP registry as dev.southern-light.mcp/marsdawn. Export Markdown to PDF and open it in the MarsDawn app on macOS, with the marsdawn CLI. This page covers its MCPB bundle (https://github.com/redtear1115/marsdawn-mcp/releases/download/v0.2.4/marsdawn.mcpb).

Is the MarsDawn MCP server safe to use?

MarsDawn scores 61 out of 100 on VerifyMCP. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the MarsDawn MCP server expose?

MarsDawn exposes 2 tools: export_markdown_to_pdf, open_in_marsdawn. Their descriptions and schemas cost roughly 514 tokens of context every time the server is loaded.

What licence is the MarsDawn MCP server under?

MarsDawn declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.