KitScout

Categories › Web & Browser › Scraping, crawling & page-to-text

URLpipe

MCP serverVerified domain · urlpipe.devRemote● LiveAPI key needed

Read any page with its JavaScript run: Markdown, screenshots, metadata, console errors, Lighthouse.

Install

Remote server: your requests and data go to urlpipe.dev. Claude Code: claude mcp add --transport http urlpipe https://urlpipe.dev/mcp · Claude app: Settings → Connectors → Add custom connector.

What it can do

The tools this server listed when we connected to it, in its own words.

  • list_projects — The projects this token can reach, each with how many requests it has made in the last 30 days and where its results are delivered. Start he
  • get_usage — What the organization's plan allows, how much of it is left this period, and what each operation costs. Worth reading before a run of expens
  • fetch_markdown — Exposes POST /markdown. Renders the page in headless Chrome and converts its main content to clean Markdown — headings, lists, links and cod
  • fetch_html — Exposes POST /html. Returns the page's HTML after JavaScript has run and redirects have been followed — the DOM a real browser sees, not the
  • capture_screenshot — Exposes POST /screenshot. Captures the whole rendered page as a PNG — JavaScript executed, web fonts and images included, exactly as a brows
  • capture_pdf — Exposes POST /pdf. Prints the whole rendered page to a PDF — JavaScript executed, web fonts and lazy-loaded images included, its headings as
  • capture_console_errors — Exposes POST /console. Loads the page in headless Chrome and returns what it reported through console.error and console.warn during load, pl
  • run_lighthouse_audit — Exposes POST /lighthouse. Runs a real Google Lighthouse audit against the live page: performance, accessibility, best-practices and SEO scor
  • extract_metadata — Exposes POST /meta. Reads everything a page declares about itself — Open Graph, Twitter cards, meta tags, JSON-LD, microdata and links — int
  • detect_technologies — Exposes POST /technologies. Detects what a page is built with — CMS, e-commerce platform, JavaScript frameworks and libraries, analytics and
  • extract_keywords — Exposes POST /keywords. Returns the 5–15 terms and phrases that best represent the page, ordered by relevance — ranked by a language model,
  • summarize_page — Exposes POST /summarize. Returns a concise Markdown summary of the page's main content, with the navigation, ads and boilerplate left out. T
  • extract_data — Exposes POST /extract. Reads the page and fills an object YOU define: pass `fields`, each with a name, a type and a description of what to t
  • scrape_url — Exposes POST /scrape. Runs any subset of the other operations in one request, served from a single page visit where possible. Each operation
  • get_result — Exposes GET /result/:token. Returns the result of a past request, in the same form the call that made it would have returned — Markdown as M
  • list_requests — A project's recent requests, newest first, with each one's token. Look here before fetching a page: if somebody already pulled it, passing t
  • get_request — Everything about one past request except its result: what was asked for, how long each stage took, whether it came from the store, and how t

KitScout test notes

Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.

Similar tools