Server data from the Official MCP Registry
Fetch any web page's HTML, AI-parsed JSON, or Google results via the ScrapeUnblocker anti-bot API
Fetch any web page's HTML, AI-parsed JSON, or Google results via the ScrapeUnblocker anti-bot API
Remote endpoints: streamable-http: https://mcp.scrapeunblocker.com/mcp
This is a well-architected OAuth-enabled MCP server with strong authentication design and proper credential handling. The code implements dual authentication modes (OAuth 2.1 and static API keys) with careful separation of concerns. Minor code quality issues around error handling breadth and missing input validation on environment variables do not significantly impact security, as permissions align well with the server's purpose of web scraping via the ScrapeUnblocker API. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity).
6 files analyzed · 7 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Available as Local & Remote
This plugin can run on your machine or connect to a hosted endpoint. during install.
From the project's GitHub README.
A hosted (HTTP) Model Context Protocol server for ScrapeUnblocker, deployed as a Vercel serverless function. It lets claude.ai (web and mobile), Claude Desktop, Claude Code, and any other MCP client fetch any web page's HTML - or AI-parsed JSON, or Google results - through ScrapeUnblocker's anti-bot API, billed to your own account.
Prefer a local install with no hosting? Use the stdio package instead:
scrapeunblocker-mcp.
https://mcp.scrapeunblocker.com/mcp
You need a ScrapeUnblocker account - create a free one. There are two ways to authenticate, and you only need one of them.
A. Sign in with OAuth (recommended) - nothing to copy or paste. The server is an OAuth 2.1 Resource Server backed by Auth0, so the client runs a standard PKCE flow, and the server resolves your ScrapeUnblocker key server-side from the account you signed in with (the token is never passed through to the backend, per RFC 8707).
If your client asks for an OAuth client ID, use the public one - it is a PKCE client, so it carries no secret and is safe to share:
5BM5Wk2dE4ABkDITmuKfemPLnn3QQ8jd
Leave the client secret field empty.
B. Bring your own API key - handy for scripts and clients without an OAuth flow. Supply the key any of three ways:
?key=YOUR_KEY (or ?token=YOUR_KEY) in the URL.Authorization: Bearer YOUR_KEY header (a non-JWT value).x-scrapeunblocker-key: YOUR_KEY header.Listing the tools (initialize, tools/list) needs no credentials at all, so MCP
directories and inspectors can introspect the server; actually running a tool does.
| Env var | Purpose |
|---|---|
AUTH0_ISSUER | Auth0 issuer URL, e.g. https://TENANT.auth0.com/ (trailing slash). Enables OAuth together with MCP_AUDIENCE. |
MCP_AUDIENCE | Canonical MCP URI = the Auth0 API Identifier, https://mcp.scrapeunblocker.com/mcp. The token aud must match this. |
MCP_EMAIL_CLAIM | Optional namespaced claim carrying the user's email (set by an Auth0 Post-Login Action), e.g. https://scrapeunblocker.com/email. Falls back to the standard email claim. |
MCP_RESOURCE_METADATA_URL | Optional override for the RFC 9728 metadata URL advertised in WWW-Authenticate. |
UTILS_API_BASE_URL | utils-api base for the email_to_key lookup, e.g. https://utils-api.scrapeunblocker.com. |
AWS_ACCESS_KEY_ID / AWS_SECRET_ACCESS_KEY / AWS_REGION | IAM creds (SigV4, execute-api) for calling utils-api. |
Discovery endpoints served (via vercel.json rewrites):
/.well-known/oauth-protected-resource and /.well-known/oauth-protected-resource/mcp.
https://mcp.scrapeunblocker.com/mcp5BM5Wk2dE4ABkDITmuKfemPLnn3QQ8jd
and leave OAuth Client Secret empty.Or skip OAuth entirely and paste a personalised URL instead:
https://mcp.scrapeunblocker.com/mcp?key=YOUR_API_KEY
claude mcp add --transport http scrapeunblocker "https://mcp.scrapeunblocker.com/mcp?key=YOUR_API_KEY"
| Tool | What it does |
|---|---|
fetch_html | Fetch the fully rendered HTML of a URL. |
fetch_parsed | Fetch a page and return AI-parsed structured JSON. |
google_search | Run a Google search and return organic results as JSON. |
This is a standard Vercel project - no build step, the function lives in api/mcp.ts.
vercel # preview
vercel --prod # production
Then point the mcp.scrapeunblocker.com domain at the Vercel project. Scraping calls
can be slow, so the function's maxDuration is set to 60s (raise it on a paid Vercel
plan if you hit timeouts on heavy pages).
MIT
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.