Skip to main content
Glama
mambalabsdev

Contractor License Lookup MCP Server

by mambalabsdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Contractor License Lookup MCP Server

Smithery Glama score MCP Registry npm version npm downloads license mcpservers.org

An MCP server for the Mamba Labs Contractor License Lookup actor on Apify. Give it a state and a trade to list licensed contractors, or a license number or business name to verify one. Each run reads the state licensing board's own public register.

What's Inside

Related MCP server: license-verify-mcp

What it does

Two modes:

  • list: give states and trades (for example CA and roofing), optionally cities or a county. You get one row per licensed contractor with license number, status, expiration date, classifications, owners or qualifying parties, address, and phone.

  • lookup: give lookups, one per line, for example WA | 04CONCL862CR or LA | Acadian Builders. You get the matching license with its status.

States covered: California (CSLB Data Portal lists), Texas (TDLR open data), Washington (Labor and Industries open data), Oregon (CCB open data), and Louisiana (LSLBC public search). California name and number lookups work only inside a trade list, because the CSLB license check page uses a reCAPTCHA. Each search ends with one free summary row. All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config (claude_desktop_config.json), Cursor, or any MCP client:

{
  "mcpServers": {
    "mamba-contractor-license-lookup": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-contractor-license-lookup"
      ],
      "env": {
        "APIFY_TOKEN": "your-apify-token"
      }
    }
  }
}

Restart the client. The lookup_contractor_licenses tool appears.

Prerequisites

Example prompts

  • "List the licensed roofing contractors in San Diego County, California."

  • "Is Washington contractor license 04CONCL862CR active, and who are the principals?"

  • "Find licensed HVAC contractors in Austin, Texas, with their phone numbers."

Tool

lookup_contractor_licenses. One tool. Example arguments:

{
  "mode": "list",
  "states": ["CA"],
  "trades": ["roofing"],
  "county": "San Diego",
  "max_results": "100"
}

Inputs

Every buyer facing input of the actor, unchanged. Omitted inputs take the actor's own defaults. Numbers and booleans are sent as strings.

Input

Type

Description

mode

string

list (default) or lookup

states

array

CA, TX, WA, OR, LA

trades

array

List mode. Trade words

cities

array

List mode. Cities, searched separately

county

string

List mode. County (CA, TX, OR)

business_name

string

List mode: name filter. Lookup mode: one more name

lookups

array

Lookup mode. Lines such as WA | 04CONCL862CR

license_number

string

Lookup mode. One more license number

active_only

string

true or false. Default true

include_owners

string

Washington principals. Default true

max_results

string

Rows per search, up to 5000

max_charge_usd

string

Optional cost cap for the run

proxy_mode

string

auto or residential. Default auto

Pricing

Pay per event on Apify, billed to your Apify account. Prices in USD.

Event

Free plan

Bronze

Silver

Gold

license-row, per license returned

$0.004

$0.0038

$0.0036

$0.0034

apify-actor-start, per run start

$0.0005

$0.0005

$0.0005

$0.0005

Search summary rows, and skipped, blocked, and no result rows, are free.

Your keys

The actor needs no key. It reads the state boards' public registers and holds no key of any kind. Proxy traffic adds nothing to your price: Mamba Labs pays the platform costs of the run. proxy_mode is a reliability setting.

Full actor documentation

apify.com/mambalabs/contractor-license-lookup

License

MIT. See LICENSE.

Available Tools

1 tool
lookup_contractor_licensesLook up contractor licensesA
Read-only

Look up contractor licenses, or list licensed contractors by trade, from the public registers of the California, Texas, Washington, Oregon, and Louisiana state licensing boards. mode list: give states and trades (plumbing, roofing, hvac, electrical, general, and more), optionally cities or a county, and get one row per licensed contractor. mode lookup: give lookups such as WA | 04CONCL862CR or LA | Acadian Builders and get the matching license. Each row carries license number, status, active flag, issue and expiration dates, classifications, owners or qualifying parties, address, phone, and the board source link; each search ends with one free summary row. California name and number lookups are skipped because the CSLB license check page uses a reCAPTCHA. Skipped, blocked, or empty searches come back free with a row_status saying so. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges per license row returned.

