Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

UK Subcontractor Right to Work Checker

REMOTE · SUBCONTRACTOR-CHECK.NEROLABS.WORKERS.DEV

Does a UK business have to right-to-work check a subcontractor or gig worker from 1 Oct 2026? Free.

0 this week 80 Trust /100

Last scanned (15 hours ago)

Scores higher than 77% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 263 tokens (~131/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Oct 26 0
    • Stability: 0.97 → pass security
  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://subcontractor-check.nerolabs.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=nerolabs.workers.dev CN=YE1,O=Let's Encrypt,C=US 10 Nov 2026 8 Feb 2027 ECDSA 256 ECDSA-SHA384 6de4049323d6abaa327886d7b5c76757b3a
SANs: *.nerolabs.workers.dev, nerolabs.workers.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of subcontractor-check.nerolabs.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://subcontractor-check.nerolabs.workers.dev/mcp Verified 200
http (plaintext) http://subcontractor-check.nerolabs.workers.dev/mcp Inconclusive 405
MCP tools · 2 exposed · ~263 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_subcontractor_right_to_work_duty ~219

UK only. Says whether a business must do a right to work check on a subcontractor, gig worker or platform worker under the rule in force from 1 October 2026 (Border Security, Asylum and Immigration Act 2025, s48), and what to do. Free. General information, not legal advice.

NameTypeReqDescription
contract_holderstring–Who has the contract with the worker: the asking business directly, or one of its subcontractors.
rolestringyesWho is asking: a business taking on self-employed people for its jobs, an app or platform matching workers to customers, an employment agency, or a homeowner hiring a tradesperson.
start_datestring–Date the contract or arrangement with the worker was agreed (entered into), YYYY-MM-DD. Optional.
work_arrangementstring–How the worker works: as an individual (sole trader or worker's contract), through their own limited company, or as an independent business with many customers of its own.

No output schema declared.

No examples provided.

how_to_do_a_right_to_work_check ~44

UK only. Returns the three accepted ways to check someone's right to work, what records to keep and for how long, and the fines. Free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the UK Subcontractor Right to Work Checker MCP server?

UK Subcontractor Right to Work Checker is a hosted endpoint at https://subcontractor-check.nerolabs.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · subcontractor-check.nerolabs.workers.dev

# add to Claude Code
claude mcp add --transport http nero-engine-uk-subcontractor-right-to-work 'https://subcontractor-check.nerolabs.workers.dev/mcp'
Common questions

What is the UK Subcontractor Right to Work Checker MCP server?

UK Subcontractor Right to Work Checker is an MCP server listed in the public MCP registry as io.github.Nero-Engine/uk-subcontractor-right-to-work. Does a UK business have to right-to-work check a subcontractor or gig worker from 1 Oct 2026? Free. This page covers its hosted endpoint (https://subcontractor-check.nerolabs.workers.dev/mcp).

Is the UK Subcontractor Right to Work Checker MCP server safe to use?

UK Subcontractor Right to Work Checker scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the UK Subcontractor Right to Work Checker MCP server expose?

UK Subcontractor Right to Work Checker exposes 2 tools: check_subcontractor_right_to_work_duty, how_to_do_a_right_to_work_check. Their descriptions and schemas cost roughly 263 tokens of context every time the server is loaded.

Does the UK Subcontractor Right to Work Checker MCP server require authentication?

No. We connected to UK Subcontractor Right to Work Checker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the UK Subcontractor Right to Work Checker MCP server still maintained?

UK Subcontractor Right to Work Checker is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the UK Subcontractor Right to Work Checker MCP server?

VerifyMCP ran 12 checks on UK Subcontractor Right to Work Checker, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about UK Subcontractor Right to Work Checker: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.