Is England Works Watch live?

Yes — it answered the hub's last check (checked 50m ago). It answered 100% of checks over the last 30 days.

Is England Works Watch free to use?

Yes — the hub reached it with no key and no payment.

What tools does England Works Watch have?

5 tools: assess_change_impact, batch_assess_changes, england_works_watch_info, licensing_source_status, list_supported_change_events.

Is England Works 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.

_ registry / mcp + a2a streamable-http · checked 50m ago

England Works Watch

https://england-works-watch-production.up.railway.app

Registry code: ba8cc568aa1647a2

api record

UK Skilled Worker sponsor-compliance change intelligence for employer, HR and HRIS agents. Use for official GOV.UK source freshness, Home Office/UKVI sponsor reporting, supported sponsor change categories, and one-event or batch impact preflight. Supported vocabulary includes absence, salary, role or occupation-code change, work-location or home-working change, delayed starts, stopping sponsorship or worker departure, organisation changes, TUPE transfers, and mergers/takeovers. The public AI edition supports an interactive single-event preflight. Commercial value is concentrated in metered…

endpoint: https://england-works-watch-production.up.railway.app/mcp
door code: 3f62eaf40849d76e
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 England Works Watch live?: Yes — it answered the hub's last check (checked 50m ago). It answered 100% of checks over the last 30 days.
Is England Works Watch free to use?: Yes — the hub reached it with no key and no payment.
What tools does England Works Watch have?: 5 tools: assess_change_impact, batch_assess_changes, england_works_watch_info, licensing_source_status, list_supported_change_events.
Is England Works 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

99.6%

90 days 96.5%· all time 96.9%

latency

60ms

last good check

priced tools

of 5 tools

_ answered our checks, 90 days 773 checks · signed record

2026-10-20 20:30 degraded → live
2026-10-20 19:36 live → degraded· timeout after 20000ms
2026-10-20 09:12 degraded → live
2026-10-20 08:07 live → degraded· timeout after 20000ms
2026-10-12 09:44 degraded → live

_ what it is for

topic: security & compliance compliance & regulation
used for: assess a uk visa sponsor reporting duty
batch check sponsor compliance events
check gov.uk guidance freshness
list supported sponsor change events
takes → gives: text, data → data
tools: 5 reads

_ 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

through this hub

calls served

successful

paid through this hub

0 USDC

what callers paid

_ what it can do 5 tools

3 open 2 never probed 3 of 5 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.

england_works_watch_info reads open 50m ago
Free product information. Use for service scope, what England Works Watch does, pricing, cost, x402 network, payment, MCP endpoint, discovery metadata, or legal-advice disclaimer. Not for source freshness, supported-event lists, or change decisions. See the Example paid result and x402 payment guidance for the paid boundary.

mcp-tool
{ "type": "object", "title": "england_works_watch_infoArguments", "properties": {} }
arguments 5 lines
licensing_source_status reads open 50m ago
Free GOV.UK evidence source status. Use for current guidance, source freshness, stale sources, changed fingerprints, blocking sources, review status, evidence lifecycle, or source coverage. Not for a specific sponsor change decision.

mcp-tool
{ "type": "object", "title": "licensing_source_statusArguments", "properties": {} }
arguments 5 lines
list_supported_change_events reads open 50m ago
Free supported-event list. Use for capability questions such as 'Does this support salary, role and work location changes?' or when asking which sponsor events the tool can handle, which change types/categories are supported, or to list supported events: absence, salary, role or occupation code, work location or home working, delayed start, stopping sponsorship or worker departure, organisation change, TUPE, merger, takeover, or Home Office/UKVI sponsor reporting. Capability/list only; not impact, reporting, or required-action decisions.

mcp-tool
{ "type": "object", "title": "list_supported_change_eventsArguments", "properties": {} }
arguments 5 lines

assess_change_impact reads unknown 11h ago