NameRequiredDescriptionDefault
modeNolist (default): states and trades in, licensed contractors out. lookup: license numbers or business names in, their licenses out.
citiesNoList mode. Keep contractors in these cities; each city is searched separately.
countyNoList mode. Keep contractors in this county (CA, TX, and OR record county).
statesNoState codes: CA, TX, WA, OR, LA. In lookup mode, used for lines that name no state.
tradesNoList mode. Trade words such as plumbing, electrical, hvac, roofing, general, solar, landscaping, painting, concrete, or pool.
lookupsNoLookup mode. One per line: a state code, a pipe, then a license number or business name, for example WA | 04CONCL862CR or LA | Acadian Builders.
proxy_modeNoauto uses the Apify proxy and moves a refused request to residential addresses; residential uses residential only. A reliability choice; proxy use adds nothing to the price. Default auto.
active_onlyNoKeep only active, unexpired licenses. Default true.
max_resultsNoLicense rows per search, up to 5000. Each license row is billed. Default 100 in list mode, 10 in lookup mode.
business_nameNoList mode: keep only names that contain this text. Lookup mode: one more business name to look up.
include_ownersNoWashington: read the current principals of each license. Default true.
license_numberNoLookup mode. One more license number, searched in states.
max_charge_usdNoOptional. The run stops before any row that would take its charges over this amount.

TDQS

A4.9/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the read-only and open-world annotations, the description discloses authentication requirements, per-row billing, free summary and skipped/blocked/empty rows, error behavior with run IDs, and the California reCAPTCHA limitation. These are material operational traits an agent needs before invoking the tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Although dense, the description is appropriately sized for a 13-parameter tool and is front-loaded with purpose, then modes, then output and caveats. Every sentence adds actionable information; there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description fills the gap by enumerating the returned fields, summary row, row_status behavior, and error format. It also covers authentication, cost, and source limitations, leaving little an agent would need to infer.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already defines all 13 parameters, but the description adds useful operational meaning: lookup line syntax, trade examples, default row limits, billing consequences, proxy cost neutrality, and the max_charge_usd cutoff. It does not need to restate every schema detail, and the added context is valuable.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: look up contractor licenses or list licensed contractors by trade from named state public registers. It clearly distinguishes the two modes, list and lookup, so an agent can tell exactly what the tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly explains when to use mode list, with states and trades, versus mode lookup, with piped state and license/business identifiers. It also warns that California name and number lookups are skipped because of a reCAPTCHA, which prevents a common incorrect attempt.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • First observedlookup_contractor_licenses
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.6/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no possibility of confusing it with another tool. The two modes (list and lookup) are clearly described within the same tool, avoiding cross-tool ambiguity.

Naming Consistency5/5

The single tool name 'lookup_contractor_licenses' follows a clear verb_noun pattern. With only one tool, consistency is trivially perfect.

Tool Count2/5

The server offers exactly one tool, which the rubric explicitly flags as 'too few (1)' for the apparent scope. While the tool is feature-rich with two modes, a single tool for multi-state licensing lookups may feel thin.

Completeness4/5

The tool provides both listing by trade and direct lookup across five states, covering the core read-only use case. However, California name/number lookups are skipped due to reCAPTCHA, and only five states are supported, leaving minor gaps.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • contractor-license-mcp-server

    Noquarter6
    A
    license
    A
    quality
    D
    maintenance
    Real-time contractor license verification across 45 US states. Verifies license status, expiration, and disciplinary history directly against state licensing board portals.
    4
    22 npm
    MIT

  • license-verify-mcp

    lmaniraruta
    A
    license
    A
    quality
    D
    maintenance
    Verifies contractor license status mid-task, returning normalized JSON with active/expired/suspended/revoked status, bond details, and insurance for WA (reliable) and CA (beta) jurisdictions.
    2
    28 npm
    MIT

  • LicenseGround MCP Server

    bdzgroup12
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents and procurement systems to verify contractor licenses against official state boards, search contractors by trade and location, audit workers' comp, surety bonds and OSHA safety records, and check SAM.gov federal debarment status. It returns a deterministic ALLOW/WARN/BLOCK compliance decision plus registry health metrics for US trade contractors.
    MIT