org.snapforge/snapforge
REMOTE · SNAPFORGE.ORG · 2 COMPONENTS
Screenshots, PDFs and Markdown from any URL or HTML for AI agents, via the SnapForge API
Available components
Last scanned (15 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Documents and Files
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 700 tokens (~175/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Probed https://snapforge.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=snapforge.org | CN=YE2,O=Let's Encrypt,C=US | 8 Oct 2026 | 6 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 54dc65b90e4047e80692186a67b76f5aa48 |
| SANs: snapforge.org | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of snapforge.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| org. | DS published | 725, 26974 | 8, 8 | Verified |
| snapforge.org. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://snapforge.org/mcp | Verified | 200 | |
| http (plaintext) | http://snapforge.org/mcp | HTTPS enforced | 308 | https://snapforge.org/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
snapforge_markdown SnapForge URL to Markdown ~146
Extract a clean Markdown version of a public URL or raw HTML (article extraction + HTML→Markdown). Great for feeding live web content to an LLM. Requires a SnapForge API key (no key? call snapforge_signup first).
| Name | Type | Req | Description |
|---|---|---|---|
| delay | integer | – | Extra wait in milliseconds before capture (0–10000) |
| html | string | – | Raw HTML to render instead of a URL (max 2MB). Provide either url or html. |
| url | string | – | Public http/https URL to render. Provide either url or html. |
| waitUntil | string | – | When to consider the page ready: "load" (default) or "networkidle" |
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | yes | The extracted Markdown content |
No examples provided.
snapforge_pdf SnapForge PDF ~219
Render a public URL or raw HTML to a PDF (returned as an embedded resource). Requires a SnapForge API key (no key? call snapforge_signup first).
| Name | Type | Req | Description |
|---|---|---|---|
| delay | integer | – | Extra wait in milliseconds before capture (0–10000) |
| html | string | – | Raw HTML to render instead of a URL (max 2MB). Provide either url or html. |
| landscape | boolean | – | Landscape orientation (default false) |
| margin | string | – | CSS size applied to all margins, e.g. "1cm" |
| pageFormat | string | – | Paper size when paginating (default A4) |
| printBackground | boolean | – | Include CSS background colors and images (default true) |
| singlePage | boolean | – | Output one continuous page sized to the content height (no A4 pagination) |
| url | string | – | Public http/https URL to render. Provide either url or html. |
| waitUntil | string | – | When to consider the page ready: "load" (default) or "networkidle" |
| Name | Type | Req | Description |
|---|---|---|---|
| bytes | integer | yes | Size of the generated PDF in bytes |
| mimeType | string | yes | Always application/pdf |
No examples provided.
snapforge_screenshot SnapForge screenshot ~246
Capture a screenshot of a public URL or raw HTML as a PNG/JPEG image. Full-page by default. Requires a SnapForge API key (no key? call snapforge_signup first).
| Name | Type | Req | Description |
|---|---|---|---|
| delay | integer | – | Extra wait in milliseconds before capture (0–10000) |
| format | string | – | Image format: "png" (default) or "jpeg" |
| fullPage | boolean | – | Capture the full scrollable page (default true) |
| height | integer | – | Viewport height in pixels (100–2160) |
| html | string | – | Raw HTML to render instead of a URL (max 2MB). Provide either url or html. |
| quality | integer | – | JPEG quality 1–100 (ignored for PNG) |
| scale | integer | – | Device pixel ratio for high-DPI/retina output (1–3) |
| url | string | – | Public http/https URL to render. Provide either url or html. |
| waitUntil | string | – | When to consider the page ready: "load" (default) or "networkidle" |
| width | integer | – | Viewport width in pixels (100–3840) |
| Name | Type | Req | Description |
|---|---|---|---|
| bytes | integer | yes | Size of the returned image in bytes |
| mimeType | string | yes | Image MIME type, e.g. image/png |
No examples provided.
snapforge_signup SnapForge signup (free API key) ~89
Create a free SnapForge account (100 renders, one-time free trial, not a monthly allowance) with just an email address and get the API key instantly. The key is bound to the current MCP session, so the screenshot/pdf/markdown tools work immediately after signup, no browser needed.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address to attach the API key to (the key is also emailed there) |
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | yes | Your SnapForge API key |
| monthlyQuota | integer | yes | Renders included: 100 in total on the free trial (no monthly reset), per month on paid plans |
| plan | string | yes | Plan name (free) |
No examples provided.
How do I install the org.snapforge/snapforge MCP server?
org.snapforge/snapforge is a hosted endpoint at https://snapforge.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · snapforge.org
claude mcp add --transport http org-snapforge-snapforge 'https://snapforge.org/mcp'
What is the org.snapforge/snapforge MCP server?
org.snapforge/snapforge is an MCP server listed in the public MCP registry as org.snapforge/snapforge. Screenshots, PDFs and Markdown from any URL or HTML for AI agents, via the SnapForge API. This page covers its hosted endpoint (https://snapforge.org/mcp).
Is the org.snapforge/snapforge MCP server safe to use?
org.snapforge/snapforge scores 87 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the org.snapforge/snapforge MCP server expose?
org.snapforge/snapforge exposes 4 tools: snapforge_screenshot, snapforge_pdf, snapforge_markdown, snapforge_signup. Their descriptions and schemas cost roughly 700 tokens of context every time the server is loaded.
Does the org.snapforge/snapforge MCP server require authentication?
No. We connected to org.snapforge/snapforge without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the org.snapforge/snapforge MCP server still maintained?
org.snapforge/snapforge is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the org.snapforge/snapforge MCP server?
VerifyMCP ran 13 checks on org.snapforge/snapforge, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.