Skip to main content
Glama
Noquarter6

contractor-license-mcp-server

by Noquarter6
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to contractor-license-mcp-server

No user-submitted related servers found.

    Related Servers

    • LicenseGround MCP Server

      bdzgroup12
      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

    • license-verify-mcp

      lmaniraruta
      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
      58 npm
      MIT
    • BizVerify MCP Server by BizVerify

      BizVerify MCP Serverofficial

      BizVerify
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to verify and search business entities across US state and international company registries, providing real-time confirmation of legal existence, status, and filings.
      9
      MIT
    • LocalPro MCP Server by LocalProDev

      LocalPro MCP Serverofficial

      LocalProDev
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides verified local trade and service business data (e.g., radon mitigation, foundation repair) to AI agents via tools like search_providers and list_niches.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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 issues

    Resources