World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Give it a URL, get structured rows. A model writes the parser once; replays are free.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 4/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 24/100 |
质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 scrapewright。按照 https://mcp.popnx.com/i/ozymandias-owens-2-scrapewright.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(scrapewright.app) · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 5 分钟
需要 scrapewright 的密钥(在开发者网站创建) · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
scrapewrighthttps://scrapewright.app/mcp在 Request headers 下添加这个名称和值
X-API-Key<在这里粘贴你的密钥>只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+Connectorsscrapewright
用 scrapewright 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 scrapewright,或回答中出现 scrapewright 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 scrapewright
scrapewright 连接时需要你自己的密钥,但 OpenAI 帮助页面只说明了 OAuth 登录,没有我们能核实的填密钥方式
A · 使用能连接 scrapewright 的应用
B · 其他 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code · 约 5 分钟
需要 scrapewright 的密钥(在开发者网站创建)
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user scrapewright https://scrapewright.app/mcp --header 'X-API-Key: your-value'按 Enter 前,把“your-value”改成你的密钥
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
应能看到 scrapewright 在列表中并显示已连接
用 scrapewright 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 scrapewright,或回答中出现 scrapewright 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 5 分钟
需要 scrapewright 的密钥(在开发者网站创建)
在 scrapewright 的设置中,X-API-Key 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 scrapewright 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 scrapewright,或回答中出现 scrapewright 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 5 分钟
需要 scrapewright 的密钥(在开发者网站创建)
在 scrapewright 的设置中,X-API-Key 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 scrapewright 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 scrapewright,或回答中出现 scrapewright 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --transport http --scope user scrapewright https://scrapewright.app/mcp --header 'X-API-Key: your-value'Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"scrapewright": {
"url": "https://scrapewright.app/mcp",
"headers": {
"X-API-Key": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"scrapewright": {
"type": "http",
"url": "https://scrapewright.app/mcp",
"headers": {
"X-API-Key": "your-value"
}
}
}
}Claude Code
claude mcp add --scope user scrapewright --env ANTHROPIC_API_KEY=your-value -- uvx scrapewright mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"scrapewright": {
"command": "uvx",
"args": [
"scrapewright",
"mcp"
],
"env": {
"ANTHROPIC_API_KEY": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"scrapewright": {
"command": "uvx",
"args": [
"scrapewright",
"mcp"
],
"env": {
"ANTHROPIC_API_KEY": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"scrapewright": {
"type": "stdio",
"command": "uvx",
"args": [
"scrapewright",
"mcp"
],
"env": {
"ANTHROPIC_API_KEY": "your-value"
}
}
}
}ANTHROPIC_API_KEY 机密 必填 envSCRAPEWRIGHT_CACHE envSCRAPEWRIGHT_OBEY_ROBOTS env说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
工具名称和描述与服务器在 2026年11月19日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
detect_siteReport what platform a site runs on and which strategy to use. Cheap; call it before a large job.
extract_pageExtract structured data from ONE page. ``fields`` declares your own schema, e.g. ["title", "salary:number", "tags:list"]; omit it for the product schema. First call on a new site compiles a recipe (300 credits); later calls replay it for 1 credit per row. A site nobody could read
crawl_siteWalk a site and extract every item. Waits up to four minutes; a longer crawl returns a job_id to pass to crawl_status. `mode` picks how the items are found. "rows" (the default) reads every card on the listing itself and follows its pagination -- right for search results, categor
crawl_statusFetch a crawl that outlived its call.
accountCredits left and this month's usage for the key in use.
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 Ozymandias-Owens-2 验证,该账户拥有此仓库
代码最后更新于16天前
使用 MIT
在 353 毫秒内响应(HTTP 200)
无需登录
已读取 5 个工具描述,未发现针对 AI 的隐藏指令
OSV.dev 中没有 scrapewright@1.0.3 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/ozymandias-owens-2-scrapewright)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:X-API-Key, ANTHROPIC_API_KEY
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于16天前,最新版本(1.0.3)于2个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| 本项 scrapewright | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 运行位置 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 是 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 5/5 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 许可证 | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Give it a URL. It writes the scraper.
Most e-commerce catalog scraping splits into two worlds: sites on a known platform (Shopify, WooCommerce) that expose a clean JSON feed, and everything else — bespoke HTML where you hand-write a parser per site and re-write it every time the markup shifts. scrapewright collapses both into one call:
The LLM is a *compiler*, not a runtime. It runs once per site to produce a recipe of CSS selectors; every page after that is parsed by plain BeautifulSoup at zero marginal cost. That is the whole cost-control story — no per-page model calls, no token bill that scales with your crawl.
┌─────────────┐
store URL ───▶ │ detect │ └──────┬──────┘ ┌──────────────────┼──────────────────┐ ▼ ▼ ▼ shopify woocommerce generic HTML products.json wc/store/products (page mode) │ │ │ │ deterministic │ ▼ │ (free) │ cached recipe? ──yes──▶ replay (free) └────────┬─────────┘ │ no ▼ ▼ Product{} ◀───── selectors ── JSON-LD? ──yes──▶ Product{} (free) ▲ │ no │ ▼ └──────── replay ◀── LLM synthesizes recipe ONCE ──▶ cache
Everything normalizes to one Product shape, so downstream code never knows or cares which path a record came from.
pip install scrapewright # deterministic paths (Shopify, Woo, JSON-LD)
pip install "scrapewright[llm]" # + LLM recipe synthesis for custom HTML pip install "scrapewright[llm,js,excel,mcp]" # + JS rendering, XLSX, MCP server playwright install chromium # only needed for --js
from scrapewright import Scrapewright
sw = Scrapewright()
for product in sw.scrape_catalog("https://shop.example.com", max_items=200): print(product.brand, product.title, product.price, product.currency)
item = sw.scrape_page("https://boutique.example.com/products/wool-coat") print(item.model_dump(exclude={"raw"}))
for product in sw.crawl("https://boutique.example.com/collection", max_items=100): print(product.title, product.price)
scrapewright detect https://shop.example.com # platform + strategy
scrapewright run https://shop.example.com --max 50 # scrape a catalog → JSONL scrapewright crawl https://boutique.example.com/collection -o products.xlsx scrapewright run https://shop.example.com -o products.csv # Excel-ready CSV scrapewright add https://boutique.example.com/products/coat # learn a site scrapewright run https://boutique.example.com/products/coat --no-llm scrapewright list # cached recipe domains
-o writes .csv (Excel-ready, UTF-8 BOM), .xlsx (pip install scrapewright[excel]), or .jsonl; without it, products stream to stdout as JSONL.
detect answers the routing question before a job starts:
$ scrapewright detect https://some-store.com
https://some-store.com platform: bigcommerce catalog: - strategy: crawl note: BigCommerce (Stencil) markup
Twelve platforms are recognized: Shopify and WooCommerce publish a free JSON catalog, so those route to catalog — deterministic, no LLM, no browser. Magento, BigCommerce, Salesforce Commerce Cloud, Squarespace, Wix, Webflow, PrestaShop, Shopware, Ecwid and OpenCart are recognized by fingerprint and route to crawl, where the recipe path handles them like any custom site — the point of naming them is knowing what you face, not writing twelve parsers. Wix and Ecwid render client-side, so detection says crawl+js up front.
A site behind an anti-bot wall reports strategy: blocked with the HTTP status, rather than pretending it found nothing.
Products are just the built-in default. Declare the fields you want and the same compile-once/replay-free loop works on any structured page — job posts, listings, registry records:
scrapewright run https://jobs.example.com/p/123 -f title -f company -f salary:number -f tags:list --schema-name job
from scrapewright import Scrapewright, Schema
job = Schema.from_names(["title", "company", "salary:number", "tags:list"], name="job") record = Scrapewright().extract("https://jobs.example.com/p/123", job) print(record.data) # {'title': ..., 'company': ..., 'salary': ..., 'tags': [...]}
Field kinds are text (default), number, url, and list. A number field is parsed out of whatever the page wrote — "£51.77", "1.250,00", "€72,000" all become numbers — and when the page said more than the digits, the original is kept next to it as _text:
{ "price": 51.77, "price_text": "£51.77" }
A value that holds no number at all ("call us") is left as the page wrote it rather than dropped. Recipes are cached per site *and* per schema, so one domain can be compiled against several field sets without them overwriting each other.
scrapewright speaks MCP, so an agent can call it as a tool instead of reading raw HTML itself. Two ways in.
Hosted, nothing to install. Point the client at the service with a key from scrapewright.app (1,000 free rows a month; an account that has never been topped up compiles one new site and renders twenty pages a day):
{
"mcpServers": { "scrapewright": { "url": "https://scrapewright.app/mcp", "headers": { "X-API-Key": "sw_..." } } } }
Tools: detect_site, extract_page, crawl_site, crawl_status, account. Paid from the same credit balance as the REST API; no model key of your own is needed.
Local, your own model key. Run the server on your machine:
pip install "scrapewright[mcp,llm]"
scrapewright mcp
Point any MCP client at that command and the agent gains five tools: detect_site, scrape_catalog, extract_page, crawl_site, and list_learned_sites.
Drop this into your client's config — Claude Desktop, Cursor, or anything else that speaks MCP:
{
"mcpServers": { "scrapewright": { "command": "uvx", "args": ["--from", "scrapewright[mcp,llm]", "scrapewright", "mcp"], "env": { "ANTHROPIC_API_KEY": "sk-ant-..." } } } }
The key is only needed for sites on no known platform, where a recipe has to be written once. Shopify and WooCommerce stores work without it.
The economics are the point. An agent that reads pages itself pays model tokens per page, forever. These tools pay once per site — an agent crawling 500 pages spends one synthesis, not five hundred, and platform stores (Shopify, WooCommerce) cost nothing at all.
The same core behind an HTTP API, with keys, quotas, metering and background jobs:
pip install "scrapewright[service,llm]"
scrapewright keys create --label alice --plan free scrapewright serve --port 8000
curl -X POST localhost:8000/v1/extract -H "X-API-Key: sw_..." -H "Content-Type: application/json" -d '{"url": "https://shop.example.com/products/coat"}'
| Endpoint | Purpose | ||
|---|---|---|---|
POST /v1/detect | platform + strategy (cheap) | ||
POST /v1/extract | one page -> structured record | ||
POST /v1/crawl | a whole site -> job id (crawls outlive a request) | ||
... mode | links follow a listing into item pages · rows read the listing's own cards · like one item page -> every page shaped like it | ||
GET /v1/jobs/{id} | poll a crawl | ||
| `GET /v1/jobs/{id}/download?format=csv\ | xlsx\ | jsonl` | the finished crawl as a file |
GET /v1/usage | what this key has consumed, against its plan |
Or skip the API: scrapewright.app/account takes a listing URL and a field list, runs the crawl, and hands back the spreadsheet.
One action costs real money: compiling a new site, a single LLM pass over a page, measured at $0.02 on a small product page and $0.15 on a heavy rendered one. Everything after that is BeautifulSoup — the ten-thousandth record from a compiled site is free to serve. So credits are priced off that one action, and everything else is denominated relative to it:
| Action | Credits |
|---|---|
| 1 record delivered | 1 |
| 1 browser render | 5 |
| 1 new site compiled | 300 |
page fetches, detect | free |
$ scrapewright plans
pack credits price $/credit margin starter 10,000 $10 0.00100 80.0% growth 50,000 $40 0.00080 75.0% scale 250,000 $150 0.00060 66.7%
Free: 1,000 credits a month, resetting.
Margin is measured on compiling a site, because that is the only step that costs anything; a test fails if a price edit drops any pack below 60%. A free account can cost us at most $0.20 a month, even if every free credit goes to the most expensive action there is.
Credits are a ledger, not a counter — every grant and every charge is a row, so a disputed bill can be reconstructed line by line, and a replayed payment webhook cannot double-credit (grants take an idempotency key). Running out returns 402 with the balance and what to do about it; a crawl is capped by the credits on hand, so a job stops at what the caller can pay for instead of overdrawing.
scrapewright credits grant <key_id> --pack starter --idempotency <payment_id>
scrapewright credits balance
Stripe is wired in and turned on by environment, not by a code change:
pip install "scrapewright[service,stripe]"
export STRIPE_SECRET_KEY=sk_test_... # absent -> nothing is for sale export STRIPE_WEBHOOK_SECRET=whsec_... # absent -> webhooks are refused scrapewright serve
| Endpoint | Purpose |
|---|---|
GET /v1/credits/packs | the price list — public, no key needed |
POST /v1/credits/checkout | start a purchase, returns a Stripe Checkout URL |
POST /v1/webhooks/stripe | payment notifications from Stripe |
The webhook endpoint takes no API key — Stripe is the caller, so the signature *is* the credential, and an unverified endpoint would be a free credit printer for anyone who guessed the URL. Three rules hold the integration up: