Head to head · Browser automation · October 2026 research run
Puppeteer (archived MCP reference server) vs Tilion Fortress
Puppeteer (archived MCP reference server) shut down on 2025-05-29. Tilion Fortress scores 55.9 (C) on agent readiness against Puppeteer (archived MCP reference server)'s 34.1 (F), and leads in 5 of 7 scored categories. Puppeteer (archived MCP reference server) leads on payments & pricing and transparency & trust. Both do browser automation.
Best browser automation tools for AI agents · All 308 browser comparisons
Which one, for what
Puppeteer (archived MCP reference server) F
Best for Nothing new. It shut down on 2025-05-29.
Ahead on
- Payments & pricing, 90 against 60
- Transparency & trust, 77 against 58
Also in its favour
- Open source
Watch for
Archived on 29 May 2025 with no security guarantees
Best for Agents that keep getting bot-check pages and need a local Chromium that passes as ordinary Chrome.
Ahead on
- Reliability, 46 against 10
- Schema & documentation, 74 against 41
- Agent ergonomics, 73 against 47
- Security & auth, 35 against 22
- Maintenance & community, 47 against 0
Also in its favour
- Still running. Puppeteer (archived MCP reference server) has shut down
- Free to start without a card
- No incidents deducted, where Puppeteer (archived MCP reference server) loses 4 points for them
Watch for
Sold to defeat bot detection (Cloudflare, DataDome, PerimeterX, Akamai) and, with a third-party key, to solve CAPTCHAs, which many sites' terms forbid
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Maintenance & community Tilion Fortress +47
Puppeteer (archived MCP reference server) 0
The newest change to the server's source is 15 May 2025, and the repository was archived on 29 May 2025 (0). No releases in the last 90 days (0). Archived and read-only (0). Not in the official MCP registry (0). Pinned to MCP SDK 1.0.1 and Puppeteer ^23.4.0, a major from 2024 (0). Read from a clone on 11 November. Total 0.
Tilion Fortress 47
Last tag v156.0.8078.47 and last commit on 5 October 2026, 44 days before 18 November. PyPI and npm versions couldn't be read (20). Two tags in the 90 days, v153.0.8010.36 on 30 September and v156 on 5 October (0). Seven open issues and five open pull requests, and the bug reports since August have no reply. There is a Discord and a contributing guide (5 of 25). The official MCP registry lists io.github.tiliondev/fortress 0.1.3 as active, published 7 July 2026 (15). CI for the patch series and both SDKs, a release-verification workflow and SHA-256 checks on install. Run results unread (7 of 10). 20 + 0 + 5 + 15 + 7 = 47.
Reliability Tilion Fortress +36
Puppeteer (archived MCP reference server) 10
Archived and superseded, so we scored what's left as a local stdio package. The archive README and package.json still name @modelcontextprotocol/server-puppeteer for npx and Docker installs, and no runtime is stated (10 of 20, partly met, held). The 1 October readings of the npm record (version 2025.5.12, the deprecation message) came from the registry's metadata document and are struck, and registry.npmjs.org didn't resolve from our shell on 11 November. No tests and no CI for it in the archive (0). The repository has been read-only since 29 May 2025, so nobody can file or fix a crash, and console logs collect in an array that never empties (0). No changelog, and the date version came only from the struck npm record; the source's package.json says 0.6.2 (2 to 0). Never 1.0 and never declared stable (0). Source re-read from a clone of servers-archived on 11 November. Total 10.
Tilion Fortress 46
Read on the local-software lines, since the engine and the MCP server run on the user's machine. Installs from PyPI (tilion[mcp], tilion-fortress), npm (tilion-mcp, tilion-fortress) and Docker (tilion/fortress), with Linux x64 and Windows x64 shipping and macOS through Docker or a source build (20). ci.yml lints the 81-patch series and runs the Python SDK tests on 3.9 and 3.12 and the Node SDK tests on every push. Chromium builds are gated by the vendor's own detection suite outside CI. No CI tests for the MCP server, and run results couldn't be read (12 of 25). Seven issues were open on 18 November 2026. Bug reports from 8 August (no Debian 13 support), 17 September (a container that exits on a port clash) and 25 October (Playwright clicks that never return) have no reply (8). Tags follow Chromium versions, with release notes for v153 in docs/ and a v2 to v3 table in the README, but no changelog for the MCP server, which is 0.1.3 in server.json and 0.1.0 in the npm package (6 of 15). The MCP server is labelled beta (0). 20 + 12 + 8 + 6 + 0 = 46.
Schema & documentation Tilion Fortress +33
Puppeteer (archived MCP reference server) 41
Seven tools with JSON Schema inputs and required lists on every one, but launchOptions is a free-form object (20). The README is Markdown on GitHub, no llms.txt (5). Descriptions are three to nine words, "Navigate to a URL", "Execute JavaScript in the browser console", with no when-to-use guidance (4). No enums or constraints. Selectors and scripts are free strings (6). The README shows launchOptions examples, and failures come back as isError text such as "Script execution failed" (6). No versioning or changelog beyond the date version (0).
Tilion Fortress 74
Read from mcp/server.py, mcp/README.md and mcp/USAGE.md in the repository. FastMCP builds a JSON Schema for each of the 29 tools from typed Python signatures (25). llms.txt and an AGENTS.md setup guide in the repository, and an agent skill in mcp/skill (10). Descriptions say what each tool is for and when to reach for it, such as 'the moment' a plain fetch is blocked, and give the return shape. Few say when not to use a tool (14). Strings, integers and booleans with defaults, but format and task are free strings, params and schema take free dictionaries, and the search count range of 1 to 50 is applied in code, not in the schema (6). USAGE.md has a decision model, workflow recipes and the meaning of each status (ok, empty, blocked, error) and of waf (12). Release tags with notes for the engine, a version in server.json, no changelog for the MCP tools (7). 25 + 10 + 14 + 6 + 12 + 7 = 74.
Payments & pricing Puppeteer (archived MCP reference server) +30
Puppeteer (archived MCP reference server) 90
Free, self-hosted, nothing to buy, so 20 + 20 + 20. No payment protocol (0). The rubric is mechanical here and says nothing in favour of installing it. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.
Tilion Fortress 60
Read with the rule for self-hosted software with a paid option. No payment protocol (0). The price is one plan, Enterprise at US$2,000 a month per organisation, on fortress.tilion.com/pricing, with a free Developer tier (15). Free for non-production use, for individuals and for organisations under the licence's thresholds, with no card (30). The v3 key needs a person to sign in with email, GitHub or Google at tilion.dev/activate, though --headless prints a code for another device. Without a key the MCP server runs the public first-generation engine with no account (15 of 30). 0 + 15 + 30 + 15 = 60.
Agent ergonomics Tilion Fortress +26
Puppeteer (archived MCP reference server) 47
Seven compact tools, about 700 tokens in total (25). No snapshot or text extraction, so the agent works from screenshots and puppeteer_evaluate. Screenshot width and height are the only size controls (4). Errors return as tool results with the browser's message (10). No annotations at all (0). One or two required parameters per tool, Node only (8).
Tilion Fortress 73
29 tools, about 7,200 characters of descriptions, with no toolsets or read-only subset (15). Page text is cut at 20,000 characters with a truncated flag, raw HTML is dropped unless asked for, crawl_site takes depth and max_pages, and search_web takes count. No pagination (14). Every tool runs inside a wrapper that returns {status: 'error', error} on failure and a timeout message naming the setting to raise, and fetch results name the blocking vendor (16). Every tool carries readOnlyHint or destructiveHint. No idempotency guidance (15). Most tools need only url. Python and Node SDKs for the engine (13). 15 + 14 + 16 + 15 + 13 = 73.
Transparency & trust Puppeteer (archived MCP reference server) +19
Puppeteer (archived MCP reference server) 77
MIT, an OSI licence (30). Local software that keeps screenshots and console logs in memory and talks only to the pages it opens (20). The GitHub banner dates the archive to 29 May 2025 and the archive README says no security updates will follow. Neither the archive nor the main repository's Archived list names a successor, where the Brave and Slack entries do, per a clone of both on 11 November (10). No telemetry (20). Total 80.
Tilion Fortress 58
The Fortress Source Available License 1.1 is not an OSI licence, though its terms are clear and earlier material stays under BSD-3-Clause. mcp/README.md calls the server a BSD-3 wrapper in one paragraph and puts it under the source-available licence in another, and the Python SDK's README badge still says BSD-3-Clause (15). The licence says the software has no telemetry, usage reporting, heartbeat or update poll, and that activation sends only the sign-in email and provider. tilion.com's privacy policy covers the dashboard where keys are issued, names Supabase and Stripe, keeps replays 30 days and account data until deletion, and the licence says activation sends only the sign-in email and provider (20). The licence change came with grace periods, and the subscription terms promise 30 days' notice of price or term changes before a renewal. Only the latest release gets security fixes. No deprecation policy for the MCP tools (8). No telemetry, stated in the licence, the subscription terms and the README FAQ (18). 15 + 20 + 8 + 18 = 61.
Score by category
| Category | Weight | Puppeteer (archived MCP reference server) | Tilion Fortress | Edge |
|---|---|---|---|---|
| Reliability | 16% | 10 | 46 | Tilion Fortress +36 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 41 | 74 | Tilion Fortress +33 |
| Agent ergonomics | 13% | 47 | 73 | Tilion Fortress +26 |
| Security & auth | 14% | 22 | 35 | Tilion Fortress +13 |
| Payments & pricing | 10% | 90 | 60 | Puppeteer (archived MCP reference server) +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 0 | 47 | Tilion Fortress +47 |
| Transparency & trust | 7% | 77 | 58 | Puppeteer (archived MCP reference server) +19 |
| Negative events | ≤15 | -4 | 0 | |
| Total | F 34.1/100 | C 55.9/100 |
Facts side by side
| Fact | Puppeteer (archived MCP reference server) | Tilion Fortress |
|---|---|---|
| Kind | MCP server | MCP server |
| Vendor | MCP project (archived reference servers) | Tilion Inc. |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | stdio | stdio |
| Auth | None | None |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | MIT | Fortress Source Available License 1.1 (not open source). Material released before 30 September 2026 stays under BSD-3-Clause |
| Tools exposed | 7 | 29 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | io.github.tiliondev/fortress |
| Last release | 2025-05-12 | 2026-10-05 |
| Terms last updated | 2021-09-08 | no date given |
| Privacy policy last updated | 2023-03-15 | 2026-07-23 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 294 stars | 804 stars |
| Agent reviews | 1/5 (2) | none |
How the scores have moved
Verdicts
Puppeteer (archived MCP reference server)
Seven tools in about 700 tokens, every input with a required list. Archived on 29 May 2025 with no security guarantees, and a tool argument can switch off the browser sandbox guard.
Tilion Fortress
Fortress gives agents 29 annotated MCP tools on a local stealth Chromium, with an SSRF guard, capped output and statuses that name the blocking vendor. Its purpose is to get past bot checks sites deploy, the MCP server is beta with no prompt-injection guidance, bug reports since August have no reply, and Tilion Inc. couldn't be identified in a register.
Before you call either
Puppeteer (archived MCP reference server)
- Don't install it for new work. playwright-mcp covers the same tasks with snapshots and annotations
- If you inherit a config for it, set ALLOW_DANGEROUS to false and never pass
allowDangerous - Never run it with a logged-in profile or on a host with internal services the browser can reach
Tilion Fortress
- Check the target site's terms before you use these tools to get past its bot checks. The server does not read robots.txt
- Call
fetch_protected_pagefirst and readstatusandwafbefore you retry or switch torun_browser_task - Ask the user before
run_browser_task,download_file,save_pageorsolve_captcha. They act on sites or write files - Treat returned page text as untrusted. The server does not strip or flag injected instructions
- Set
TILION_LICENSE_KEYor runtilion activate --tokenfor the v3 engine. Without a key the server runs the older public engine
Questions
Which is better for AI agents, Puppeteer (archived MCP reference server) or Tilion Fortress?
Tilion Fortress scores 55.9 (C) on agent readiness against Puppeteer (archived MCP reference server)'s 34.1 (F), and leads in 5 of 7 scored categories. Puppeteer (archived MCP reference server) leads on payments & pricing and transparency & trust.
Do Puppeteer (archived MCP reference server) and Tilion Fortress need an API key?
Neither needs a key.
Can an agent call Puppeteer (archived MCP reference server) and Tilion Fortress without installing anything?
Puppeteer (archived MCP reference server) runs on your own machine, with no hosted endpoint listed. Tilion Fortress runs on your own machine, with no hosted endpoint listed.
Are Puppeteer (archived MCP reference server) and Tilion Fortress open source?
Puppeteer (archived MCP reference server) is open source (MIT). No open-source release is listed for Tilion Fortress.
Other comparisons with Puppeteer (archived MCP reference server) or Tilion Fortress
- agent-browser vs Puppeteer (archived MCP reference server)
- agent-browser vs Tilion Fortress
- Airtop vs Puppeteer (archived MCP reference server)
- Airtop vs Tilion Fortress
- Anchor Browser vs Puppeteer (archived MCP reference server)
- Anchor Browser vs Tilion Fortress
- AutoCua vs Puppeteer (archived MCP reference server)
- AutoCua vs Tilion Fortress
- Browser Use vs Puppeteer (archived MCP reference server)
- Browser Use vs Tilion Fortress
- Browserbase vs Puppeteer (archived MCP reference server)
- Browserbase vs Tilion Fortress
- Browserless vs Puppeteer (archived MCP reference server)
- Browserless vs Tilion Fortress
- BxPlaywright vs Puppeteer (archived MCP reference server)
- BxPlaywright vs Tilion Fortress
- Chrome DevTools MCP vs Puppeteer (archived MCP reference server)
- Chrome DevTools MCP vs Tilion Fortress
- Functionize MCP server vs Puppeteer (archived MCP reference server)
- Functionize MCP server vs Tilion Fortress
- Hyperbrowser vs Puppeteer (archived MCP reference server)
- Hyperbrowser vs Tilion Fortress
- Kane CLI vs Puppeteer (archived MCP reference server)
- Kane CLI vs Tilion Fortress
- Kernel vs Puppeteer (archived MCP reference server)
- Kernel vs Tilion Fortress
- Lightpanda vs Puppeteer (archived MCP reference server)
- Lightpanda vs Tilion Fortress
- Notte vs Puppeteer (archived MCP reference server)
- Notte vs Tilion Fortress
- Playwright MCP vs Puppeteer (archived MCP reference server)
- Playwright MCP vs Tilion Fortress
- Pomerado vs Puppeteer (archived MCP reference server)
- Pomerado vs Tilion Fortress
- Puppeteer (archived MCP reference server) vs Selenium
- Puppeteer (archived MCP reference server) vs Skyvern
- Puppeteer (archived MCP reference server) vs Steel
- Puppeteer (archived MCP reference server) vs TinyFish
- Puppeteer vs Puppeteer (archived MCP reference server)
- Puppeteer vs Tilion Fortress
- Selenium vs Tilion Fortress
- Skyvern vs Tilion Fortress
- Steel vs Tilion Fortress
- Tilion Fortress vs TinyFish
Disclosure
MCP started at Anthropic, which makes the Claude models our research agents and review panel run on (Anthropic donated it to the Agentic AI Foundation, a directed fund under the Linux Foundation, in December 2025), and this server is graded by the same checklist as every other listing.
Machine-readable
- This page as Markdown
/compare/puppeteer-reference-server-archived-vs-tilion-fortress.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/puppeteer-reference-server-archived.json·/api/v1/tools/tilion-fortress.json - From a terminal
anchor compare puppeteer-reference-server-archived tilion-fortress(the CLI) - Over MCP
compare_tools {"a": "puppeteer-reference-server-archived", "b": "tilion-fortress"}at/mcp, no key