contractor-license-mcp-server
Related Servers
Alternatives to contractor-license-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables listing and verifying licensed contractors across California, Texas, Washington, Oregon, and Louisiana by state, trade, city, county, license number, or business name, returning license status, expiration, classifications, owners, address, and phone.174 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseAqualityDmaintenanceVerifies 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.280 npmMIT
- AlicenseAqualityDmaintenance50-state professional license verification for AI agents.35 npmMIT
- AlicenseAqualityBmaintenanceEnables lookup of licensed US real estate agents on official state license registers by license number or name, returning the brokerage of record along with its active agent count, size band, and the agent's license status and expiry. It also lists every active agent at a given brokerage or every brokerage office in a zip code across 19 states.150 npmMIT
- FlicenseNot gradedqualityCmaintenanceVerifies Texas plumbing contractor licenses in real time from official TSBPE data, supporting lookups by contractor name, license number, and county. It charges $0.05 USDC per paid query using the x402 protocol, with free discovery tools.-
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.