Screenshotline
REMOTE · API.SCREENSHOTLINE.COM · SCANNED SEP 20
Screenshot any web page, or read it as clean Markdown, with consent banners, ads and popups removed.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 440 tokens (~220/item across 2 items; 2 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 Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
How do I install the Screenshotline MCP server?
Screenshotline is a hosted endpoint at https://api.screenshotline.com/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 · api.screenshotline.com
claude mcp add --transport http mamubeenkhan-screenshotline 'https://api.screenshotline.com/mcp'
{
"mcpServers": {
"mamubeenkhan-screenshotline": {
"url": "https://api.screenshotline.com/mcp"
}
}
} {
"servers": {
"mamubeenkhan-screenshotline": {
"type": "http",
"url": "https://api.screenshotline.com/mcp"
}
}
} [mcp_servers.mamubeenkhan-screenshotline] url = "https://api.screenshotline.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mamubeenkhan-screenshotline": {
"type": "remote",
"url": "https://api.screenshotline.com/mcp",
"enabled": true
}
}
} openclaw mcp add mamubeenkhan-screenshotline --url 'https://api.screenshotline.com/mcp' --transport streamable-http
mcp_servers:
mamubeenkhan-screenshotline:
url: "https://api.screenshotline.com/mcp" {
"McpServers": {
"mamubeenkhan-screenshotline": {
"Transport": "http",
"Url": "https://api.screenshotline.com/mcp"
}
}
} assistant mcp add mamubeenkhan-screenshotline -t streamable-http -u 'https://api.screenshotline.com/mcp'
{
"mcpServers": {
"mamubeenkhan-screenshotline": {
"type": "http",
"url": "https://api.screenshotline.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 11 Sept 26 66
First indexed and scored.
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 20 Sept 2026 · Probed https://api.screenshotline.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.screenshotline.com | CN=YE2,O=Let's Encrypt,C=US | 9 Sept 2026 | 8 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 534e62749149f3e0741c4841acc9a22ad79 |
| SANs: api.screenshotline.com | ||||||
| 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 api.screenshotline.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| screenshotline.com. | absent | 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; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.screenshotline.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.screenshotline.com/mcp | HTTPS enforced | 308 | https://api.screenshotline.com/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 →
read_page ~198
Render a web page and return its content as clean Markdown. The page is fully rendered first - JavaScript executed, consent banners dismissed, lazy images loaded - so this works on sites that return nothing useful to a plain HTTP fetch. Prefer this over screenshot when you need to read or reason about the text.
| Name | Type | Req | Description |
|---|---|---|---|
| block_chats | boolean | – | Remove live-chat widgets. Default true. |
| block_cookie_banners | boolean | – | Remove consent banners. Default true. |
| block_popups | boolean | – | Remove newsletter and donation interstitials. Default true. |
| max_chars | number | – | Truncate the Markdown to this many characters. 0 or omitted means no limit. |
| strip_chrome | boolean | – | Drop navigation, headers, footers and sidebars, keeping the main content. Default true. Set false for a full transcript of the page. |
| url | string | yes | The page to read. Must be http or https. |
No output schema declared.
No examples provided.
screenshot ~242
Capture a screenshot of a web page and return it as an image. Handles consent banners, ads, lazy-loaded images and late-rendering SPAs. Use this when the layout, styling or visual appearance is what matters; use read_page when you only need the text.
| Name | Type | Req | Description |
|---|---|---|---|
| block_ads | boolean | – | Block ad networks and collapse the empty slots. Default true. |
| block_chats | boolean | – | Remove live-chat widgets. Default true. |
| block_cookie_banners | boolean | – | Remove consent banners. Default true. |
| block_popups | boolean | – | Remove newsletter and donation interstitials. Default true. |
| color_scheme | string | – | Render the page in light or dark mode. |
| format | string | – | Default png. |
| full_page | boolean | – | Capture the entire scrollable page rather than just the viewport. |
| selector | string | – | Capture only the element matching this CSS selector. |
| url | string | yes | The page to capture. Must be http or https. |
| viewport_height | number | – | Viewport height in pixels. Default 800. |
| viewport_width | number | – | Viewport width in pixels. Default 1280. |
No output schema declared.
No examples provided.
What is the Screenshotline MCP server?
Screenshotline is an MCP server listed in the public MCP registry as io.github.MAMubeenKhan/screenshotline. Screenshot any web page, or read it as clean Markdown, with consent banners, ads and popups removed. This page covers its hosted endpoint (https://api.screenshotline.com/mcp).
Is the Screenshotline MCP server safe to use?
Screenshotline scores 71 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 Screenshotline MCP server expose?
Screenshotline exposes 2 tools: screenshot, read_page. Their descriptions and schemas cost roughly 440 tokens of context every time the server is loaded.
Does the Screenshotline MCP server require authentication?
No. We connected to Screenshotline without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Screenshotline MCP server still maintained?
Screenshotline is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.