Stealthy browser automation, testing, and web-scraping via CDP Mode.
Tether is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Use the Chrome or Firefox tabs you share, signed in as you: read, click, fill forms, debug.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user udaysinh-git-tether-mcp '--' npx -y tether-browser
# 2 — ask your agent for something these tools do
# list_tabs, open_tab, close_tab and 49 more
Tether costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Tether as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user udaysinh-git-tether-mcp '--' npx -y tether-browserReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
52 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
List the browser tabs you can use. Normally these are the tabs the user shared by clicking Tether, plus tabs you or those pages opened. If the user has turned on bypass mode, every tab is listed.
No parameter schema on file.
Open a URL in a new tab in the user's browser. The new tab is shared with you.
No parameter schema on file.
Close a shared tab.
No parameter schema on file.
Go to a URL in a shared tab, or go back, forward or reload.
No parameter schema on file.
Read the page as an outline of headings, text and interactive elements. Each element you can act on has a ref like [e14]. Take a snapshot before acting and use the refs in click, type and fill_form.
No parameter schema on file.
Get the visible text of the page, or of one element, as plain text. Good for reading articles, tables and results.
No parameter schema on file.
Click an element.
No parameter schema on file.
Move the pointer over an element, e.g. to open a menu.
No parameter schema on file.
Fill several fields at once. Text fields take a string, checkboxes and radios take true or false, selects take the option label or value.
No parameter schema on file.
Choose one or more options in a select element, by label or value.
No parameter schema on file.
Press a key, optionally on an element. Examples: "Enter", "Escape", "Tab", "ArrowDown", "Control+a".
No parameter schema on file.
Scroll an element into view, or scroll the page by a number of pixels.
No parameter schema on file.
Wait until some text appears or disappears, or for a number of milliseconds.
No parameter schema on file.
Take a screenshot of the visible part of a shared tab. The tab is brought to the front first.
No parameter schema on file.
Run JavaScript in the page's own context (page globals are visible) and return the result of the last expression, awaited if it is a promise. Works on sites with a strict CSP. Use for reading data the outline does not show or driving page APIs directly.
No parameter schema on file.
Attach local files to a file input, as if the user picked them.
No parameter schema on file.
Watch a page and notify the user when something they care about happens ("tell me when the price drops below 2000", "when results are posted"). The browser fetches the page on a schedule with the user's cookies. mode=fetch (default) loads the URL without rendering it, so point it at the JSON API…
No parameter schema on file.
List watchers with their last result.
No parameter schema on file.
Run a watcher now and return what its check produced. Set notify to true to send the notification if it fires; by default this is a dry run that still records the value as the new baseline.
No parameter schema on file.
Delete a watcher.
No parameter schema on file.
List the media on a shared tab: images, video and audio (with size, length, playing state), canvases and CSS background images, plus HLS/DASH streams and media files the page loaded (from the network log). Each has an id like m3 for save_media. Streams only appear after the page has requested…
No parameter schema on file.
Save an item from list_media (or any URL) to disk under ~/.tether/media/<site>/, using the browser's cookies. Handles normal files, blob: and data: URLs, canvases, and HLS/DASH streams (through ffmpeg). Returns the file path.
No parameter schema on file.
Get the current frame of a video on a shared tab as an image. Falls back to a cropped screenshot when the site doesn't allow reading the video.
No parameter schema on file.
After clicking something that downloads a file (an invoice, a CSV export, a PDF), wait for it to finish and get its path on disk. Downloads that started in the last 15 seconds count, so call it right after the click.
No parameter schema on file.
Download a URL through the user's browser, with their cookies, and get the saved file's path. Limited to sites of shared tabs unless bypass mode is on.
No parameter schema on file.
List files downloaded while tabs were shared with you (not the user's whole download history).
No parameter schema on file.
Hand a shared tab to the user and wait for them. With message, the page shows it with a Done button and brings the tab to the front: use it for CAPTCHAs, 2FA codes, logins, payment confirmation or any choice that is theirs. Without message, it waits for the user to resume a tab they paused…
No parameter schema on file.
Start working in the user's own browser (their logins and cookies) when no tab is shared yet. mode=window (default) opens a separate window for you, so the user's tabs are left alone; every tab you open in it is yours. mode=current asks to use the tab the user is looking at, for tasks about the…
No parameter schema on file.
Finish a session you started: closes the window start_session opened for you (all of them if you don't name one). With tab, stops using that shared tab instead, leaving it open for the user.
No parameter schema on file.
Ask the user for bypass mode, which gives you every open tab in the browser instead of only the shared ones. The browser shows the user a prompt with your reason and waits up to two minutes for an answer. Only ask when the task needs other tabs.
No parameter schema on file.
List network requests made by a shared tab since it was shared (newest last): id, method, status, type, time, size, URL. Use network_request with an id to see headers and bodies.
No parameter schema on file.
Show one captured request in full: request and response headers, request body and response body.
No parameter schema on file.
Read console output and uncaught errors from a shared tab since it was shared.
No parameter schema on file.
List the cookies the browser would send to the tab's current page, including httpOnly ones.
No parameter schema on file.
List the user's userscripts: ones you saved and ones they imported. They live in ~/.tether/scripts as .user.js files, appear in the Tether popup on matching sites, and work unchanged in Tampermonkey or Violentmonkey.
No parameter schema on file.
Save a reusable userscript. code is the body of a function: plain JavaScript with full DOM access in the page, no imports; use return to hand a result back to run_script. These GM_ APIs work in Tether and in Tampermonkey: GM_addStyle, GM_getValue, GM_setValue, GM_deleteValue, GM_listValues,…
No parameter schema on file.
Read a saved script, to change it. Returns the editable body for scripts you saved, or the whole file for imported ones.
No parameter schema on file.
Run a saved script in a shared tab and return its result.
No parameter schema on file.
Install a userscript (.user.js) or user style (.user.css) from a URL, such as Greasy Fork, OpenUserJS or userstyles.world, or from pasted text. It is saved unchanged. @require'd libraries and style preprocessors (Stylus, Less) are not supported.
No parameter schema on file.
Read change requests the user sent from the Tether popup: what they want changed on a site, often with reference images (screenshots, mockups, mood boards). The tab they sent it from is shared with you. Handle open requests, then call resolve_request.
No parameter schema on file.
Mark a change request done and leave a short reply the user sees in the popup (what you changed, and how to turn it off).
No parameter schema on file.
Preview CSS on a shared tab without saving it. Each call replaces the previous preview on that tab; navigation clears it. Check the result with screenshot, then save_style.
No parameter schema on file.
Remove the CSS preview from a tab.
No parameter schema on file.
Save CSS that restyles a site on every visit, in every connected browser. It is stored as a UserCSS file (~/.tether/styles/<id>.user.css) that also installs unchanged in Stylus. It shows in the popup on matching pages, where the user can switch it off. Saving an existing name replaces it and bumps…
No parameter schema on file.
List saved site styles, yours and imported ones.
No parameter schema on file.
Read a saved style, to change it. Returns the editable CSS for styles you saved, or the whole UserCSS file for imported ones.
No parameter schema on file.
Delete a saved style.
No parameter schema on file.
List sites Tether has recorded the user using (clicks, typing, pages, API calls), and sites with saved notes.
No parameter schema on file.
Summarise everything recorded for a site: its pages, the buttons and links the user actually uses on each (with CSS selectors), the fields they fill, the API endpoints behind it, common paths between pages, and saved notes. Pass page for one page in detail including its last outline. Read this…
No parameter schema on file.
List recorded sessions for a site, or read one session's timeline step by step.
No parameter schema on file.
Read or write notes about a site that persist for future sessions and other agents: how things work, where things are, gotchas. Without text it reads them.
No parameter schema on file.
Delete a saved script.
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Tether or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.3.5. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Tether can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.