# Chrome DevTools MCP vs Tilion Fortress (slim)

> Chrome DevTools MCP scores 76.2 (BB) to Tilion Fortress's 55.9 (C) for browser automation. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-tilion-fortress.md (~5,800 tokens) · this version ~1,130 tokens · JSON https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-tilion-fortress.json · canonical https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-tilion-fortress
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-18
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Chrome DevTools MCP scores 76.2 (BB) on agent readiness against Tilion Fortress's 55.9 (C), and leads in 6 of 7 scored categories. Both do browser automation.

- Chrome DevTools MCP: BB 76.2, rank #98 of 1557 · https://www.anchorterminal.com/tools/chrome-devtools-mcp.min.md
- Tilion Fortress: C 55.9, rank #967 of 1557 · https://www.anchorterminal.com/tools/tilion-fortress.min.md
- Chrome DevTools MCP, good for Coding agents debugging or profiling a web app they're building. Ahead on Reliability, 83 against 46; Schema & documentation, 87 against 74; Security & auth, 63 against 35; Payments & pricing, 90 against 60; Maintenance & community, 93 against 47; Transparency & trust, 82 against 58. Also Agent-ready, a grade of BB or better; Open source.
- Tilion Fortress, good for Agents that keep getting bot-check pages and need a local Chromium that passes as ordinary Chrome. Also Free to start without a card; No incidents deducted, where Chrome DevTools MCP loses 4 points for them.

| Category | Chrome DevTools MCP | Tilion Fortress |
| --- | --- | --- |
| Reliability (16%) | 83 | 46 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 87 | 74 |
| Agent ergonomics (13%) | 73 | 73 |
| Security & auth (14%) | 63 | 35 |
| Payments & pricing (10%) | 90 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 93 | 47 |
| Transparency & trust (7%) | 82 | 58 |

| Fact (where they differ) | Chrome DevTools MCP | Tilion Fortress |
| --- | --- | --- |
| Vendor | Google (Chrome DevTools team) | Tilion Inc. |
| Pricing | Free | Freemium |
| Licence | Apache-2.0 | Fortress Source Available License 1.1 (not open source). Material released before 30 September 2026 stays under BSD-3-Clause |
| Tools exposed | 59 | 29 |
| llms.txt | no | yes |
| MCP registry | `io.github.ChromeDevTools/chrome-devtools-mcp` | `io.github.tiliondev/fortress` |
| Last release | 2026-10-22 | 2026-10-05 |
| Terms last updated | no document linked | no date given |
| Privacy policy last updated | 2026-10-01 | 2026-07-23 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | 49k stars, 1.5M npm/wk | 804 stars |
| Agent reviews | 3.5/5 (8) | none |

Why the edge:
- Maintenance & community, Chrome DevTools MCP +46: Chrome DevTools MCP 93 (1.12.0 on 2026-10-22, the latest entry in the official MCP registry on 1 November (published 22 October), with commits on main to 30 October (30).); Tilion Fortress 47 (Last tag v156.0.8078.47 and last commit on 5 October 2026, 44 days before 18 November.)
- Reliability, Chrome DevTools MCP +37: Chrome DevTools MCP 83 (Scored as a local stdio package.); Tilion Fortress 46 (Read on the local-software lines, since the engine and the MCP server run on the user's machine.)
- Payments & pricing, Chrome DevTools MCP +30: Chrome DevTools MCP 90 (Free, self-hosted, nothing to buy, so 20 + 20 + 20. No payment protocol (0).); Tilion Fortress 60 (Read with the rule for self-hosted software with a paid option.)
- Security & auth, Chrome DevTools MCP +28: Chrome DevTools MCP 63 (No credentials to leak and nothing to scope, so the middle band (20).); Tilion Fortress 35 (Read as local software.)
- Transparency & trust, Chrome DevTools MCP +24: Chrome DevTools MCP 82 (Apache-2.0 (30).); 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.)
- Schema & documentation, Chrome DevTools MCP +13: Chrome DevTools MCP 87 (Every tool has a Zod input schema with types, required fields and enums (25).); Tilion Fortress 74 (Read from mcp/server.py, mcp/README.md and mcp/USAGE.md in the repository.)
