Skip to main content
Glama

Related Servers

Alternatives to visimark

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables LLM agents to propose non-destructive CriticMarkup edits, manage threaded review comments, and inspect Markdown efficiently so authors can accept or reject changes in compatible editors.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to record checkpoints for Markdown files and ask what changed since they last looked, returning only the changed Markdown blocks as precise word-level diffs with attribution. Keeps a local, private revision history so multiple readers and writers can each track their own bookmark instead of re-reading whole files.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Read-only MCP server that enables inspecting and auditing markdown agent steering files such as CLAUDE.md, AGENTS.md, GEMINI.md, SKILL.md, rules, commands and memory files. It reads files byte-exactly, outlines headings, lints frontmatter, invisible characters and broken links, estimates per-session token budgets, and locates steering files by when they load, all without ever writing, deleting or making network calls.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes an evidence-first Markdown store of current claims and tasks to AI agents over MCP stdio, letting them search, fetch, trace, list changes, validate, and run maintenance read-only by default. Dropping read-only mode additionally allows adding, transitioning, reviewing, and updating claims and tasks.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables an AI assistant to read and write a local, file-based .emd document through shaped tools — 28 for any document, 85 with the ledger pack — rather than a general query, with every write a dry run until committed, a copy kept beside the document first, and values that break a declared type or rule refused as they are written. On hosts that support MCP Apps it also draws sheets, boards and roadmaps directly in the conversation, falling back to text elsewhere.
      15 npm
      2
      AGPL 3.0

    TDQS

    A4.2/5.0

    Scored across 8 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues