URLpipe

Name: URLpipe
Author: dev.urlpipe

MCP serverMCP

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

by dev.urlpiperepository ↗homepage ↗v1.2.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"urlpipe","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability53/53 checks ok

when	check	result	http	latency	detail
6 h ago	mcp initialize	ok	200	153 ms	server urlpipe 1.3.0 · protocol 2025-06-18 · 14 tools
12 h ago	mcp initialize	ok	200	90 ms	server urlpipe 1.3.0 · protocol 2025-06-18 · 14 tools
18 h ago	mcp initialize	ok	200	87 ms	server urlpipe 1.3.0 · protocol 2025-06-18 · 14 tools
24 h ago	mcp initialize	ok	200	66 ms	server urlpipe 1.3.0 · protocol 2025-06-18 · 14 tools
30 h ago	mcp initialize	ok	200	188 ms	server urlpipe 1.3.0 · protocol 2025-06-18 · 14 tools
2 d ago	mcp initialize	ok	200	84 ms	server urlpipe 1.3.0 · protocol 2025-06-18 · 14 tools
2 d ago	mcp initialize	ok	200	39 ms	server urlpipe 1.3.0 · protocol 2025-06-18 · 14 tools
2 d ago	mcp initialize	ok	200	89 ms	server urlpipe 1.3.0 · protocol 2025-06-18 · 14 tools
2 d ago	mcp initialize	ok	200	100 ms	server urlpipe 1.3.0 · protocol 2025-06-18 · 14 tools
3 d ago	mcp initialize	ok	200	66 ms	server urlpipe 1.3.0 · protocol 2025-06-18 · 14 tools

Tools observed via MCP handshake

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 here: every other too
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 expensive calls: the oper
fetch_markdown — Exposes POST /markdown. Renders the page in headless Chrome and converts its main content to clean Markdown — headings, lists, links and code kept, navigation,
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 empty shell curl re
capture_screenshot — Exposes POST /screenshot. Captures the whole rendered page as a PNG — JavaScript executed, web fonts and images included, exactly as a browser would draw it. 1
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, plus uncaught exceptio
run_lighthouse_audit — Exposes POST /lighthouse. Runs a real Google Lighthouse audit against the live page: performance, accessibility, best-practices and SEO scores plus Core Web Vit
extract_metadata — Exposes POST /meta. Reads everything a page declares about itself — Open Graph, Twitter cards, meta tags, JSON-LD, microdata and links — into one object with th
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, not by raw frequency
summarize_page — Exposes POST /summarize. Returns a concise Markdown summary of the page's main content, with the navigation, ads and boilerplate left out. The most expensive o
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 is billed and store
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 Markdown, a structure
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 that token to get_re
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 the webhook delivery

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrydev.urlpipe/mcp

first seen 14 d ago · fetched 11 h agoopen ↗

Field history (7 recent events)

14 d ago · declared · summary → "Read any page with its JavaScript run: Markdown, screenshots, metadata, console errors, Lighthouse."
14 d ago · declared · description → "Read any page with its JavaScript run: Markdown, screenshots, metadata, console errors, Lighthouse."
14 d ago · declared · publisherName → "dev.urlpipe"
14 d ago · declared · homepageUrl → "https://urlpipe.dev/mcp-server"
14 d ago · declared · repoUrl → "https://github.com/URLpipe/mcp"
14 d ago · declared · version → "1.2.0"
14 d ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from