Paid programmatic single-event change decision for ONE concrete Skilled Worker sponsor event. Use for one event to determine impact, including questions such as 'Does moving one sponsored worker to permanent home working trigger reporting?', whether Home Office/UKVI sponsor reporting is triggered, whether it is AFFECTED/NOT_AFFECTED, what the sponsor must do, what action is required, or required actions. Handles one absence, salary, role or occupation-code, remote/home/work-location, delayed-start, stop-sponsoring/worker-departure, organisation, TUPE, merger, or takeover event. Returns an evidence-linked rationale, required action/deadline fields, and explicit review or missing-input state. For a one-off interactive check, the public AI edition can provide the same class of single-event preflight without x402; use this commercial tool when an agent/runtime requires metered programmatic execution. Payment: x402 Base mainnet USDC; sign buyer-side and retry this same tool with payment metadata. Not for multiple events; use batch_assess_changes instead.

mcp-tool

{
  "type": "object",
  "title": "assess_change_impactArguments",
  "required": [
    "payload"
  ],
  "properties": {
    "payload": {
      "type": "object",
      "examples": [
        {
          "route": "skilled_worker",
          "event_type": "unauthorised_absence",
          "consecutive_working_days": 11
        }
      ],
      "required": [
        "event_type",
        "route"
      ],
      "properties": {
        "route": {
          "enum": [
            "skilled_worker"
          ],
          "type": "string",
          "description": "Visa route for the sponsor-duty decision. V0.1 supports Skilled Worker only; unsupported routes fail closed."
        },
        "reason": {
          "type": "string",
          "description": "Reason for stopping sponsorship or the worker's departure, or the relevant organisation-change reason."
        },
        "direction": {
          "enum": [
            "increase",
            "decrease"
          ],
          "type": "string",
          "description": "Whether the salary change increases or decreases pay."
        },
        "delay_days": {
          "type": "integer",
          "minimum": 0,
          "description": "For worker_start_delay: days after the relevant Skilled Worker start-date trigger."
        },
        "event_type": {
          "enum": [
            "worker_start_delay",
            "unauthorised_absence",
            "unpaid_or_reduced_pay_absence",
            "salary_change",
            "role_change",
            "work_location_change",
            "stop_sponsoring",
            "organisation_change",
            "tupe_transfer",
            "merger_takeover"
          ],
          "type": "string",
          "description": "Sponsor change event category to assess: absence; salary; role or occupation-code change; work-location or home-working change; delayed start; stopping sponsorship or worker departure; organisation change; TUPE transfer; or merger/takeover."
        },
        "change_kind": {
          "type": "string",
          "description": "For organisation_change or TUPE: the specific organisation or transfer change being assessed."
        },
        "change_type": {
          "type": "string",
          "description": "For merger_takeover: merger, takeover, or similar sponsor-organisation change type."
        },
        "hybrid_only": {
          "type": "boolean",
          "description": "For work_location_change: whether work remains hybrid with the main office unchanged."
        },
        "total_weeks": {
          "type": "number",
          "minimum": 0,
          "description": "For unpaid_or_reduced_pay_absence: total weeks of the absence at unpaid or reduced pay."
        },
        "role_eligible": {
          "type": "boolean",
          "description": "For role_change: whether the proposed role is eligible under the Skilled Worker route."
        },
        "new_client_site": {
          "type": "boolean",
          "description": "For work_location_change: whether the worker has a new normal client site."
        },
        "new_main_office": {
          "type": "boolean",
          "description": "For work_location_change: whether the worker has a new normal main office or branch."
        },
        "occasional_only": {
          "type": "boolean",
          "description": "For work_location_change: whether the location change is only occasional and day-to-day."
        },
        "valid_exception": {
          "type": "boolean",
          "description": "For an absence: whether a listed permitted-absence exception is established."
        },
        "duties_unchanged": {
          "type": "boolean",
          "description": "For TUPE or merger/takeover: whether the worker's duties remain unchanged."
        },
        "permanent_remote": {
          "type": "boolean",
          "description": "For work_location_change: whether the worker moves to permanent or full-time home working."
        },
        "compelling_reason": {
          "type": "boolean",
          "description": "For an absence: whether a compelling reason is established under the sponsor-duty rule."
        },
        "same_occupation_code": {
          "type": "boolean",
          "description": "For role_change: whether the new role keeps the same occupation code; occupation-code changes may require a new CoS/application."
        },
        "salary_requirements_met": {
          "type": "boolean",
          "description": "For role_change: whether the proposed role and pay continue to meet applicable salary requirements."
        },
        "consecutive_working_days": {
          "type": "integer",
          "minimum": 0,
          "description": "For unauthorised_absence: consecutive working days absent without authorisation."
        },
        "modern_slavery_identified": {
          "type": "boolean",
          "description": "Whether the worker has been identified as a victim of modern slavery; supplied special circumstances require individual review."
        },
        "employment_conditions_lifted": {
          "type": "boolean",
          "description": "Whether Skilled Worker employment conditions have been lifted; ordinary employment-change rules require individual review in this case."
        },
        "old_entity_continues_trading": {
          "type": "boolean",
          "description": "For merger_takeover: whether the old sponsor entity continues trading after the change."
        },
        "same_salary_option_still_met": {
          "type": "boolean",
          "description": "For salary_change: whether the original Skilled Worker salary option remains met after the change."
        },
        "new_entity_has_relevant_licence": {
          "type": "boolean",
          "description": "For merger_takeover: whether the new entity has the relevant sponsor licence."
        },
        "new_sponsor_has_relevant_licence": {
          "type": "boolean",
          "description": "For TUPE or merger/takeover: whether the receiving sponsor holds the relevant sponsor licence."
        },
        "pre_registration_nurse_or_midwife": {
          "type": "boolean",
          "description": "For salary_change: whether the worker is a pre-registration nurse or midwife covered by the modeled salary branch."
        },
        "revised_salary_meets_skilled_worker": {
          "type": "boolean",
          "description": "For salary_change: whether the revised salary still meets a Skilled Worker salary basis."
        }
      },
      "description": "One structured Skilled Worker sponsor-change event. Supply the event-specific facts you know; missing required decision facts fail closed rather than being guessed.",
      "additionalProperties": true
    }
  },
  "additionalProperties": false
}

