_ registry / mcp streamable-http · checked 13h ago

progress-watch

https://progress.watch

Registry code: 7e200b1fa12dd54d

api record

Report progress from any script or agent and get notified when it finishes.

from a public catalogue that lists it, not from the operator

endpoint
https://progress.watch/mcp
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 progress-watch live?
Yes — it answered the hub's last check (checked 13h ago). It answered 100% of checks over the last 30 days.
Is progress-watch free to use?
Not measured yet.
What tools does progress-watch have?
4 tools: create_space, create_task, update_task, complete_task.
Is progress-watch 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
100%

90 days 100%· all time 100%

latency
327ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 4 tools
4 never probed 0 of 4 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.

  • create_space unknown never probed

    Create a space — the container tasks live in, and what the user opens to watch them. Only call this when no space is configured for this connection and creating a task failed for that reason. If a space is already configured, use it: making a second one splits the user's tasks across two screens they have to add separately. Returns the space uuid and the URL to watch it. Give the user that URL — until they open it, nothing you report is visible to them, and the uuid is the only way back to it.

    mcp-tool

    {
      "type": "object",
      "required": [
        "title"
      ],
      "properties": {
        "icon": {
          "type": "string",
          "description": "One character shown beside the name. An emoji reads best, e.g. \"🌙\"."
        },
        "title": {
          "type": "string",
          "maxLength": 100,
          "description": "What this collection of tasks is for, e.g. \"Nightly builds\". At most 100 characters; longer is cut to 100, the last one an ellipsis."
        }
      }
    }
    arguments 17 lines
  • create_task unknown never probed

    Create a task the user can watch from anywhere while it runs. Call this first in every turn you do any work, reading and answering included, without being asked and however small the work looks: the user connected this server to watch exactly that work, and a turn that reports nothing looks to them like a turn that never happened. Returns a task uuid to report against. If you decompose work into steps, create one child task per step by passing parent_uuid. Nesting is one level only: a child cannot have children. A parent's progress is averaged from its children automatically, so never report progress on a parent yourself. Create the whole tree before starting, then report each step as it happens and complete it when it is actually done — not all of them at the end. A board that stays empty for the whole job and turns green at the finish is worth nothing to whoever is watching it. Keep creating steps as work appears. The tree is a live picture, not a plan you fixed at the start: something you did not foresee gets its own step when you find it, rather than being folded into whichever step is already open. A parent whose bar drops because it gained a step is telling the truth.

    mcp-tool

    {
      "type": "object",
      "required": [
        "title"
      ],
      "properties": {
        "title": {
          "type": "string",
          "maxLength": 200,
          "description": "What this task is doing, in a few words. At most 200 characters; longer is cut to 200, the last one an ellipsis."
        },
        "source": {
          "type": "string",
          "maxLength": 100,
          "description": "What is reporting, e.g. the agent or tool name. At most 100 characters; longer is cut to 100, the last one an ellipsis."
        },
        "space_uuid": {
          "type": "string",
          "description": "Only needed to override the space configured for this connection."
        },
        "parent_uuid": {
          "type": "string",
          "description": "Make this a step of an existing task. One level only."
        }
      }
    }
    arguments 26 lines
  • update_task unknown never probed

    Report progress on a task. Call periodically — every meaningful step, not every loop iteration. Call it once when the work actually begins, too. A task that has been created but never reported reads as "waiting for data", which nobody can tell apart from a reporter that died before its first write. If the step has nothing to count, send current 0 and end 1: that reads as running, and it is honest. `current` and `end` are raw counts, not a percentage: the user sees "1200 of 50000 pages", which tells them something "2.4%" does not. `end` may change as you learn more; send the new number and the bar recalculates. Every call replaces the whole state. Send everything each time — anything you leave out is cleared, not kept. Put a one-line status in values.log; it holds the last line only, not a history. A task uuid is all this needs — it already knows which space it belongs to.

    mcp-tool

    {
      "type": "object",
      "required": [
        "task_uuid"
      ],
      "properties": {
        "end": {
          "type": "number",
          "description": "How much there is in total."
        },
        "values": {
          "type": "object",
          "description": "Flat object of extra numbers or strings, e.g. {\"errors\": 3, \"log\": \"retrying /foo\"}. At most 20 keys of at most 40 characters, or the request is refused with 400. A string is cut to 1000 characters, the last one an ellipsis.",
          "maxProperties": 20
        },
        "current": {
          "type": "number",
          "description": "How much is done so far."
        },
        "task_uuid": {
          "type": "string",
          "description": "The uuid returned by create_task."
        }
      }
    }
    arguments 25 lines
  • complete_task unknown never probed

    Mark a task finished. This is what sends the user's push notification, so call it when the work is actually done — including when it failed, with the failure recorded in values. Call it as part of the step that finishes the work, not in a sweep once everything is done. Closing a whole tree at the end is cheaper for you and leaves the user watching an empty board for the entire job. Nothing finishes a parent for you: complete it once its last step is done. Completing a parent also stops every step under it that is still open, so a job that ends early is closed by completing the parent alone. Those steps show as stopped, not done, with their numbers as they were.

    mcp-tool

    {
      "type": "object",
      "required": [
        "task_uuid"
      ],
      "properties": {
        "values": {
          "type": "object",
          "description": "Final numbers or a closing log line, e.g. {\"status\": \"failed\", \"log\": \"exit 1\"}. Same limits as update_task.",
          "maxProperties": 20
        },
        "task_uuid": {
          "type": "string",
          "description": "The uuid returned by create_task."
        }
      }
    }
    arguments 17 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 7e200b1fa12dd54d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/7e200b1fa12dd54d/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/7e200b1fa12dd54d/badge.svg)](https://brick.blue/agent/7e200b1fa12dd54d?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
80%

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.