Markcrawl vs Datagokr — 한국 공공데이터 검색 (Korean public data search)
In-depth architectural comparison of the Markcrawl and Datagokr — 한국 공공데이터 검색 (Korean public data search) 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
Markcrawl
Search & Data Extraction · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Datagokr — 한국 공공데이터 검색 (Korean public data search)
Search & Data Extraction · Local stdio
Quality: 36/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Markcrawl if you need specialized Search & Data Extraction tools running via a local process. Choose Datagokr — 한국 공공데이터 검색 (Korean public data search) if your workspace requires Search & Data Extraction integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Markcrawl when:
You need dedicated capabilities in the Search & Data Extraction domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Single-page and whole-site crawling, Clean Markdown and JSONL output, Citation metadata with access dates.
Markcrawl is categorized under Search & Data Extraction and uses a local stdio subprocess. In contrast, Datagokr — 한국 공공데이터 검색 (Korean public data search) belongs to Search & Data Extraction using local stdio subprocess. Select Markcrawl when you need capabilities focused on search & data extraction and Datagokr — 한국 공공데이터 검색 (Korean public data search) when you require tools for search & data extraction.