screenshotrender
https://www.screenshotrender.com
Registry code: fe9df05acdb2a613
Take screenshots of any public website from Claude, Cursor, ChatGPT, or any MCP client. The take_screenshot tool renders a URL and returns the image inline, plus a hosted link and the page title and description. It supports full-page capture, a wait delay before capturing, and a timeout. You bring your own ScreenshotRender API key (starts with sr-), available at screenshotrender.com
from a public catalogue that lists it, not from the operator
- endpoint
- https://www.screenshotrender.com/api/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is screenshotrender live?
- Yes — it answered the hub's last check (checked 7h ago). It answered 99% of checks over the last 30 days.
- Is screenshotrender free to use?
- Not measured yet.
- What tools does screenshotrender have?
- 1 tool: take_screenshot.
- Is screenshotrender safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99%· all time 99%
last good check
of 1 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- topic
- search & web scraping & fetch
- used for
- take a screenshot of a website
- capture a full-page screenshot
- takes → gives
- text → images
- tools
- 1 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
take_screenshot reads unknown never probed
Capture a screenshot of any public website using ScreenshotRender. Returns the rendered image inline plus a hosted URL and basic page metadata (title, description). Use this whenever the user wants to see, save, or share what a web page looks like.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "url" ], "properties": { "url": { "type": "string", "description": "The URL of the page to screenshot. Include the scheme (https://). Example: https://stripe.com" }, "wait": { "type": "integer", "maximum": 30000, "minimum": 0, "description": "Milliseconds to wait after load before capturing, for pages with animations or lazy content." }, "timeout": { "type": "integer", "maximum": 60000, "minimum": 1000, "description": "Maximum milliseconds to wait for the page to load." }, "fullPage": { "type": "boolean", "description": "Capture the entire scrollable page instead of just the 1280x720 viewport. Defaults to false (or the connection default)." } } }arguments 29 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idfe9df05acdb2a613.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/fe9df05acdb2a613/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/fe9df05acdb2a613?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.