Contractor License Lookup MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token, required to call the actor. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lookup_contractor_licensesA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
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.
The single tool name 'lookup_contractor_licenses' follows a clear verb_noun pattern. With only one tool, consistency is trivially perfect.
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.
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.