MCP.Market

t3-watch MCP server

by lfglabs.ai·ai.lfglabs/t3-watch·v0.6.0

An agent on call for the things nobody watches. Checks run free; your agent wakes only on a change.

A88/100grade A
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
Growing

0 stars577 downloads/wk

Reviews

Write one

Nobody has reviewed t3-watch yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

t3-watch tools (18, 2 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • watch_alerts

    Where change events go, if anywhere.

  • watch_apply

    Applies the last scan: turns on the listed checks (or every suggested one) and removes the listed keys by access key.

  • watch_check

    One check's definition, recent runs with evidence, notes and changes. Use it to investigate.

  • watch_decide_draft

    Approves or discards a draft. Only the Watch view calls this, on the person's click.

  • watch_draft_check

    Drafts a check. Watch validates it and runs it once; it stays a draft until the person turns it on. Kinds and config: - http: { url, expectStatus?, contains? } - github: { repo: "owner/name", branch?, workflow?, maxAgeSeconds? } (maxAgeSeconds needs workflow and also fails when that workflow's newest successful run is older, for scheduled workflows) - aws_metric: { profile?, region, namespace, met

  • watch_draft_vendor

    Drafts a vendor description (JSON) so Watch can recognise and check a new API-key vendor. Validated, tested with a stored key when there is one, and kept as a draft until the person approves it.

  • watch_note

    Leaves a short note on a check (or on Watch as a whole), shown on Home next to it. Use it for what you found.

  • watch_runs

    Recent runs of one check, for the Watch view.

  • watch_scanwrite action

    Runs setup: reads the repositories under the folders and the logins the person allowed on the page (see watch_sources), stores working keys, proposes checks and runs each once. Refuses until the person has chosen. Takes about half a minute.

  • watch_set_alerts

    Sets where Watch sends a change event (one POST per check that starts or stops failing): normally a T3 webhook task URL. Pass url null to stop. Watch signs each body in X-Watch-Signature with the secret the person made on the page; this tool never takes a secret.

  • watch_set_check

    Turns a check on, pauses it, snoozes it until a time, resumes it, or runs it now.

  • watch_set_product

    Names the product a service belongs to on Home, for when Watch's guess from names is wrong, such as a site whose repository has another name. A site or repository with no product of its own joins a named product whose name matches its own, and a repository follows the site it matches. Names compare without case, accents or punctuation; a product has one spelling, so naming it in a new one respells

  • watch_sign_in_link

    Makes a link that signs a browser in to the Watch page. It works once, within … minutes. Make one only when the person asks to open the page, and give it only to them.

  • watch_sources

    What setup may read: the folders, each with how many repositories it holds, and the logins (the GitHub CLI, AWS CLI profiles, keys in .env files), each with whether it is on this machine and allowed. The person changes this on the page, before a scan.

  • watch_start_scan

    Starts setup in the background, for the Watch view.

  • watch_state

    The full state for the Watch view.

  • watch_status

    What is broken, what could not run, drafts waiting, and how many checks pass.

  • watch_test_alertwrite action

    Sends one test alert, signed when a secret is set, to the webhook Watch's alerts go to, and says whether the webhook accepted it. It wakes the thread that webhook is bound to, once. Use it right after watch_set_alerts, and when the person asks whether alerts work.

Public scan report

scanner v0.1.10 · 2026-10-24 · same rubric, same numbers if you re-run it

no findings
  • Code scan63 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identitynamespace and repository owner differ; GitHub account older than a year5/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How t3-watch compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 80% of 4,460 AI and agents servers
Tools
18
the typical AI and agents server has 6
Tools that change things
11%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
577
more than 88% of 1,538 AI and agents servers with a package

What its tools let an agent do: 16 read · 2 change

Release history: 2 versions in the registry since 2026-10-23, latest 2026-10-24, typically one every 1 day.

Install t3-watch in Claude Code, Cursor or VS Code

Runs npx -y @lfg-labs/t3-watch on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add t3-watch -- npx -y @lfg-labs/t3-watch
Add to Cursor

What the publisher says

From the t3-watch repository's README, as published. We do not edit it. Read it on GitHub

t3-watch

An agent on call for the things nobody watches. Checks run free; your agent wakes only when something changes.

Watch keeps an eye on the systems you run: CI, cloud accounts, API keys, URLs and scheduled jobs. It sets itself up from the projects and logins already on your machine, and runs its checks as plain code on its own clock, so they spend no model tokens.

Turn on, Pause and Add key. Keys are pasted here, never in chat. Details edits a check's name, how often it runs and its settings, and deletes one; a deleted check keeps its history and can be restored.

  • The page is for knowing and deciding: what's broken, what's waiting for you, and one-click

(or any MCP client) investigates failures, writes new checks and shows the page inline.

  • The chat is for understanding and authoring. A "Watch" thread in T3 Code

The demo in 60 seconds, recorded from npx @lfg-labs/t3-watch demo with its sample data. Click it for the sharper MP4, which GitHub hands over as a download.

Website · MCP Registry

Try it first

npx @lfg-labs/t3-watch demo

With Node 24 or newer, the demo runs a Watch with sample checks on this machine and prints a sign-in link for its page. Every check and alert in it gets a canned answer, and it neither scans nor takes keys, so it reaches none of your accounts and sends nothing off the machine. Signing in to it leaves your own Watch signed in. Ctrl-C stops it and removes it. The video and the screenshots here come from it.

Install

Watch needs Node 24 or newer, on a machine that stays on.

npm install -g @lfg-labs/t3-watch
t3-watch install

install runs Watch in the background at login (systemd on Linux, launchd on macOS), adds its MCP server to Codex and Claude Code, and prints a sign-in link for the page. A sign-in link works once, within 10 minutes, so a copy left in a terminal, a log or a chat is useless after use. For each other browser, t3-watch url prints a new one, or ask your Watch thread for the page. A browser gets its own session, never the access token agents use, and t3-watch signout signs every browser out while agents keep working.

T3 Code can run several accounts for one provider, each in its own home. t3-watch install --all also adds Watch's MCP server to every enabled Claude Code and Codex home in T3's settings, so a Watch thread works on any account, and t3-watch uninstall --all takes it out of them again.

To run from a checkout instead, clone this repository, run pnpm install && pnpm build, then node bin/t3-watch.js install.

On Linux, loginctl enable-linger $USER keeps it running while you're logged out.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

t3-watch: common questions

Is t3-watch MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the t3-watch safety report
How do I install t3-watch?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does t3-watch need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is t3-watch maintained?
The last commit was 11 days ago (2026-10-24). The latest release is v0.6.0.
What can I use instead of t3-watch?
Servers from other publishers that do the same job: Claude Real Video MCP server, Power BI Authoring MCP Server (Local) and Watch Skill MCP server.
How does t3-watch compare with other AI and agents MCP servers?
safety score 88/100 (higher than 80% of 4,460 AI and agents servers); tools 18 (the typical AI and agents server has 6); tools that change things 11% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to t3-watch

Same job from other publishers: the closest match first, then the best rated.

  • Claude Real Video
    Let any LLM watch a video locally — and search everything it has ever watched.
    A
  • Power BI Authoring MCP Server (Local)
    The Power BI Authoring MCP server lets an AI agent create and change Power BI semantic models.
    A
  • Watch Skill
    Watch video and live sessions, keep timestamped evidence, and verify an agent's own work.
    B
  • Kiln
    Spawn an object into existence: describe it, and your agent designs it, checks it, and 3D prints it.
    B
  • Vibe Check
    Metacognitive AI agent oversight: adaptive CPI interrupts for alignment, reflection and safety
    B