feedthrough
io.github.feedthrough/feedthrough
About feedthrough
feedthrough is an MCP server published by the GitHub account feedthrough. Debug bridge inside your web app: an agent reads the DOM, console and network. Any browser.
It runs on your own machine: your AI client starts it from the npm package @feedthrough/mcp at version 0.4.0.
It asks for no keys or passwords.
Version 0.4.0 was published on 4 September 2026, and the source code is public, so you can read it before installing.
Written from the registry entry. 9 automated checks on the registry entry and the package code: 7 pass, 0 warn, 0 fail, 2 info. How we check.
What it asks for
| Variable | Required | Secret | Description |
|---|---|---|---|
FEEDTHROUGH_PORT | No | No | Port the bridge WebSocket server listens on (defaults to 8765). |
FEEDTHROUGH_ALLOWED_HOST_SUFFIXES | No | No | Comma-separated non-loopback host suffixes allowed to connect (defaults to .test). Setting it replaces the default, so include .test to keep it. |
Checks
| Check | Result | Detail |
|---|---|---|
| Source repository linked | Pass | https://github.com/feedthrough/feedthrough |
| Version pinned | Pass | Every package has an explicit version |
| Secrets requested | Info | Asks for no secrets |
| Known package registry | Pass | All packages come from npm, PyPI, OCI, NuGet or MCPB |
| Namespace ownership | Info | Name verified via GitHub account feedthrough |
| Registry text aimed at the AI | Pass | Description and settings contain no hidden characters or instructions to the AI |
| Install scripts | Pass | @feedthrough/mcp@0.4.0 runs nothing at install |
| Code red flags | Pass | Read 10 files in @feedthrough/mcp@0.4.0: no obfuscation, encoded execution, credential reads or data-collection endpoints found |
| Text aimed at the AI | Pass | No hidden characters or instructions to the AI in 10 files, including comments and the README |
Popularity & health: 53 / 100
Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.
1 forks, 13 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.
What people say
No Hacker News threads link to its source code.
Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.
Facts
| Registry name | io.github.feedthrough/feedthrough |
|---|---|
| Publisher | GitHub account feedthrough |
| How the name is verified | Name verified via GitHub account feedthrough. The registry ties the name prefix to that account or domain; it does not check the code. |
| Type | Local: runs on your machine from a package |
| Packages | npm @feedthrough/mcp 0.4.0 (stdio) |
| Version | 0.4.0 |
| Published | |
| Last updated | |
| Source repository | https://github.com/feedthrough/feedthrough |
| Website | None linked |
| Category | Browser automation (assigned by keyword rule, not by hand) |
Related servers in Browser automation
- peek6/7Exposes recorded browser sessions (rrweb DOM, console, network) to…
- mcp-cdp7/7Safe-by-default MCP that drives an Electron/Chrome app over CDP:…
- devcdp7/7Chrome DevTools for AI assistants: console, network, DOM, source…
Firefox DevTools MCP6/7Control and debug Firefox: navigate, fill forms, inspect network…- nexus-browser-mcp7/7Event-driven deterministic browser MCP: HITL gates, audit,…
- Browser Scraper7/7Stealth Chrome for AI agents: bot-protected sites, Turnstile,…