A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Nothing to run from here
Watchtower 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.
8
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Job alerts for AI agents: describe a role once, get only new postings from 1,500+ tech job boards.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http watchtower-mcp 'https://watchtower.lat/mcp?ref=registry'
# 2 — ask your agent for something these tools do
# watch_jobs, search_jobs, list_companies and 5 more
Watchtower costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
WAAll 1 server
watchtower1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http watchtower-mcp 'https://watchtower.lat/mcp?ref=registry'Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
8 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.
Create a persistent watch for tech jobs. Describe what you want in query ("iOS jobs in Austin making at least 150k a year with a maximum of 6 years of experience") and leave url out: the watch then covers every job board Watchtower monitors (tech companies and startups, whatever platform they use) and reports each new matching posting (JOB_ADDED). The response shows how the query was read (interpr
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | What to watch for, in plain language: role, place, pay, experience, level, remote. E.g. "iOS jobs in Austin making at least 150k a year with a maximum of 6 years of experience", "senior backend roles |
| url | string | no | Optional. Limit the watch to one job board or careers page, e.g. https://boards.greenhouse.io/acme, https://jobs.lever.co/acme, https://acme.wd5.myworkdayjobs.com/Careers. Omit to watch every monitore |
| urls | array | no | Optional. Several boards to watch with the same filters (max 25). Returns watches and per-URL errors. |
| keywords | array | no | Only report jobs whose title/location/department/company contains one of these as a whole word, e.g. ["iOS", "Swift"]. |
| all_keywords | array | no | Only report jobs containing every one of these, e.g. ["data", "scientist"]. |
| exclude_keywords | array | no | Never report jobs mentioning one of these, e.g. ["manager", "clearance"]. |
| locations | array | no | Only report jobs with one of these in their location, e.g. ["Austin"], ["Berlin", "Remote"]. |
| seniority | array | no | Only report these levels, derived from the title. "mid" means the title carries no level. |
| remote_only | boolean | no | Only report jobs whose title or location says remote (and not hybrid/on-site). |
| min_salary | number | no | Yearly pay the job must be able to reach, e.g. 150000. Compared with the top of the posted range (hourly and monthly pay are converted). |
| salary_currency | string | no | ISO currency of min_salary, e.g. "USD". Jobs that state pay in another currency are then left out. |
| max_experience_years | number | no | The most years of experience a job may ask for, e.g. 6. |
| include_unknown | boolean | no | Many postings state no pay or no years of experience. true (default) still reports them, without a salary / experience_years field; false reports only postings that state a qualifying value. |
| webhook_url | string | no | Optional public https URL that receives a signed POST whenever matching changes are detected. Polling get_changes keeps working either way. |
| interval_minutes | integer | no | How often to check, in minutes (min 5, default 60). Resources shared with other watchers use the shortest interval. |
| label | string | no | A short note to yourself about why you are watching this. |
| client_token | string | no | Only if this conversation already uses a Watchtower token (wt_...) from before the app was connected. Otherwise leave it out; never ask the user for one. |
Find the tech jobs open right now that match a request, across every job board Watchtower monitors (tech companies and startups). Describe what you want in query ("iOS jobs in Austin with a maximum of 6 years of experience"). Read-only: nothing is saved and no watch is created, and no token is needed. The response shows how the query was read (interpreted), the matching jobs newest first, the tota
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | What to look for, in plain language: role, place, pay, experience, level, remote. E.g. "iOS jobs in Austin with a maximum of 6 years of experience", "senior backend roles in New York or remote paying |
| keywords | array | no | Only report jobs whose title/location/department/company contains one of these as a whole word, e.g. ["iOS", "Swift"]. |
| all_keywords | array | no | Only report jobs containing every one of these, e.g. ["data", "scientist"]. |
| exclude_keywords | array | no | Never report jobs mentioning one of these, e.g. ["manager", "clearance"]. |
| locations | array | no | Only report jobs with one of these in their location, e.g. ["Austin"], ["Berlin", "Remote"]. |
| seniority | array | no | Only report these levels, derived from the title. "mid" means the title carries no level. |
| remote_only | boolean | no | Only report jobs whose title or location says remote (and not hybrid/on-site). |
| min_salary | number | no | Yearly pay the job must be able to reach, e.g. 150000. Compared with the top of the posted range (hourly and monthly pay are converted). |
| salary_currency | string | no | ISO currency of min_salary, e.g. "USD". Jobs that state pay in another currency are then left out. |
| max_experience_years | number | no | The most years of experience a job may ask for, e.g. 6. |
| include_unknown | boolean | no | Many postings state no pay or no years of experience. true (default) still reports them, without a salary / experience_years field; false reports only postings that state a qualifying value. |
| limit | integer | no | Jobs per page (default 25, max 100). |
| offset | integer | no | Skip this many matches; pass next_offset from the previous page. |
| client_token | string | no | Only if this conversation already uses a Watchtower token (wt_...) from before the app was connected. Otherwise leave it out; never ask the user for one. |
List the companies whose job boards Watchtower monitors, i.e. what search_jobs and watch_jobs without a url cover. Pass query to check whether a company is covered ("stripe"). Each entry has name, board_url (pass it to watch_jobs as url to follow only that company), platform and open_jobs. Read-only, no token needed. If a company is missing, watch its board URL or careers page to add it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Part of a company name or board URL, case-insensitive, e.g. "stripe". Omit to list all. |
| limit | integer | no | Companies per page (default 100, max 1000). |
| offset | integer | no | Skip this many; pass next_offset from the previous page. |
| client_token | string | no | Only if this conversation already uses a Watchtower token (wt_...) from before the app was connected. Otherwise leave it out; never ask the user for one. |
Return job changes detected since your last get_changes call, across all your watches or one watch. This is the cheap replacement for re-browsing careers pages: if it returns an empty list, nothing you care about has changed. By default the cursor advances so each change is delivered once; pass peek=true to look without advancing, or since=<cursor> to replay.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| watch_id | string | no | Limit to one watch. Omit for all your watches. |
| since | integer | no | Replay changes after this cursor instead of your stored position. |
| limit | integer | no | Max changes to return (default 50). If has_more is true, call again. |
| peek | boolean | no | If true, do not mark returned changes as delivered. |
| client_token | string | no | Only if this conversation already uses a Watchtower token (wt_...) from before the app was connected. Otherwise leave it out; never ask the user for one. |
List all active watches for your client with their health, last check time and number of pending (undelivered) changes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_token | string | no | Only if this conversation already uses a Watchtower token (wt_...) from before the app was connected. Otherwise leave it out; never ask the user for one. |
Get a watch with its status and the jobs currently open that match its filters: on its board, or across every monitored board for a watch created without a url. Use this to answer "what is open right now" without searching or fetching careers pages yourself.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| watch_id | string | yes | — |
| client_token | string | no | Only if this conversation already uses a Watchtower token (wt_...) from before the app was connected. Otherwise leave it out; never ask the user for one. |
Mark changes up to a cursor as processed. Use with get_changes(peek=true) for at-least-once delivery: peek, act on the changes, then ack the cursor get_changes returned. Not needed if you call get_changes without peek (that acknowledges automatically).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cursor | integer | yes | The cursor value returned by get_changes. |
| watch_id | string | no | Limit the acknowledgement to one watch. Omit for all your watches. |
| client_token | string | no | Only if this conversation already uses a Watchtower token (wt_...) from before the app was connected. Otherwise leave it out; never ask the user for one. |
Stop monitoring. Frees one of your watch slots. Delete watches you no longer need.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| watch_id | string | yes | — |
| client_token | string | no | Only if this conversation already uses a Watchtower token (wt_...) from before the app was connected. Otherwise leave it out; never ask the user for one. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- 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 Watchtower or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.1.
0.1.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish Watchtower can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.