license-verify-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| verify_licenseA | Verify a contractor's current license or registration status before awarding work, signing a contract, or performing due diligence. Call this tool when you need to:
Currently supports: WA (Washington State) via WA L&I open data (includes real bond + insurance data); CA (California) via CSLB Check-A-License. Call list_supported_jurisdictions first if unsure whether a state is supported. Returns structured JSON with found status, normalized status enum (active|expired|suspended|revoked|unknown), license type, dates, bond/insurance notes, and the raw source record. If business_name matches multiple contractors, a "matches" array (up to 10) is returned instead of a single result. At least one of license_number or business_name must be provided. |
| list_supported_jurisdictionsA | List all US states (jurisdictions) supported by this contractor license verification server, with their data source and availability status. Call this tool when:
Returns an array of jurisdictions with code, full name, source, and status (live or coming_soon). |
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 2 tools
The two tools have clearly distinct purposes: one lists supported jurisdictions, the other verifies a contractor's license. No overlap in functionality, making selection unambiguous.
Both tools follow a consistent verb_noun pattern: list_supported_jurisdictions and verify_license. The naming is clear and predictable.
With only 2 tools, the server feels minimal. While the scope is narrow, a typical license verification server might include additional tools like get_license_details or search_business_by_name.
The tool set covers the core workflow: listing available jurisdictions and verifying a license. Minor gaps exist, such as no tool to retrieve a specific jurisdiction's details or support for other license types.