Read any page with its JavaScript run: Markdown, screenshots, metadata, console errors, Lighthouse.
MCPpedia last refreshed this data
dev.urlpipe/mcp is an MCP server that read any page with its JavaScript run: Markdown, screenshots, metadata, console errors, Lighthouse. Its tool list has not been published yet over http, requires no API key, and scores 69/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"urlpipe": {
"url": "https://urlpipe.dev/mcp",
"type": "http",
"headers": {
"Authorization": "Bearer ${URLPIPE_TOKEN}"
}
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Read any page with its JavaScript run: Markdown, screenshots, metadata, console errors, Lighthouse.
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in writing
Scrape, crawl, and map websites to Markdown or JSON via local CLI.
Create and edit PDFs: text, Markdown, tables, metadata and pages, with Japanese font embedding.
Any file → clean Markdown for AI agents: PDF, Office, EPUB, HTML, images, audio/video. Local MCP.
一键同步文章到多个内容平台,支持今日头条、WordPress、知乎、简书、掘金、CSDN、typecho各大平台,一次发布,多平台同步发布。解放个人生产力
MCP Security Weekly
Get CVE alerts and security updates for dev.urlpipe/mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Give your agent a browser that runs the page's JavaScript before it reads it.
Website ·
Docs ·
Pricing
A plain fetch tool does an HTTP GET. On a site that builds itself in the browser —
React, Vue, most docs sites and dashboards — that returns an empty shell, and the agent
either says it can't read the page or guesses what was on it.
URLpipe loads every page in real Chrome first, then hands your agent what it asked for: the page as Markdown, a screenshot it can look at, a PDF, its metadata, data in a schema you define, its console errors or a Lighthouse audit.
https://urlpipe.dev/mcp. Nothing to install or run.This repository holds the server's registry entry (server.json) and
the setup for each client. The server itself runs at urlpipe.dev.
Every client sends it as Authorization: Bearer YOUR_TOKEN.
claude mcp add --transport http urlpipe https://urlpipe.dev/mcp \
--scope user \
--header "Authorization: Bearer YOUR_TOKEN"
Or share it with your team in .mcp.json, each person setting their own URLPIPE_TOKEN:
{
"mcpServers": {
"urlpipe": {
"type": "http",
"url": "https://urlpipe.dev/mcp",
"headers": {
"Authorization": "Bearer ${URLPIPE_TOKEN}"
}
}
}
}
Where your organization has request headers in Customize → Connectors → Add custom
connector, add https://urlpipe.dev/mcp with No sign-in and an authorization
header of Bearer YOUR_TOKEN. Otherwise use the open-source
mcp-remote bridge in
claude_desktop_config.json (needs Node.js):
{
"mcpServers": {
"urlpipe": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://urlpipe.dev/mcp",
"--header",
"Authorization:${URLPIPE_AUTH}",
"--transport",
"http-only"
],
"env": {
"URLPIPE_AUTH": "Bearer YOUR_TOKEN"
}
}
}
}
~/.cursor/mcp.json, or .cursor/mcp.json in a project:
{
"mcpServers": {
"urlpipe": {
"url": "https://urlpipe.dev/mcp",
"headers": {
"Authorization": "Bearer ${env:URLPIPE_TOKEN}"
}
}
}
}
.vscode/mcp.json — VS Code asks for the token once and stores it securely:
{
"inputs": [
{
"type": "promptString",
"id": "urlpipe-token",
"description": "URLpipe MCP token",
"password": true
}
],
"servers": {
"urlpipe": {
"type": "h
... [View full README on GitHub](https://github.com/urlpipe/mcp#readme)