contractor-license-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLV_API_KEY | Yes | Your API key from the dashboard | |
| CLV_API_URL | Yes | API backend URL (use https://www.tradesapi.com) |
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 |
|---|---|
| clv_verify_licenseA | Verify a contractor's license by checking the state licensing board portal. Returns license validity, holder name, status, expiration, and any disciplinary actions. |
| clv_batch_verifyA | Verify multiple contractor licenses in a single request (max 25). Returns results for each license, with partial failure handling — individual failures don't block others. |
| clv_list_supported_statesA | List all US states currently supported for contractor license verification, including portal URLs, health status, and available trades. |
| clv_search_by_nameA | Search for contractors by business or individual name in a state licensing database. Returns matching contractors with license numbers, status, and confidence scores. |
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 4 tools
Each tool has a clearly distinct purpose: batch verification, listing supported states, searching by name, and single license verification. There is no overlap in functionality, and an agent can easily differentiate between them based on their specific operations.
All tool names follow a consistent 'clv_' prefix and snake_case pattern (e.g., clv_batch_verify, clv_list_supported_states). This uniformity makes the tools predictable and easy to identify within the server's domain.
With 4 tools, the server is well-scoped for contractor license verification, covering key operations like verification, batch processing, state listing, and name searching. Each tool serves a necessary function without redundancy or bloat.
The tool set provides strong coverage for core verification workflows, including single and batch checks, state support info, and name searches. A minor gap might be the lack of tools for updating or managing license data, but for a verification-focused server, the surface is largely complete.