timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Clean full-page screenshots of real sites: cookie banners, pop-ups, chat widgets and ads removed.
Skills that teach the AI this kind of work; they work alongside this one
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…
scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 12/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install API Screenshot. Follow https://mcp.popnx.com/i/matbrons-api-screenshot.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · What you ask goes through the maker’s server ({host}) · ✓ Commands checked Nov 16, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
You need a API Screenshot key (create it on the maker’s site) · The address has {…} parts you must replace with your own first · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
CustomizeConnectors
Copy each value into the field with the same name in Claude, then click Continue
API Screenshothttps://{host}/mcpUnder Request headers, add this name and value
AuthorizationBearer <paste your key here>Paste the key only into the app’s field, never into a chat or to anyone
Click Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add
+ConnectorsAPI Screenshot
Use API Screenshot and tell me what you can do for me, then show me one thing✓ If Claude says it is using API Screenshot or shows a API Screenshot tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect API Screenshot yet
API Screenshot needs your own key to connect, but OpenAI’s help page only describes OAuth sign-in; there is no key option we could verify
A · Use an app that can connect API Screenshot
B · Others in Web & browsers that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
You need a API Screenshot key (create it on the maker’s site) · The address has {…} parts you must replace with your own first
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --transport http --scope user api-screenshot 'https://{host}/mcp' --header 'Authorization: Bearer {api_key}'Replace “your-value” with your key before pressing Enter
Paste the key only into the app’s field, never into a chat or to anyone
You should see API Screenshot listed as connected
Use API Screenshot and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using API Screenshot or shows a API Screenshot tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
You need a API Screenshot key (create it on the maker’s site) · The address has {…} parts you must replace with your own first
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
~/.cursor/mcp.json
Paste these settings, fill in the empty values and save
{
"mcpServers": {
"api-screenshot": {
"url": "https://{host}/mcp",
"headers": {
"Authorization": "Bearer {api_key}"
}
}
}
}In the API Screenshot settings, Authorization is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use API Screenshot and tell me what you can do for me, then show me one thing✓ If Cursor says it is using API Screenshot or shows a API Screenshot tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
You need a API Screenshot key (create it on the maker’s site) · The address has {…} parts you must replace with your own first
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
MCP: Open User Configuration
Paste these settings, fill in the empty values and save
{
"servers": {
"api-screenshot": {
"type": "http",
"url": "https://{host}/mcp",
"headers": {
"Authorization": "Bearer {api_key}"
}
}
}
}In the API Screenshot settings, Authorization is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use API Screenshot and tell me what you can do for me, then show me one thing✓ If VS Code says it is using API Screenshot or shows a API Screenshot tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
Address for apps that connect over the web
https://{host}/mcpJSON settings are under “For developers” below
Claude Code
claude mcp add --transport http --scope user api-screenshot 'https://{host}/mcp' --header 'Authorization: Bearer {api_key}'Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"api-screenshot": {
"url": "https://{host}/mcp",
"headers": {
"Authorization": "Bearer {api_key}"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"api-screenshot": {
"type": "http",
"url": "https://{host}/mcp",
"headers": {
"Authorization": "Bearer {api_key}"
}
}
}
}Claude Code
claude mcp add --scope user api-screenshot --env API_KEY=your-value -- docker run -i --rm -e API_KEY ghcr.io/matbrons/api-screenshot:0.1.2Claude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"api-screenshot": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"API_KEY",
"ghcr.io/matbrons/api-screenshot:0.1.2"
],
"env": {
"API_KEY": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"api-screenshot": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"API_KEY",
"ghcr.io/matbrons/api-screenshot:0.1.2"
],
"env": {
"API_KEY": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"api-screenshot": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"API_KEY",
"ghcr.io/matbrons/api-screenshot:0.1.2"
],
"env": {
"API_KEY": "your-value"
}
}
}
}API_KEY secret required envPORT envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
oci: ghcr.io/matbrons/api-screenshot:0.1.2Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
The address needs your own values, so we cannot read the tool list for you.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account matbrons, which owns the repo
Code last changed 3 days ago
Uses MIT
The address needs your own account values, so we cannot check it for you
The address needs your own account values, so we cannot check it for you
Not checked yet; we read the tool list when we check the endpoint
Not checked: only npm and PyPI packages with a version can be checked
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/matbrons-api-screenshot)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: Authorization, API_KEY
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed 3 days ago, and the latest version (0.1.2) reached the registry 3 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).
In the same category: Browser Use, changedetection.io (official), Apify MCP Server, Pomerado, Actionbook
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Official changedetection.io MCP: web page change tracking, back-in-stock and price alerts.
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡
Connect your agents to any website. The cheaper, faster and more reliable alternative to browser use
Let your AI agent operate any website through a real, logged-in browser session.
| This one API Screenshot | Browser Use | changedetection.io (official) | Apify MCP Server | Pomerado | Actionbook | |
|---|---|---|---|---|---|---|
| Runs where | Cloud or install on your computer | Cloud or install on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | Yes | Yes | No | Yes | No | No |
| Add with + in Claude | No | Yes | No | No | No | No |
| Basic checks | 3/3 | 5/5 | 3/3 | 4/4 | 4/4 | 4/4 |
| License | MIT | MIT | Apache-2.0 | MIT | MIT | Apache-2.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A screenshot API you run yourself. It takes full-page shots of real sites with the cookie banners, pop-ups, chat widgets and ads removed. It runs on your own Cloudflare account or on any server with Docker.
Examples and docs: apiscreenshot.com. Measured: how many shots Cloudflare's free plan gives and what a server needs to run it.
curl -H "Authorization: Bearer $API_KEY" \
"https://api-screenshot.your-subdomain.workers.dev/screenshot?url=https://www.theguardian.com&full_page=true" -o shot.png
Contents: Run it (Cloudflare, your own server, safe by default) · Use it (JSON, signed URLs, caching, options, errors) · Use it from an AI agent · Settings · Ads, trackers and filter lists · Sites that block bots (retries) · Safety · Limits · Develop
The button asks you to sign in to Cloudflare and connect GitHub, then copies this repo to your GitHub account and deploys it to your Cloudflare account. It asks for one secret, API_KEY: paste a long random string, for example from openssl rand -hex 32, and keep it. Your API is then at https://api-screenshot. .workers.dev.
Or from a clone:
git clone https://github.com/matbrons/api-screenshot && cd api-screenshot
npm install npx wrangler login npx wrangler deploy API_KEY=$(openssl rand -hex 32); echo "Your API key: $API_KEY" echo "$API_KEY" | npx wrangler secret put API_KEY
On a new account, the first deploy asks you to pick your workers.dev subdomain. It also creates the KV namespace for the cache and writes its id into wrangler.jsonc, so that file shows as changed afterwards; keep the change. To check it all works (this takes one real shot):
APISHOT_TEST_URL=https://api-screenshot.<your-subdomain>.workers.dev APISHOT_TEST_KEY=$API_KEY ops/watch.sh
It uses Browser Rendering, which the free Workers plan includes with a daily limit (see Limits).
API_KEY=$(openssl rand -hex 32); echo "Your API key: $API_KEY"
docker run -d --restart unless-stopped -p 3000:3000 -e API_KEY="$API_KEY" ghcr.io/matbrons/api-screenshot
The image runs on amd64 and arm64. It is published when a version is tagged, so it appears after the first release. To build it yourself instead: docker build -t api-screenshot .
Or without Docker, with Node 22.19 or newer and Chrome or Chromium installed:
npm install
API_KEY=$(openssl rand -hex 32); echo "Your API key: $API_KEY" API_KEY="$API_KEY" HOST=127.0.0.1 npm start
It finds Chrome or Chromium on its own; set CHROME_PATH if it doesn't. HOST=127.0.0.1 keeps it to your own machine; leave it out on a server, where it listens on every address.
The server path uses a real Chromium. Whether it gets past more bot walls than the Worker depends mostly on your server's IP address: see Sites that block bots.
A screenshot API on a public URL lets anyone spend your browser time. So until API_KEY (or SIGNING_SECRET, for signed URLs) is set, every screenshot request is refused with not_configured, and so is a key shorter than 16 characters or one copied from an example. If you really want it open, for example on a private network, set ALLOW_PUBLIC_ACCESS=true.
# GET with query options
curl -H "Authorization: Bearer $API_KEY" \ "http://localhost:3000/screenshot?url=https://example.com&full_page=true&format=jpeg" -o shot.jpg
curl -X POST http://localhost:3000/screenshot \ -H "Authorization: Bearer $API_KEY" -H "content-type: application/json" \ -d '{"url": "https://example.com", "viewport_width": 390, "viewport_mobile": true}' -o shot.png
The key can also go in an X-API-Key header. It is never taken from the URL, where it would end up in logs and browser history: a request with access_key in the query is refused. To put a shot in an tag or a link, use a signed URL.
A shot comes back as the image (or PDF) itself, with these headers:
| Header | Value |
|---|---|
x-final-url | The URL after redirects |
x-target-status | The HTTP status the site answered with |
x-removed-elements | How many things were removed from the shot: the cookie banner, whether it was answered or hidden, plus each pop-up, backdrop, chat widget or ad that was showing. A banner and its own parts count as one. 0 when there was nothing to remove. |
x-consent-manager | The consent tool behind the cookie banner that was removed (see below). Not sent when no banner was removed. |
x-page-height | The page's full height in CSS pixels |
x-truncated | true when the shot was cut off: the page (or the selector element) was taller than full_page_max_height, or than 16384 device pixels (see Limits) |
x-cache | HIT when the shot came from the cache, MISS when it was taken now and kept, BYPASS when the cache wasn't read (fresh, or caching off). See Caching. |
age | On a HIT: seconds since the shot was taken |
x-overlay-remaining | cookie_banner or popup when one is still on screen in the shot, after every attempt to remove it. Not sent when the shot is clean. |
x-consent-manager is one of:
OneTrust, Cookiebot, Didomi, Usercentrics, Sourcepoint, TrustArc, Quantcast, consentmanager, CookieYes, Complianz, iubenda, Osano, Shopify and others.airbnb).generic: a banner recognised by its look and words, not by a known tool.Before the shot, a last check looks for a cookie banner or pop-up that is still covering part of the screen. If it finds one, it presses Escape, then the banner's reject or close button (never accept), and cleans up again. One that survives all that is left in the shot and named in x-overlay-remaining, so you can retry or flag it. A site's own sticky header or menu doesn't count, even when it has a "Sign up" link.
With response_type=json the answer is JSON instead of the file: the page's details plus the image or PDF in base64. response_type=metadata gives the details alone and skips the shot, which is quicker.
{
"url": "https://example.com/", "final_url": "https://example.com/", "status": 200, "title": "Example Domain", "description": null, "icon": "https://example.com/favicon.ico", "open_graph": { "title": "...", "image": "https://..." }, "page_height": 800, "removed_elements": 0, "consent_manager": null, "overlay_remaining": null, "truncated": false, "content_type": "image/png", "size": 18734, "image": "iVBORw0KGgo..." }
open_graph holds the page's og: tags without the prefix. icon is the page's own icon link, or /favicon.ico when it has none (which may not exist).
To put a shot straight into an or og:image tag without giving away your key, sign the URL instead. Set a second secret, SIGNING_SECRET (16 characters or more, for example from openssl rand -hex 32; on Cloudflare echo "$SIGNING_SECRET" | npx wrangler secret put SIGNING_SECRET, or add it under the Worker's settings), then add a signature to each URL:
expires if you want the link to stop working at some point (a Unix time in seconds).A-Z a-z 0-9 - _ . ~) and join them as name=value&name=value.signature is the HMAC-SHA256 of that string with SIGNING_SECRET, in hex.Anyone can read a signed URL, but changing, adding or removing any parameter breaks it. A wrong signature gets unauthorized with reason: signature_invalid, an expired one reason: signature_expired. Only GET requests can be signed. Make signed URLs on your server, never in the browser, so the secret stays with you.
In Node.js:
import { createHmac } from 'node:crypto';
const encode = (s) => encodeURIComponent(s).replace(/[!'()*]/g, (c) => %${c.charCodeAt(0).toString(16).toUpperCase()});
function signedUrl(base, options, secret) { const query = Object.keys(options).sort() .map((name) => ${encode(name)}=${encode(String(options[name]))}) .join('&'); const signature = createHmac('sha256', secret).update(query).digest('hex'); return ${base}/screenshot?${query}&signature=${signature}; }
signedUrl('https://api-screenshot.your-subdomain.workers.dev', { url: 'https://example.com', full_page: true, expires: Math.floor(Date.now() / 1000) + 7 * 24 * 3600, // optional: valid for a week }, process.env.SIGNING_SECRET);
In a shell, with the query already sorted and encoded:
QUERY='full_page=true&url=https%3A%2F%2Fexample.com'
SIG=$(printf '%s' "$QUERY" | openssl dgst -sha256 -hmac "$SIGNING_SECRET" -r | cut -d' ' -f1) echo "https://api-screenshot.your-subdomain.workers.dev/screenshot?$QUERY&signature=$SIG"
With only SIGNING_SECRET set and no API_KEY, the API takes signed URLs and nothing else.
A finished shot is kept for a day, so the same request again comes back at once and costs no browser time. Requests count as the same when their options are, after defaults are filled in: url=example.com and url=https://example.com/ share one shot. Only real shots are kept. A blocked, blank or any other error is never cached, so the next request tries again.
The cache is checked after the key or signature, so a cached shot never goes to someone who couldn't have asked for it. The x-cache header says whether a shot came from the cache. cache-control tells browsers how long they may keep it too: private for requests with the key, public for signed URLs (never past their expires), so a CDN in front can serve them.
On Cloudflare, shots are kept in Workers KV; the deploy creates the namespace for you. On a server they are kept in a folder, CACHE_DIR, up to CACHE_MAX_MB, and the shots used longest ago make room for new ones. In Docker that folder is /var/cache/api-screenshot; add -v api-screenshot-cache:/var/cache/api-screenshot to docker run to keep the shots when the container is replaced.
Option names match the ones common to hosted screenshot APIs, so most requests written for one of those work here unchanged. An unknown option is refused, so a typo doesn't fail silently.
| Option | Default | What it does |
|---|---|---|
url | required | The page to shoot. https:// is added when missing. |
| html | | Markup to