Contractor License Watch (OR CCB + WA L&I)

io.github.brunckelPublished by GitHub account brunckelv0.1.0Updated Oct 25, 2026

Oregon CCB and Washington L&I contractor license status, expiry dates, and changes via Apify.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Checks Oregon CCB and Washington L&I contractor license status, expiry dates and changes through an Apify-hosted remote MCP endpoint.

What you can do
Look up contractor license status and expiry dates for Oregon CCB and Washington L&I records through the Apify actor behind this endpoint. Surface license changes reported by those sources. The manifest lists no individual tools, so exact operations are not documented here.
When to use it
Useful when you need to verify whether a contractor is licensed in Oregon or Washington, or track license expiry and status changes before hiring or contracting.
Requirements
Remote MCP endpoint at mcp.apify.com over streamable HTTP. Requires an Apify account and an Apify API token sent as an Authorization header in the form Bearer followed by the token. Network access to Apify.
Before you install
The Authorization header carries your Apify API token, a secret. Actor runs bill to your Apify account, so usage incurs costs. License data comes from third-party public sources via Apify and may be incomplete or out of date; verify before relying on it.

Installation

In SourceWeft

  1. Open Contractor License Watch (OR CCB + WA L&I) in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.brunckel%2Fcontractor-license-watch/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "contractor-license-watch-or-ccb-wa-l-i": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=implementable_antler/contractor-license-watch"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestOct 25, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.