visimark
Related Servers
Alternatives to visimark
No user-submitted related servers found.
Related Servers
- AlicenseBqualityFmaintenanceProvides intelligent manuscript analysis and writing assistance for markdown projects, including semantic search, quality checks, terminology consistency, link validation, progress tracking, and comprehensive writing statistics.35131 npm13MIT
- AlicenseNot gradedqualityDmaintenanceEnables intelligent Markdown document analysis including extracting table of contents with hierarchy, detecting numbering issues like duplicates and discontinuities, and generating formatted TOC content in multiple output formats.1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables sharing Markdown documents for collaborative review with inline annotations and structured change requests.7 npmMIT
- AlicenseNot gradedqualityBmaintenanceExposes a living systems memory vault to autonomous agents, letting them search notes with BM25 ranking, read sections within token budgets, extract API/port/schema contracts, compute dependency blast radius, and run machine-verifiable invariant assertions before mutating code. It also supports surgical frontmatter edits, schema linting, wikilink integrity checks, and worklog recording, over stdio MCP.MIT
- FlicenseNot gradedqualityDmaintenanceEnables querying and modifying Markdown documentation as a relational database using SQL, with automatic write-back of changes to the original .md files.-

openmarkdownofficial
FlicenseNot gradedqualityAmaintenanceLocal-first Markdown editor whose MCP server lets a coding agent and a human co-edit the same .md file — it opens and reveals files in the editor and reads or section-edits their contents. Tools: open_file, reveal, read_section, write_section, wait_for_change.63-
TDQS
Scored across 8 tools
Each tool has a clearly distinct role: ref (lookup builtins), explain (describe declarations), eval (compute values), check (verify agreement), infer (propose rules), fmt (plan repairs), and their _apply counterparts. The plan-then-apply split is explicit and the read-only analyzers (check vs eval vs explain) are differentiated by their descriptions.
All tools use a consistent visimark_ snake_case prefix with verb-based names, and the _apply suffix reliably marks write actions. Minor deviation: 'ref' and 'fmt' are abbreviations while others are full verbs, but the pattern remains predictable.
Eight tools is well-scoped for a document-analysis/formula-verification server, with each tool earning its place. Read/plan/apply responsibilities are cleanly separated without redundancy.
The surface covers the full lifecycle: reference lookup, document description, evaluation, verification, inference, formatting, and the apply operations to land each plan, all with write-safety gating. No obvious gaps for the stated domain.