markdown-editor-mcp-server (Kcao3034/markdown-editor-mcp-server) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 15 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

markdown-editor-mcp-server

📝 Enhance your Markdown workflow with this MCP server, designed for structured editing and full compliance with MCP 2025 standards.

→ Kcao3034/markdown-editor-mcp-server· listed on github_repo_search

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

Kcao3034

Source: github_repo_search

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
// tools this server exposes15 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

search_tools

Scalability feature: find the right tool for your complex task among all available tools.

get_document_structure

Parses the Markdown file and returns a tree of headings and elements. Use this first to navigate.

search_text

Performs a semantic search for text strings and returns their structural paths.

get_context

Returns the target element along with its immediate neighbors (before and after).

read_element

Fetches the full content of a specific block by its path.

replace_content

Overwrites the content of a specific block. Maintains document structure.

insert_element

Inserts a new block (heading, paragraph, etc.) relative to an existing one.

move_element

Moves an element (and its children) to a new location in the document.

delete_element

Removes a block from the document.

update_metadata

Modifies the document's Frontmatter.

undo

Reverts the last N operations on the document.

list_directory

Lists files and folders in the workspace.

create_file
create_directory
delete_item
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

15/15 tools missing one or more hints — search_tools (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_document_structure (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search_text (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +12 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 2 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/kcao3034/markdown-editor-mcp-server)](https://m8ven.ai/mcp/kcao3034/markdown-editor-mcp-server)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: d50849f5e6d91699dadd295f5de3da523a7109de
code hash: c05820c9bc6994be6d916872afaf3a424f8803bcaffa26cd7cdd25ac88369915
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client