Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Framejet Screenshot

REMOTE · FRAMEJET.DEV

Clean PNG/JPEG screenshots via REST or MCP, with goal-driven multi-step navigation.

Available components

0 this week 25 Trust /100

Last scanned (21 hours ago)

Scores higher than 10% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Browser Automation

Trust breakdown (7 categories)

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 Security63
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Changelog

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.

  • 23 Oct 26 −53
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: 0.93 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list. functional
  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 57. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 50. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 4 Nov 2026 · Probed https://framejet.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.framejet.dev CN=YR1,O=Let's Encrypt,C=US 4 Sept 2026 3 Dec 2026 RSA 2048 SHA256-RSA 5d847b42b14db254e4b9148402fd3d42ad1
SANs: *.framejet.dev, framejet.dev
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of framejet.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
framejet.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 503
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://framejet.dev/mcp HTTP error 503
http (plaintext) http://framejet.dev/mcp HTTPS enforced 308 https://framejet.dev/mcp
MCP tools · 1 exposed · ~526 tokens

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 →

Tool Tokens
screenshot ~526

Render any public URL to a PNG or JPEG image. Cookie/consent banners and chat widgets are removed by default so the result is clean enough to reason about. Returns the image inline. For a page that is several clicks past the URL, pass `goal` in plain words and Framejet walks the flow before capturing — you do not need CSS selectors, and you could not write them anyway, because the controls for step 2 do not exist until step 1 has happened. Any text to be typed must be supplied in `values`; nothing is ever invented. If the goal cannot be reached the call fails and no credits are spent, so a returned image always means the goal was reached. On plans that price goals per block (10 credits a block, a screenshot is 1) `max_credits` is the most a goal may spend; it stops with goal_budget_exceeded rather than go past it. When you do know the page, `actions` is cheaper, faster and deterministic.

NameTypeReqDescription
actionsstring–Deterministic alternative to `goal` when you already know the page: ';'-separated steps, each verb:arg — click:<css>, type:<css>=<text>, waitfor:<css>, wait:<ms>, scroll:<px>. Prefer this over `goal`…
cleanboolean–Strip cookie banners / chat widgets, default true
delayinteger–Extra wait in ms after load
formatstring–Image format, default png
full_pageboolean–Capture the whole scroll height (default false)
goalstring–Plain-words description of the page state to reach before capturing, ending with when to stop. Example: 'Search for the Colosseum article, open it, then open its View history page. Stop when the revi…
heightinteger–Viewport height, default 800
max_credits––Most credits a `goal` may spend, default 10. The maximum is reserved while the goal runs and the unused part is released. Ignored on plans where a goal costs one credit.
urlstringyesThe http(s) page to capture
valuesarray–Exact strings a `goal` step may type into a field. Framejet picks among these and never invents text; if none fits, the capture fails.
widthinteger–Viewport width, default 1280

No output schema declared.

No examples provided.

Install

How do I install the Framejet Screenshot MCP server?

Framejet Screenshot is a hosted endpoint at https://framejet.dev/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 · framejet.dev

# add to Claude Code
claude mcp add --transport http dev-framejet-screenshot 'https://framejet.dev/mcp'
Common questions

What is the Framejet Screenshot MCP server?

Framejet Screenshot is an MCP server listed in the public MCP registry as dev.framejet/screenshot. Clean PNG/JPEG screenshots via REST or MCP, with goal-driven multi-step navigation. This page covers its hosted endpoint (https://framejet.dev/mcp).

Is the Framejet Screenshot MCP server safe to use?

Framejet Screenshot scores 25 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 Framejet Screenshot MCP server expose?

Framejet Screenshot exposes 1 tool: screenshot. Their descriptions and schemas cost roughly 526 tokens of context every time the server is loaded.

Does the Framejet Screenshot MCP server require authentication?

Its publisher declares that Framejet Screenshot requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.

Is the Framejet Screenshot MCP server still maintained?

Framejet Screenshot is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.