Contractor Licence Changes
REMOTE · LICENSE-CHANGES-MCP.OTTOBOT2025.WORKERS.DEV · SCANNED SEP 28
Did this contractor's licence change? Observed lapses and reinstatements, not a snapshot.
Available components
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 383 tokens (~191/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Contractor Licence Changes MCP server?
Contractor Licence Changes is a hosted endpoint at https://license-changes-mcp.ottobot2025.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 · license-changes-mcp.ottobot2025.workers.dev
claude mcp add --transport http agency-ottobot-contractor-license-changes 'https://license-changes-mcp.ottobot2025.workers.dev/mcp'
{
"mcpServers": {
"agency-ottobot-contractor-license-changes": {
"url": "https://license-changes-mcp.ottobot2025.workers.dev/mcp"
}
}
} {
"servers": {
"agency-ottobot-contractor-license-changes": {
"type": "http",
"url": "https://license-changes-mcp.ottobot2025.workers.dev/mcp"
}
}
} [mcp_servers.agency-ottobot-contractor-license-changes] url = "https://license-changes-mcp.ottobot2025.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"agency-ottobot-contractor-license-changes": {
"type": "remote",
"url": "https://license-changes-mcp.ottobot2025.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add agency-ottobot-contractor-license-changes --url 'https://license-changes-mcp.ottobot2025.workers.dev/mcp' --transport streamable-http
mcp_servers:
agency-ottobot-contractor-license-changes:
url: "https://license-changes-mcp.ottobot2025.workers.dev/mcp" {
"McpServers": {
"agency-ottobot-contractor-license-changes": {
"Transport": "http",
"Url": "https://license-changes-mcp.ottobot2025.workers.dev/mcp"
}
}
} assistant mcp add agency-ottobot-contractor-license-changes -t streamable-http -u 'https://license-changes-mcp.ottobot2025.workers.dev/mcp'
{
"mcpServers": {
"agency-ottobot-contractor-license-changes": {
"type": "http",
"url": "https://license-changes-mcp.ottobot2025.workers.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 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
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
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 28 Sept 2026 · Probed https://license-changes-mcp.ottobot2025.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=ottobot2025.workers.dev | CN=WE1,O=Google Trust Services,C=US | 9 Aug 2026 | 7 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 3f11fbdb97e1bc7c0e453c60b68f81e3 |
| SANs: ottobot2025.workers.dev, *.ottobot2025.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of license-changes-mcp.ottobot2025.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | 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://license-changes-mcp.ottobot2025.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://license-changes-mcp.ottobot2025.workers.dev/mcp | Inconclusive | 405 |
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 →
check_license_history ~192
Has this contractor's licence changed? Returns every status transition observed in the state board's own published file since 2026-07-17 -- suspensions, expirations, reinstatements and first appearance -- with the date each was seen. This is change over time, not a current-status lookup: use it after a snapshot check, to find out whether the licence you are about to rely on lapsed and came back. Distinguishes 'no change observed' from 'this source is not observed for that change', which are not the same answer. Only public, unsuppressed directory records are returned. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| license_number | string | yes | The licence number as the board prints it |
| state | string | yes | Two-letter state code. Covered: AZ, CA, CO, CT, DE, FL, IA, NV, NY, OR, TX, UT, VA, WA |
No output schema declared.
No examples provided.
recent_license_changes ~191
What changed lately across a state: licences that lapsed, were reinstated, or appeared for the first time, newest first, optionally narrowed to one trade. Answers the monitoring question a single lookup cannot -- which contractors lost standing this month, or who is newly licensed in this trade. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| change_type | string | – | lapse = active to suspended/expired/inactive; new_license = first observed |
| days | integer | – | Look back 1 to 365 days (default 30) |
| limit | integer | – | Max rows, clamped to 1 through 100 (default 25) |
| state | string | yes | Two-letter state code. Covered: AZ, CA, CO, CT, DE, FL, IA, NV, NY, OR, TX, UT, VA, WA |
| trade | string | – | Optional trade filter, e.g. electricians, plumbers |
No output schema declared.
No examples provided.
What is the Contractor Licence Changes MCP server?
Contractor Licence Changes is an MCP server listed in the public MCP registry as agency.ottobot/contractor-license-changes. Did this contractor's licence change? Observed lapses and reinstatements, not a snapshot. This page covers its hosted endpoint (https://license-changes-mcp.ottobot2025.workers.dev/mcp).
Is the Contractor Licence Changes MCP server safe to use?
Contractor Licence Changes scores 68 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 Contractor Licence Changes MCP server expose?
Contractor Licence Changes exposes 2 tools: check_license_history, recent_license_changes. Their descriptions and schemas cost roughly 383 tokens of context every time the server is loaded.
Does the Contractor Licence Changes MCP server require authentication?
No. We connected to Contractor Licence Changes without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Contractor Licence Changes MCP server still maintained?
Contractor Licence Changes is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.