# Contractor Licence Changes (remote · license-changes-mcp.ottobot2025.workers.dev)

Did this contractor's licence change? Observed lapses and reinstatements, not a snapshot.

- Trust score: 68/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `license-changes-mcp.ottobot2025.workers.dev`: 68/100 (this document), [markdown](https://verifymcp.io/servers/agency-ottobot-contractor-license-changes/license-changes-mcp.md), [page](https://verifymcp.io/servers/agency-ottobot-contractor-license-changes/license-changes-mcp)

## Channel facts

- Endpoint: `https://license-changes-mcp.ottobot2025.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.3`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-28.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

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

### Claude

```bash
claude mcp add --transport http agency-ottobot-contractor-license-changes 'https://license-changes-mcp.ottobot2025.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "agency-ottobot-contractor-license-changes": {
      "url": "https://license-changes-mcp.ottobot2025.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "agency-ottobot-contractor-license-changes": {
      "type": "http",
      "url": "https://license-changes-mcp.ottobot2025.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.agency-ottobot-contractor-license-changes]
url = "https://license-changes-mcp.ottobot2025.workers.dev/mcp"
```

### opencode

```json
{
  "$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

```bash
openclaw mcp add agency-ottobot-contractor-license-changes --url 'https://license-changes-mcp.ottobot2025.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  agency-ottobot-contractor-license-changes:
    url: "https://license-changes-mcp.ottobot2025.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "agency-ottobot-contractor-license-changes": {
      "Transport": "http",
      "Url": "https://license-changes-mcp.ottobot2025.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add agency-ottobot-contractor-license-changes -t streamable-http -u 'https://license-changes-mcp.ottobot2025.workers.dev/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 68, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 68, +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.

### 2026-09-25 (score 67, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 66, +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.

### 2026-09-21 (score 65, +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.

### 2026-09-19 (score 64, +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.

### 2026-09-16 (score 63, +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.

### 2026-09-14 (score 62, +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.

## MCP tools (2)

### `check_license_history` (~192 tokens)

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.

Input parameters:

- `license_number` (string, required): The licence number as the board prints it
- `state` (string, required): Two-letter state code. Covered: AZ, CA, CO, CT, DE, FL, IA, NV, NY, OR, TX, UT, VA, WA

### `recent_license_changes` (~191 tokens)

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.

Input parameters:

- `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, required): 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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/agency-ottobot-contractor-license-changes/license-changes-mcp#diagnostics

## Score history

- 2026-09-28: 68
- 2026-09-27: 68
- 2026-09-26: 67
- 2026-09-25: 67
- 2026-09-24: 66
- 2026-09-23: 66
- 2026-09-22: 65
- 2026-09-21: 65
- 2026-09-20: 64
- 2026-09-19: 64
- 2026-09-18: 63
- 2026-09-17: 63
- 2026-09-16: 63
- 2026-09-15: 62
- 2026-09-14: 62
- 2026-09-13: 61
- 2026-09-12: 61
- 2026-09-11: 60
- 2026-09-10: 60
- 2026-09-09: 59
- 2026-09-08: 59
- 2026-09-07: 58

## Common questions

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

## Links

- Remote endpoint: https://license-changes-mcp.ottobot2025.workers.dev/mcp
- Repository: https://github.com/modelcontextprotocol/registry
- Changelog RSS feed: https://verifymcp.io/servers/agency-ottobot-contractor-license-changes/license-changes-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/agency-ottobot-contractor-license-changes/license-changes-mcp.json
- HTML version of this page: https://verifymcp.io/servers/agency-ottobot-contractor-license-changes/license-changes-mcp