Skip to main content
Glama

Related Servers

Alternatives to Tailprint

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Give AI agents eyes on any web page: pixel-perfect screenshots, print-ready PDFs, branded OG images, code images, and structured page extraction (JSON or Markdown).
      7
      37 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to render any URL or raw HTML into PDF files or PNG/JPEG/WebP screenshots over MCP stdio or Streamable HTTP. Output stays in memory with SSRF protection, bounded concurrency, and configurable size and timeout limits.
      237 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Converts any URL into clean, LLM-ready Markdown, text, or HTML with production-grade features like SSRF protection, rate limiting, retries, caching, and structured error handling.
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Web scraping, crawling, and structured data extraction for AI agents. 5 tools: scrape (clean markdown from any URL), crawl (entire sites), map (discover URLs), extract (structured JSON), and search. 833ms avg latency, single binary, self-hostable.
      8
      1,255
      AGPL 3.0
    • A
      license
      A
      quality
      B
      maintenance
      Fetch any web page as clean Markdown or plain text, split it into heading-aware, token-bounded RAG chunks, convert raw HTML, and read page metadata. Uses the Web2MD API on RapidAPI with your own key (free BASIC plan).
      4
      4
      43 npm
      MIT

    TDQS

    A3.7/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools target clearly distinct operations (merge, split, compress, stamp, fill, verify, lifecycle). The main overlap is render_template vs render_pdf, since render_pdf also accepts template_id + JSON data, and generate_einvoice overlaps partially with the invoice template path; descriptions help but an agent could still hesitate over which render entry point to use.

    Naming Consistency5/5

    All 13 names are snake_case with a consistent verb_noun structure (list_templates, get_template_source, render_pdf, merge_pdfs, fill_pdf_form, manage_pdf_lifecycle). No camelCase or stylistic mixing, and the render_* family is predictably grouped.

    Tool Count5/5

    13 tools sits comfortably in the ideal band for a PDF generation/manipulation server. Each tool covers a distinct PDF capability (render, merge, split, compress, stamp, form-fill, verify, lifecycle) with no filler.

    Completeness4/5

    The surface covers the core PDF lifecycle well: templating, rendering, e-invoicing, merge/split/compress, forms, watermarking, verification, and expiration management. Minor gaps remain—no encryption/password protection, page rotation, or text extraction—but agents can work around these via existing render/verify tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues