Md Log MCP vs Shield — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Md Log MCP vs Shield
In-depth architectural comparison of the Md Log MCP and Shield MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Md Log MCP
Security · Local stdio
Quality: 56/100 (Good) | Auth: No auth required
Shield
Security · Local stdio
Quality: 63/100 (Good) | Auth: No auth required
Verdict Summary: Choose Md Log MCP if you need specialized Security tools running via a local process. Choose Shield if your workspace requires Security integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Md Log MCP when:
You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
md-log MCP: save/update/fetch markdown by path (stdio + remote HTTP, PAT auth).
Local guardrail proxy for AI coding agents. Wraps any MCP server (stdio or Streamable HTTP) and blocks destructive tool calls — DROP TABLE, rm -rf, force-push — before they execute. MCP supply-chain protection: TOFU tool-catalog pinning against rug pulls, plus tool-description and tool-result scanning for tool poisoning and prompt injection. 51 starter rules, approval gates, audit logging. Single binary, Apache-2.0.
Category & Scope
Tools & Capabilities Breakdown
Md Log MCP Tools (14)
upload_asset
Upload one image (reserve → presigned PUT → complete) and return an `asset://<key>` reference to embed as ``. Provide the image as **either** `data_base64` (inline base64) **or** `file_path` (a local file the server reads) — exactly one; with `file_path`, `filename` defaults to…
append_to_markdown
Append to an existing file with optimistic concurrency (GET current → concat → conditional PUT with `base_version_no`). Auto-retries once on conflict, then surfaces `CONFLICT`. Accepts `commit_message` — a recommended 1-2 line change summary shown in the version history.
update_markdown
Replace a file's content. Pass `expected_version` for optimistic concurrency (mismatch → `CONFLICT`); omit it to force LWW. Accepts `commit_message` — a recommended 1-2 line change summary shown in the version history.
get_markdown
Read a file's content by path (materializes inline content or a presigned content URL for large docs). Pass `version` (a `version_no` from `list_versions`) to read an old immutable version.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Md Log MCP is categorized under Security and uses a local stdio subprocess. In contrast, Shield belongs to Security using local stdio subprocess. Select Md Log MCP when you need capabilities focused on security and Shield when you require tools for security.
List a file's immutable version history, newest first (`version_no`, `commit_message`, author, `registered_at`, size).
delete_markdown
Soft-delete a file. Requires `confirm:true` (otherwise `VALIDATION`); resolves the path to a document key first.
create_folder
mkdir -p` — create every missing segment; already-existing folders count as success.
list_folders
Return the full folder tree.
list_files
List the documents and immediate subfolders inside a folder path.
search_markdown
Search by TITLE (substring) + BODY full-text (current versions; whole-word match, ranked, body hits include a snippet).
move_markdown
Move and/or rename a `.md` by path (`from_path` → `to_path`); destination folders auto-created; the document KEEPS its key, so version history and reviewers' annotations survive.
move_folder
Move a folder (whole subtree) under a new parent (`new_parent_path` empty/omitted = root); parent auto-created; cyclic moves rejected server-side.