Skip to main content
Glama
contractor-license-mcp-server

contractor-license-mcp-server

by Noquarter6

Related Servers

Alternatives to contractor-license-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      1
      74 npm
      MIT
    • 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
    • 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
      80 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      1
      50 npm
      MIT

    TDQS

    A4.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues