Skip to main content
Glama
User0856

snaprender-mcp

by User0856
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to snaprender-mcp

No user-submitted related servers found.

    Related Servers

    • PagePixels Screenshots MCP Server by PagePixels

      PagePixels Screenshots MCPofficial

      PagePixels
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to capture website screenshots, automate browser interactions, and manage recurring screenshot configurations across 150+ global locations. It also supports AI-powered domain research and visual change monitoring for any web page.
      6 npm
      MIT
    • screenshots-snapshot-site by snapshot-site

      screenshots-snapshot-siteofficial

      snapshot-site
      A
      license
      A
      quality
      A
      maintenance
      Screenshot, visual-diff, and AI page-analysis API for AI agents. Capture any URL as PNG, JPEG, WebP, PDF, or HTML, diff two versions of a page to catch visual regressions, and get an AI summary of what a page contains.
      3
      45 npm
      1
      MIT

    • OtterSnap

      zzzjy765
      A
      license
      A
      quality
      B
      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
      82 npm
      MIT

    • shotpipe-mcp

      podop29
      A
      license
      Not graded
      quality
      C
      maintenance
      Hosted, SSRF-safe, cached screenshots and Open Graph images for AI agents - no headless Chrome to run.
      34 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct purpose: checking cache, retrieving usage stats, and capturing screenshots. There is no overlap in functionality.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case, making the set predictable and easy to understand.

    Tool Count5/5

    Three tools is an appropriate size for a focused screenshot service, covering essential operations without unnecessary complexity.

    Completeness4/5

    The tool set covers the core workflow of capturing screenshots, with supplementary tools for cache checking and usage tracking. A minor gap is the absence of cache management operations.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources