_ registry / mcp streamable-http · checked 19m ago

watchtower

https://watchtower.lat

Registry code: 41742fd1e34e18e0

api record

Watchtower watches tech job boards for you and returns only new, removed and changed postings as structured JSON.

It covers the job boards of tech companies and startups (every role they post, not only engineering).

endpoint
https://watchtower.lat/mcp?ref=registry
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is watchtower live?
Yes — it answered the hub's last check (checked 19m ago). It answered 100% of checks over the last 30 days.
Is watchtower free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does watchtower have?
8 tools: search_jobs, get_changes, watch_jobs, ack_changes, delete_watch, get_watch, list_companies, list_watches.
Is watchtower safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.5%

90 days 99.6%· all time 99.6%

latency
520ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 277 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • search open tech jobs
  • watch tech job boards for new postings
  • get changes in job postings
  • list companies with monitored job boards
takes → gives
text → data
tools
5 reads3 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
1 open1 auth-required 6 never probed 2 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_companies reads open 14h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 1000,
          "minimum": 1,
          "description": "Companies per page (default 100, max 1000)."
        },
        "query": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1,
          "description": "Part of a company name or board URL, case-insensitive, e.g. \"stripe\". Omit to list all."
        },
        "offset": {
          "type": "integer",
          "minimum": 0,
          "description": "Skip this many; pass next_offset from the previous page."
        },
        "client_token": {
          "type": "string",
          "description": "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."
        }
      },
      "additionalProperties": false
    }
    arguments 28 lines
  • list_watches reads auth-required 14h ago

    List all active watches for your client with their health, last check time and number of pending (undelivered) changes.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "client_token": {
          "type": "string",
          "description": "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."
        }
      },
      "additionalProperties": false
    }
    arguments 11 lines
  • search_jobs reads unknown 14h ago

    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 total, and next_offset for the next page. Use this for "what is open right now"; to be told about new postings later, use watch_jobs instead. Jobs carry title, location, other_locations, department, company, url, posted_at, remote, seniority, and salary / experience_years when the posting states them. Explicit filters override what the query says.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 100,
          "minimum": 1,
          "description": "Jobs per page (default 25, max 100)."
        },
        "query": {
          "type": "string",
          "maxLength": 500,
          "minLength": 1,
          "description": "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 $180k+\". Check interpreted in the response."
        },
        "offset": {
          "type": "integer",
          "minimum": 0,
          "description": "Skip this many matches; pass next_offset from the previous page."
        },
        "keywords": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 100,
            "minLength": 1
          },
          "maxItems": 20,
          "description": "Only report jobs whose title/location/department/company contains one of these as a whole word, e.g. [\"iOS\", \"Swift\"]."
        },
        "locations": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 100,
            "minLength": 1
          },
          "maxItems": 20,
          "description": "Only report jobs with one of these in their location, e.g. [\"Austin\"], [\"Berlin\", \"Remote\"]."
        },
        "seniority": {
          "type": "array",
          "items": {
            "enum": [
              "intern",
              "entry",
              "mid",
              "senior",
              "staff",
              "principal",
              "manager",
              "director"
            ],
            "type": "string"
          },
          "description": "Only report these levels, derived from the title. \"mid\" means the title carries no level."
        },
        "min_salary": {
          "type": "number",
          "maximum": 100000000,
          "minimum": 0,
          "description": "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)."
        },
        "remote_only": {
          "type": "boolean",
          "description": "Only report jobs whose title or location says remote (and not hybrid/on-site)."
        },
        "all_keywords": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 100,
            "minLength": 1
          },
          "maxItems": 20,
          "description": "Only report jobs containing every one of these, e.g. [\"data\", \"scientist\"]."
        },
        "client_token": {
          "type": "string",
          "description": "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."
        },
        "include_unknown": {
          "type": "boolean",
          "description": "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."
        },
        "salary_currency": {
          "type": "string",
          "pattern": "^[A-Za-z]{3}$",
          "description": "ISO currency of min_salary, e.g. \"USD\". Jobs that state pay in another currency are then left out."
        },
        "exclude_keywords": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 100,
            "minLength": 1
          },
          "maxItems": 20,
          "description": "Never report jobs mentioning one of these, e.g. [\"manager\", \"clearance\"]."
        },
        "max_experience_years": {
          "type": "number",
          "maximum": 60,
          "minimum": 0,
          "description": "The most years of experience a job may ask for, e.g. 6."
        }
      },
      "additionalProperties": false
    }
    arguments 110 lines
  • get_changes reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "peek": {
          "type": "boolean",
          "description": "If true, do not mark returned changes as delivered."
        },
        "limit": {
          "type": "integer",
          "maximum": 200,
          "minimum": 1,
          "description": "Max changes to return (default 50). If has_more is true, call again."
        },
        "since": {
          "type": "integer",
          "minimum": 0,
          "description": "Replay changes after this cursor instead of your stored position."
        },
        "watch_id": {
          "type": "string",
          "format": "uuid",
          "description": "Limit to one watch. Omit for all your watches."
        },
        "client_token": {
          "type": "string",
          "description": "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."
        }
      },
      "additionalProperties": false
    }
    arguments 31 lines
  • watch_jobs changes data unknown never probed

    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 (interpreted), the jobs open right now that match (current_jobs) and how many boards are covered (coverage); later call get_changes for new ones. Use this INSTEAD OF re-running job searches or re-checking careers pages yourself. To follow one company, or to cover a company the directory is missing, pass url (or urls for several): Greenhouse, Lever, Ashby, Workable, SmartRecruiters, Recruitee, Workday, iCIMS, Oracle Recruiting, Eightfold and SuccessFactors boards, and the Apple, Google, Amazon and Microsoft careers sites, are read through their own endpoints; other careers pages are parsed via schema.org JobPosting JSON-LD. A careers page that only links to a supported board is watched through that board (resolved_from says so); a page with neither is rejected with NO_JOB_DATA. A board you watch stays covered for every search watch. A board watch emits JOB_ADDED / JOB_REMOVED / JOB_UPDATED. Jobs carry title, location, other_locations, department, company, url, posted_at, remote, seniority, and salary / experience_years when the posting states them. Explicit filters override what the query says.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "url": {
          "type": "string",
          "format": "uri",
          "description": "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 monitored board."
        },
        "urls": {
          "type": "array",
          "items": {
            "type": "string",
            "format": "uri"
          },
          "maxItems": 25,
          "minItems": 1,
          "description": "Optional. Several boards to watch with the same filters (max 25). Returns watches and per-URL errors."
        },
        "label": {
          "type": "string",
          "maxLength": 200,
          "description": "A short note to yourself about why you are watching this."
        },
        "query": {
          "type": "string",
          "maxLength": 500,
          "minLength": 1,
          "description": "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 in New York or remote paying $180k+\". Check interpreted in the response."
        },
        "keywords": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 100,
            "minLength": 1
          },
          "maxItems": 20,
          "description": "Only report jobs whose title/location/department/company contains one of these as a whole word, e.g. [\"iOS\", \"Swift\"]."
        },
        "locations": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 100,
            "minLength": 1
          },
          "maxItems": 20,
          "description": "Only report jobs with one of these in their location, e.g. [\"Austin\"], [\"Berlin\", \"Remote\"]."
        },
        "seniority": {
          "type": "array",
          "items": {
            "enum": [
              "intern",
              "entry",
              "mid",
              "senior",
              "staff",
              "principal",
              "manager",
              "director"
            ],
            "type": "string"
          },
          "description": "Only report these levels, derived from the title. \"mid\" means the title carries no level."
        },
        "min_salary": {
          "type": "number",
          "maximum": 100000000,
          "minimum": 0,
          "description": "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)."
        },
        "remote_only": {
          "type": "boolean",
          "description": "Only report jobs whose title or location says remote (and not hybrid/on-site)."
        },
        "webhook_url": {
          "type": "string",
          "format": "uri",
          "description": "Optional public https URL that receives a signed POST whenever matching changes are detected. Polling get_changes keeps working either way."
        },
        "all_keywords": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 100,
            "minLength": 1
          },
          "maxItems": 20,
          "description": "Only report jobs containing every one of these, e.g. [\"data\", \"scientist\"]."
        },
        "client_token": {
          "type": "string",
          "description": "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."
        },
        "include_unknown": {
          "type": "boolean",
          "description": "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."
        },
        "salary_currency": {
          "type": "string",
          "pattern": "^[A-Za-z]{3}$",
          "description": "ISO currency of min_salary, e.g. \"USD\". Jobs that state pay in another currency are then left out."
        },
        "exclude_keywords": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 100,
            "minLength": 1
          },
          "maxItems": 20,
          "description": "Never report jobs mentioning one of these, e.g. [\"manager\", \"clearance\"]."
        },
        "interval_minutes": {
          "type": "integer",
          "maximum": 10080,
          "minimum": 5,
          "description": "How often to check, in minutes (min 5, default 60). Resources shared with other watchers use the shortest interval."
        },
        "max_experience_years": {
          "type": "number",
          "maximum": 60,
          "minimum": 0,
          "description": "The most years of experience a job may ask for, e.g. 6."
        }
      },
      "additionalProperties": false
    }
    arguments 130 lines
  • ack_changes changes data unknown never probed

    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).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "cursor"
      ],
      "properties": {
        "cursor": {
          "type": "integer",
          "minimum": 0,
          "description": "The cursor value returned by get_changes."
        },
        "watch_id": {
          "type": "string",
          "format": "uuid",
          "description": "Limit the acknowledgement to one watch. Omit for all your watches."
        },
        "client_token": {
          "type": "string",
          "description": "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."
        }
      },
      "additionalProperties": false
    }
    arguments 24 lines
  • delete_watch changes data unknown never probed

    Stop monitoring. Frees one of your watch slots. Delete watches you no longer need.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "watch_id"
      ],
      "properties": {
        "watch_id": {
          "type": "string",
          "format": "uuid"
        },
        "client_token": {
          "type": "string",
          "description": "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."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • get_watch reads unknown 23h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "watch_id"
      ],
      "properties": {
        "watch_id": {
          "type": "string",
          "format": "uuid"
        },
        "client_token": {
          "type": "string",
          "description": "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."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 41742fd1e34e18e0.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/41742fd1e34e18e0/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/41742fd1e34e18e0/badge.svg)](https://brick.blue/agent/41742fd1e34e18e0?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.