localscreenshot MCP Server (Free)
https://api.localscreenshot.com
Registry code: ca2f482b125a056a
localscreenshot takes screenshots of public web pages for AI agents, from 227 countries.
This is the free endpoint. It needs no key and it does not capture a page of your choice. It has three read-only tools:
- endpoint
- https://api.localscreenshot.com/mcp/free
- protocol
- streamable-http ·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 localscreenshot MCP Server (Free) live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is localscreenshot MCP Server (Free) free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does localscreenshot MCP Server (Free) have?
- 3 tools: take_demo_screenshot, list_countries, get_pricing.
- Is localscreenshot MCP Server (Free) 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 100%· all time 100%
last good check
of 3 tools
- unknown → live
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.
list_countries open 1h ago
List the countries a screenshot can be taken from, with their two-letter codes. Choosing a country needs an account: this free endpoint only lists them.
{ "type": "object", "properties": {} }arguments 4 linesget_pricing open 1h ago
What localscreenshot costs: the free credits every account gets each month, the limits of a free account, what a screenshot costs in credits, and where paid plans and credit packs start.
{ "type": "object", "properties": {} }arguments 4 linestake_demo_screenshot unknown 1h ago
See what a localscreenshot result looks like: a real screenshot of one of our example pages. It does not capture a page of your choice. For that, create a free account and use the main MCP server with an API key.
{ "type": "object", "required": [ "page" ], "properties": { "page": { "enum": [ "guardian", "wikipedia", "hackernews" ], "type": "string", "description": "Which example page to capture." }, "device": { "enum": [ "desktop", "phone" ], "type": "string", "description": "Screen to render it on. Default: desktop." } } }arguments 25 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 idca2f482b125a056a.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/ca2f482b125a056a/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/ca2f482b125a056a?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.