snaprender-mcp

MCPcommunity
v1.5.6io.github.User0856MITUpdated 6d agonpmGitHub

MCP server for the SnapRender screenshot API: lets AI agents capture websites as PNG, JPEG, WebP or PDF, extract content and run batches

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
300Downloads/wk
3GitHub stars
2Forks
6d agoLast update
Needs 1 credential before it runs
  • SNAPRENDER_API_KEYAPI keyrequired

    Your SnapRender API key (starts with sk_live_). Get one free at https://snap-render.com

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.User0856
LicenseMIT
Version1.5.6
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface11 tools · 1 privileged
Security scan✓ Cleanv1.5.6 · 1d agoHow well does this scan work?
EvalsNone
IndexedOct 10, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

11 tools · 1 privileged
Statically extracted from the published packagev1.5.6 · 1d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

take_screenshotCapture a screenshot of a website URL, raw HTML, or Markdown content. Provide exactly one of: url, html, or markdown.

Capture a screenshot of a website URL, raw HTML, or Markdown content. Provide exactly one of: url, html, or markdown.

No input schema was published for this tool.

check_screenshot_cacheCheck if a screenshot is already cached without capturing a new one.

Check if a screenshot is already cached without capturing a new one.

No input schema was published for this tool.

sign_screenshot_urlGenerate a signed URL for a screenshot that can be used without an API key.

Generate a signed URL for a screenshot that can be used without an API key.

No input schema was published for this tool.

extract_contentExtract content from a web page. Returns structured data based on the extraction type.

Extract content from a web page. Returns structured data based on the extraction type.

No input schema was published for this tool.

batch_screenshotsCreate a batch screenshot job for multiple URLs (1-50).

Create a batch screenshot job for multiple URLs (1-50).

No input schema was published for this tool.

get_batch_statusGet the status of a batch screenshot job. Poll this until status is 'completed' or 'failed' (wait 2-5 seconds between polls).

Get the status of a batch screenshot job. Poll this until status is 'completed' or 'failed' (wait 2-5 seconds between polls).

No input schema was published for this tool.

list_webhooksList all webhook subscriptions on your account.

List all webhook subscriptions on your account.

No input schema was published for this tool.

create_webhookCreate a webhook subscription for event notifications.

Create a webhook subscription for event notifications.

No input schema was published for this tool.

delete_webhookprivilegedDelete a webhook subscription by ID. This cannot be undone.

Delete a webhook subscription by ID. This cannot be undone.

No input schema was published for this tool.

test_webhookSend a test payload to a webhook endpoint to verify it receives events correctly.

Send a test payload to a webhook endpoint to verify it receives events correctly.

No input schema was published for this tool.

get_usageGet current month's screenshot usage statistics including

Get current month's screenshot usage statistics including

No input schema was published for this tool.

11 of 11 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for the SnapRender screenshot API: lets AI agents capture websites as PNG, JPEG, WebP or PDF, extract content and run batches

Keywords
mcpscreenshotapisnaprenderclaudeaiagentmodel-context-protocol
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-11 — observed resolution, not a publisher declaration.

60 packages resolved · 1 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+42 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in images, video & audio