remove-paywall-mcp
Searches the Wayback Machine via the Internet Archive to retrieve archived copies of paywalled articles and extract clean text.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@remove-paywall-mcp remove paywall from https://www.wsj.com/articles/abc123"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
remove-paywall-mcp
MCP server that removes article paywalls by searching internet archives. Give it a URL, get back the article text.
How it works
You give it a paywalled article URL
Tracking params are stripped and the URL is normalized
It tries multiple approaches in parallel:
Direct fetch with Googlebot user-agent (FT, WSJ, and many others serve full content to crawlers)
12ft.io proxy for hard paywalls
iitty textise for plain-text rendering
Wayback Machine CDX API, archive.ph/is mirrors, and Wayback Availability API
It extracts the article body with readability-lxml, stripping navigation, ads, and sidebar cruft
Post-extraction check: if the result still contains paywall text (e.g., the snapshot captured the paywall itself), it retries with the next archive
It returns clean text with the title and snapshot URL
It also learns from every attempt — success rates per domain per archive source are tracked in a local SQLite database, and archive search order is re-ranked automatically using Laplace smoothing.
Related MCP server: mcp-server-wayback
Install
# zero-install (recommended — works everywhere uvx is available)
uvx remove-paywall-mcp
# from PyPI
pip install remove-paywall-mcp
# from source
pip install git+https://github.com/jasval/remove-paywall-mcp.git
# Docker
docker run -i --rm remove-paywall-mcp
docker compose up -d # HTTP mode on port 8000Platform configs
Once installed, add this to your MCP client config:
OpenCode
{
"mcp": {
"remove-paywall": {
"type": "local",
"command": ["uvx", "remove-paywall-mcp"],
"enabled": true
}
}
}Claude Desktop
{
"mcpServers": {
"remove-paywall": {
"command": "uvx",
"args": ["remove-paywall-mcp"]
}
}
}LiteLLM
mcp_tools:
remove_paywall:
type: "stdio"
command: "uvx"
args: ["remove-paywall-mcp"]Docker (any client)
{"command": "docker", "args": ["run", "-i", "--rm", "remove-paywall-mcp"]}Tools
remove_paywall
Main tool. Removes a paywall from an article URL and returns clean article text.
Parameter | Type | Description |
| string | The paywalled article URL |
search_archives
Search all archive sources for snapshots without extracting content. Useful to see what's available.
Parameter | Type | Description |
| string | The article URL to search for |
get_from_archive
Fetch from a specific archive source.
Parameter | Type | Description |
| string | The article URL |
| string |
|
domain_info
Look up a domain in the knowledge base — paywall status, notes, and per-archive success rates.
Parameter | Type | Description |
| string | Domain name (e.g. |
add_domain
Register a domain in the knowledge base. Mark paywalled domains so archives are searched first, or non-paywalled domains so the live page is fetched directly.
Parameter | Type | Description |
| string | Domain name |
| boolean |
|
| string? | Optional description |
Prompts
The server provides 3 prompt templates for LLMs to use the tools effectively.
remove_paywall_prompt
Full instruct for bypassing a specific URL. Tells the assistant to use remove_paywall, fall back to search_archives, and check domain_info.
Parameter | Type | Description |
| string | The paywalled article URL |
bypass_paywall
Short alias — just tells the assistant to call remove_paywall on the URL.
Parameter | Type | Description |
| string | The paywalled article URL |
handle_paywalls
System prompt fragment. No arguments — returns instructions for the assistant to automatically call remove_paywall whenever it encounters a paywall, login wall, or metered content. Paste this into your system prompt or load it as a prompt at session start.
Domain knowledge base
Seeded with 33 well-known paywalled domains (NYT, WSJ, Bloomberg, Medium, etc.), stored in SQLite at ~/.remove-paywall-mcp/domains.db. Tracks every archive success/failure per domain and re-ranks archive search order automatically — domains where archive.is consistently fails won't waste time on it.
Env vars
Variable | Default | Description |
|
|
|
|
| Bind address (HTTP mode) |
|
| Port (HTTP mode) |
|
| Database directory |
Archive sources
Source | Priority | Notes |
Googlebot direct | 1 | Fetches directly with |
12ft.io | 2 | Proxy at |
iitty | 3 |
|
Wayback Machine | 4 | CDX API, newest-first ( |
archive.is/ph mirrors | 5 | Tries newest/oldest across archive.ph, archive.is, archive.today, archive.md |
Wayback Availability | 6 |
|
Priority is dynamically re-ranked per domain based on historical success rates recorded in the knowledge base.
Architecture
MCP client (Claude/OpenCode/LiteLLM)
│ stdio or HTTP
▼
┌─────────────────┐
│ server.py │ MCPServer with 5 tools
│ +3 prompts │
└────────┬────────┘
│
┌────┴────┐
▼ ▼
┌────────┐ ┌──────────┐
│archives│ │ extractors│
│ .py │ │ .py │
│ │ │ │
│googlebot│ │readability│
│ 12ft │ │Beautiful │
│ iitty │ │Soup │
│ wayback│ │ │
│ archive│ │ │
│ .is/ph │ │ │
│ wayback│ │ │
│ avail │ │ │
└───┬────┘ └──────────┘
│
▼
┌──────────────┐
│domain_store │
│ .py │
│ │
│ SQLite knows │
│ which domains│
│ have paywalls│
│ and which │
│ archives work│
│ best (Laplace│
│ smoothed) │
└──────────────┘License
MIT
Available Tools
5 toolsadd_domainA
Register a domain in the paywall knowledge base.
Set has_paywall=true for sites that normally have paywalls (so archives are tried first). Set has_paywall=false for sites that don't (so archive search is skipped and the live page is fetched directly).
Inputs: domain (required), has_paywall (required), notes. Returns: result
domain_infoA
Look up stored knowledge about a paywall domain.
Returns paywall status, user notes, historical archive success rates, and the best archive order for this domain. Use add_domain to register new domains.
Inputs: domain (required). Returns: result
get_from_archiveB
Fetch an archived version of a URL from a specific source.
source must be one of: googlebot, 12ft, iitty, wayback, archive_is, wayback_available. Returns the extracted article text.
Inputs: url (required), source (required). Returns: result
remove_paywallA
Remove a paywall from an article URL by searching internet archives.
First tries a direct fetch with Googlebot user-agent (many sites serve full content to crawlers), then 12ft.io proxy, iitty textise, Wayback Machine (CDX API with dedup + newest-first), archive.is/ph mirrors, and Wayback Availability API. Archives are tried in parallel using historical success rates to prioritize the best one for each domain.
Returns extracted article text with title and snapshot info.
Inputs: url (required). Returns: result
search_archivesA
Search all archive sources for snapshots of a URL.
Returns a list of available snapshot URLs from each archive source: Googlebot direct fetch, 12ft.io proxy, iitty textise, Wayback Machine, archive.is/ph mirrors, and Wayback Availability API. Does not extract content — use remove_paywall for full article retrieval.
Inputs: url (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool has a distinct purpose: remove_paywall is the high-level bypass, search_archives lists snapshots, get_from_archive fetches from a named source, and domain_info/add_domain manage domain knowledge. No two tools appear to do the same thing.
Most tool names follow a verb_noun pattern (remove_paywall, search_archives, add_domain), but get_from_archive uses verb-preposition-noun and domain_info is a noun phrase. This is a minor deviation from an otherwise consistent snake_case style.
With 5 tools, the server is well-scoped for its purpose: one main operation, two low-level retrieval ops, and two knowledge-base ops. No redundancy and no missing essential functionality.
The tool surface covers the full workflow: automatic bypass, manual archive search/fetch, and persistent domain knowledge. The ability to consult and add domain info ensures agents can adapt to known paywall patterns. No major gaps evident.
Maintenance
Related MCP Connectors
One MCP server for all web data. Scrape, search, crawl, and AI research in one install.
One MCP server for 180+ live web-data APIs returning clean JSON from sites that block scrapers.
Turn any public website into an MCP server for agents to search, read and navigate.
Unified 15-tool SEO, SERP, clean Markdown & GEO (LLM citation Share-of-Voice) MCP server.
Related MCP Servers
- AlicenseNot gradedqualityFmaintenanceAn MCP server that extracts clean Markdown or HTML content from web pages by stripping away ads, navigation, and clutter. It offers tools to process URLs or raw HTML, returning structured metadata alongside the main article content.2MIT
- AlicenseAqualityCmaintenanceMCP server for the Internet Archive's Wayback Machine. Search archived snapshots, extract page text from a specific date, track how a site has changed over time, check if broken links are recoverable, and perform research across Internet Archive collections.621 PyPI3MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server for intelligent web content extraction from JavaScript-heavy sites using single-file and trafilatura. It enables AI agents to fetch, render, and paginate through clean article content and metadata.23MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that enables AI agents to automatically pay for and access paywalled content via the x402 payment protocol.8 npmMIT