"JavaScript" matching MCP connectors:

GrabbitA

live.grabbit

Grabbit gives AI agents eyes on the web through a hosted MCP server. Send a public URL and get a pixel-perfect hosted image back, without maintaining Chromium, Playwright, or a browser fleet. Capture a full page, exact viewport, or single CSS selector as PNG, JPEG, or WebP. Grabbit handles cookie and consent banners, waits for JavaScript-heavy pages, blocks private and internal URLs, supports safe retries with idempotency keys, and delivers async results through signed webhooks. Completed captures include a CDN URL. Connect with OAuth 2.1 or an API key. Grabbit works with Claude, Cursor, Codex, and any MCP client. Live captures cost $0.002 each. The $50 annual plan includes 25,000 prepaid credits that never reset or expire. Free test keys return placeholder images, so you can wire up the integration before paying. Home: https://grabbit.live Docs: https://grabbit.live/screenshot-api Built by BrainGrid.

ScrapingBeeA

com.scrapingbee.mcp

Fetch any web page as text, markdown, HTML or a screenshot — JavaScript, CAPTCHAs and anti-bot blocking handled — and extract structured data; JSON tools for Google, Amazon, Walmart, YouTube, ChatGPT and Gemini.

Web data for AI agents. Spicrawl MCP lets agents fetch public web pages as clean Markdown, HTML, text, screenshots, PDFs, or structured JSON. It handles JavaScript-heavy pages and browser actions like clicking, filling forms, and scrolling.

URLpipeA

dev.urlpipe

Read any page after its JavaScript runs: Markdown, screenshots, metadata, console errors and Lighthouse audits.

Lekta — AEO/GEO Audit for AI Answer EnginesA

dev.lekta

**Can AI actually read your page?** ChatGPT, Perplexity, Claude and Google's AI Overviews fetch pages very differently from your browser — no JavaScript, tight timeouts, and a robots.txt rulebook of their own. Lekta fetches a URL exactly the way they do and grades what survives, **A+ to F**. This is the technical half of **AEO** (answer engine optimization) and **GEO** (generative engine optimization): before a model can cite you, it has to be able to fetch you, parse you, and find one sentence worth quoting. **The loop this server was built for:** `Audit https://mysite.com/pricing with Lekta, apply the fixes it lists, audit it again, and show me the difference.` Your agent gets a graded verdict, a ranked fix plan with the exact markup to paste, and a diff that proves the change landed. Repeat until A+. **Four layers, 100 points:** **Access** 25 — do the ~17 AI crawler tokens get past robots.txt? **Indexability** 25 — how much content survives without JavaScript? **Answerability** 30 — is there a single quotable sentence an engine can lift? **Recency** 20 — can a model tell when this page was last true? **What this is not:** a rank tracker. Lekta will not tell you how often ChatGPT mentions your brand. It tells you whether your page can be read and quoted when it does — the part you can actually fix. **No black box.** Every finding cites its basis — an RFC, a vendor doc, or a dated measurement we ran. The engine is versioned with a public changelog: a score never moves without a published shift table. **Tools:** `lekta_audit` (fresh fetch) · `lekta_report` (cached read) · `lekta_fix_plan` (ranked, paste-ready) · `lekta_diff` (before/after) · `lekta_my_sites` Listing tools is open. Tool calls need a free key from lekta.dev/en/panel/api — send `Authorization: Bearer lekta_…` or `x-api-key`. Cached reads, fix plans and diffs cost nothing; only fresh fetches count against the daily limit. **Topics:** AEO · GEO · AI SEO · LLM SEO · answer engine optimization · generative engine optimization · AI crawler access (GPTBot, ClaudeBot, PerplexityBot, Google-Extended) · JavaScript-free indexability · structured data · content freshness