arguments 162 lines

batch_assess_changes reads unknown 11h ago

Primary paid batch/multiple-event decision path for 1-25 events. Use for a list, batch, set, several, many, multiple, 5, 8, 20 or other collection of sponsor changes; assess or evaluate them together in one request and return per-event evidence-linked results plus counts by outcome. Use when the user says 'these changes', 'all changes', 'multiple Skilled Worker events', or asks to batch check several salary, absence, role, location or other sponsor events. This is the main paid API path for repeated HR, HRIS, payroll, recruitment, adviser or agent workflows because it avoids orchestrating many separate interactive checks. Payment: x402 Base mainnet USDC; sign buyer-side and retry this same tool with payment metadata. Not for one event; use assess_change_impact or the public AI edition instead.

mcp-tool

{
  "type": "object",
  "title": "batch_assess_changesArguments",
  "required": [
    "payload"
  ],
  "properties": {
    "payload": {
      "type": "object",
      "required": [
        "changes"
      ],
      "properties": {
        "changes": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "event_type",
              "route"
            ],
            "properties": {
              "route": {
                "enum": [
                  "skilled_worker"
                ],
                "type": "string",
                "description": "Visa route for the sponsor-duty decision. V0.1 supports Skilled Worker only; unsupported routes fail closed."
              },
              "reason": {
                "type": "string",
                "description": "Reason for stopping sponsorship or the worker's departure, or the relevant organisation-change reason."
              },
              "direction": {
                "enum": [
                  "increase",
                  "decrease"
                ],
                "type": "string",
                "description": "Whether the salary change increases or decreases pay."
              },
              "delay_days": {
                "type": "integer",
                "minimum": 0,
                "description": "For worker_start_delay: days after the relevant Skilled Worker start-date trigger."
              },
              "event_type": {
                "enum": [
                  "worker_start_delay",
                  "unauthorised_absence",
                  "unpaid_or_reduced_pay_absence",
                  "salary_change",
                  "role_change",
                  "work_location_change",
                  "stop_sponsoring",
                  "organisation_change",
                  "tupe_transfer",
                  "merger_takeover"
                ],
                "type": "string",
                "description": "Sponsor change event category to assess: absence; salary; role or occupation-code change; work-location or home-working change; delayed start; stopping sponsorship or worker departure; organisation change; TUPE transfer; or merger/takeover."
              },
              "change_kind": {
                "type": "string",
                "description": "For organisation_change or TUPE: the specific organisation or transfer change being assessed."
              },
              "change_type": {
                "type": "string",
                "description": "For merger_takeover: merger, takeover, or similar sponsor-organisation change type."
              },
              "hybrid_only": {
                "type": "boolean",
                "description": "For work_location_change: whether work remains hybrid with the main office unchanged."
              },
              "total_weeks": {
                "type": "number",
                "minimum": 0,
                "description": "For unpaid_or_reduced_pay_absence: total weeks of the absence at unpaid or reduced pay."
              },
              "role_eligible": {
                "type": "boolean",
                "description": "For role_change: whether the proposed role is eligible under the Skilled Worker route."
              },
              "new_client_site": {
                "type": "boolean",
                "description": "For work_location_change: whether the worker has a new normal client site."
              },
              "new_main_office": {
                "type": "boolean",
                "description": "For work_location_change: whether the worker has a new normal main office or branch."
              },
              "occasional_only": {
                "type": "boolean",
                "description": "For work_location_change: whether the location change is only occasional and day-to-day."
              },
              "valid_exception": {
                "type": "boolean",
                "description": "For an absence: whether a listed permitted-absence exception is established."
              },
              "duties_unchanged": {
                "type": "boolean",
                "description": "For TUPE or merger/takeover: whether the worker's duties remain unchanged."
              },
              "permanent_remote": {
                "type": "boolean",
                "description": "For work_location_change: whether the worker moves to permanent or full-time home working."
              },
              "compelling_reason": {
                "type": "boolean",
                "description": "For an absence: whether a compelling reason is established under the sponsor-duty rule."
              },
              "same_occupation_code": {
                "type": "boolean",
                "description": "For role_change: whether the new role keeps the same occupation code; occupation-code changes may require a new CoS/application."
              },
              "salary_requirements_met": {
                "type": "boolean",
                "description": "For role_change: whether the proposed role and pay continue to meet applicable salary requirements."
              },
              "consecutive_working_days": {
                "type": "integer",
                "minimum": 0,
                "description": "For unauthorised_absence: consecutive working days absent without authorisation."
              },
              "modern_slavery_identified": {
                "type": "boolean",
                "description": "Whether the worker has been identified as a victim of modern slavery; supplied special circumstances require individual review."
              },
              "employment_conditions_lifted": {
                "type": "boolean",
                "description": "Whether Skilled Worker employment conditions have been lifted; ordinary employment-change rules require individual review in this case."
              },
              "old_entity_continues_trading": {
                "type": "boolean",
                "description": "For merger_takeover: whether the old sponsor entity continues trading after the change."
              },
              "same_salary_option_still_met": {
                "type": "boolean",
                "description": "For salary_change: whether the original Skilled Worker salary option remains met after the change."
              },
              "new_entity_has_relevant_licence": {
                "type": "boolean",
                "description": "For merger_takeover: whether the new entity has the relevant sponsor licence."
              },
              "new_sponsor_has_relevant_licence": {
                "type": "boolean",
                "description": "For TUPE or merger/takeover: whether the receiving sponsor holds the relevant sponsor licence."
              },
              "pre_registration_nurse_or_midwife": {
                "type": "boolean",
                "description": "For salary_change: whether the worker is a pre-registration nurse or midwife covered by the modeled salary branch."
              },
              "revised_salary_meets_skilled_worker": {
                "type": "boolean",
                "description": "For salary_change: whether the revised salary still meets a Skilled Worker salary basis."
              }
            },
            "additionalProperties": true
          },
          "maxItems": 25,
          "minItems": 1,
          "description": "1-25 structured Skilled Worker sponsor-change events."
        }
      },
      "additionalProperties": false
    }
  },
  "additionalProperties": false
}

arguments 169 lines

_ try it over mcp 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.

Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
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.
Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id ba8cc568aa1647a2.

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

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/ba8cc568aa1647a2/badge.svg)](https://brick.blue/agent/ba8cc568aa1647a2?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 knowoff the mcp door

card completeness

90%

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

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.