THRONE
See report Verify server

registry / record

github.com/zcaceres/markdownify-mcp

github / sealed 2026-06-14 / No. 35ef2e98

> throne registry github.com/zcaceres/markdownify-mcp sealed
receiptsealed evidence
scan id
35ef2e98dec24aaa98f79bb7ec39daae
target
https://github.com/zcaceres/markdownify-mcp
sealed at
2026-06-14 06:28:44Z
evidence hash
sha256:182518f52e6b274fabd849ac3872235aad17fd18a728f0856421643ecb0bb047
01connectPASS770ms

initialize ok: server mcp-markdownify-server 0.1.0, negotiated protocolVersion 2025-11-25, capabilities ['tools']

02discoverPASS6ms

supported: tools/list (11 tools); method not found (tolerated): resources/list, prompts/list

03validate_schemasPASS11ms

all 11 tool inputSchemas are valid JSON Schema

04smoke_test_toolsPASS10.1s

called 10 of 10 tools (cap 10): 0 ok, 10 returned tool-level errors (expected for synthesized args)

05error_handlingPASS3.8s

structured error responses, connection survived — wrong_type_args: error(-32603); unknown_method: error(-32601); invalid_id: no response (silent), connection alive

06streamingPASS0ms

no streaming-capable tool declared by this server; not applicable (pass-na)

07resource_lifecyclePASS2ms

resources capability not declared; not applicable (pass-na)

08concurrent_callsWARN15.7s

ladder 1/2/4/8 overlapping audio-to-markdown calls: max_observed_stable_concurrency=4; degraded above that — level 8: id mapping broken — 8 distinct request ids, 1 matched exactly once (expected 8)

09reconnectPASS7.4s

transport closed and relaunched; re-handshake ok (protocolVersion 2025-11-25, first session was 2025-11-25)

01connectPASS4.1s

initialize ok: server mcp-markdownify-server 0.1.0, negotiated protocolVersion 2025-11-25, capabilities ['tools']

02discoverPASS68ms

supported: tools/list (11 tools); method not found (tolerated): resources/list, prompts/list

03validate_schemasPASS13ms

all 11 tool inputSchemas are valid JSON Schema

04smoke_test_toolsPASS40.3s

called 10 of 10 tools (cap 10): 0 ok, 10 returned tool-level errors (expected for synthesized args)

05error_handlingPASS7.0s

structured error responses, connection survived — wrong_type_args: error(-32603); unknown_method: error(-32601); invalid_id: no response (silent), connection alive

06streamingPASS0ms

no streaming-capable tool declared by this server; not applicable (pass-na)

07resource_lifecyclePASS2ms

resources capability not declared; not applicable (pass-na)

08concurrent_callsWARN14.9s

ladder 1/2/4/8 overlapping audio-to-markdown calls: max_observed_stable_concurrency=1; degraded above that — level 2: id mapping broken — 2 distinct request ids, 0 matched exactly once (expected 2)

09reconnectPASS5.1s

transport closed and relaunched; re-handshake ok (protocolVersion 2025-11-25, first session was 2025-11-25)

chatgpt desktopemulation profile pending real-traffic captureCOMING SOON
SECURITY: REVIEW / 2 finding(s), 1 high / review material, not a verdict
HIGHTHR-INSTALL-03 / Install-time script execution (npm lifecycle)

"preinstall" runs arbitrary code on every npm install: 'node preinstall.js'

markdownify-mcp-HEAD/package.json
LOWTHR-VER-11 / Outdated MCP SDK or protocol version pin

obsolete protocol version string '2024-11-05' in source

markdownify-mcp-HEAD/scripts/docker-smoke-test.sh:23
VERDICT: FIT TO SHIPSANDBOXED RUN — submitted server executed in a disposable microVM — compatibility: 0 fail / 2 warn across 2 clients / security: review — 2 finding(s), 1 highsealed by THRONE / No. 35ef2e98 / 2026-06-14
THRONE: FIT TO SHIPwear the crown

paste this in your README. it renders the live verdict and links back to this record. if a release ever breaks the verdict, the badge says so on its own.

[![THRONE: FIT TO SHIP](https://api.usethrone.dev/api/badge/https%3A%2F%2Fgithub.com%2Fzcaceres%2Fmarkdownify-mcp)](https://usethrone.dev/server/zcaceres-markdownify-mcp)
executed in a disposable microVM, created for this scan and destroyed after it. nothing outlives a run.

maintainer of this server? challenge this record: hello@usethrone.dev. tell us what we got wrong and we re-run it in the open.

this page renders the stored record of a real run. nothing on it is asserted without the execution that proved it.