Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.lmaniraruta/license-verify-mcp

NPM · LICENSE-VERIFY-MCP

Verify US contractor license + surety bond + insurance from official state data. WA live, CA beta.

Available components

0 this week 81 Trust /100

Last scanned (23 hours ago)

Scores higher than 69% of npm servers

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security90
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects basic-ftp 5.3.1, reached via apify > apify-client > proxy-agent > pac-proxy-agent > get-uri > basic-ftp. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 74 of 258 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 468 tokens (~234/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 13 Nov 26 0
    • CVE-2026-126346 affects this package: high ▼ security
    • CVE-2026-126345 affects this package: high ▼ security
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 5 Nov 26 −3
    • Stability: pass → 0.77 functional
  • 31 Oct 26 0
    • CVE-2026-118764 affects this package: high ▼ security
  • 30 Oct 26 0
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/license-verify-mcp@0.1.3

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 4 findings
ID CVE Severity Vector Fix available
GHSA-5pm8-86m8-9m6r CVE-2026-126345 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-c475-qrg2-pj4r CVE-2026-102990 high yes
GHSA-r4jh-29pc-gfqr CVE-2026-126346 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-g3hv-75wg-m249 CVE-2026-118764 medium yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 258 packages
Packages resolved 258
Deprecated 2
Stale 73
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~468 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
list_supported_jurisdictions ~103

List all US states (jurisdictions) supported by this contractor license verification server, with their data source and availability status. Call this tool when: - You need to check whether a specific state is supported before calling verify_license - You want to display available options to the user - You need the authoritative data source URL for a jurisdiction Returns an array of jurisdictions with code, full name, source, and status (live or coming_soon).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

verify_license ~365

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: - Confirm a contractor is currently licensed and in good standing - Check whether a license is active, expired, suspended, or revoked - Look up a contractor by license/registration number (preferred — exact match) or by business name (partial match, may return multiple) - Retrieve license type, effective and expiration dates from official government records 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.

NameTypeReqDescription
business_namestring–Business name or partial business name to search for. Case-insensitive partial match. May return multiple results if ambiguous — check the 'matches' array in that case.
jurisdictionstringyesTwo-letter US state code. Supported: 'WA' (Washington, via WA L&I open data), 'CA' (California, via CSLB). Call list_supported_jurisdictions to see all options.
license_numberstring–Contractor license or registration number to look up (e.g. 'ECOSTSC758NN'). Case-insensitive exact match. Preferred over business_name for unambiguous results.

No output schema declared.

No examples provided.

Install

How do I install the io.github.lmaniraruta/license-verify-mcp server?

io.github.lmaniraruta/license-verify-mcp runs locally as an npm package, launched with npx -y license-verify-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · license-verify-mcp

# add to Claude Code
claude mcp add lmaniraruta-license-verify-mcp -- npx -y license-verify-mcp
Common questions

What is the io.github.lmaniraruta/license-verify-mcp server?

io.github.lmaniraruta/license-verify-mcp is listed in the public MCP registry as io.github.lmaniraruta/license-verify-mcp. Verify US contractor license + surety bond + insurance from official state data. WA live, CA beta. This page covers its npm package (license-verify-mcp).

Is the io.github.lmaniraruta/license-verify-mcp server safe to use?

io.github.lmaniraruta/license-verify-mcp scores 81 out of 100 on VerifyMCP. We recorded 4 known advisories against it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.lmaniraruta/license-verify-mcp server expose?

io.github.lmaniraruta/license-verify-mcp exposes 2 tools: verify_license, list_supported_jurisdictions. Their descriptions and schemas cost roughly 468 tokens of context every time the server is loaded.

Is the io.github.lmaniraruta/license-verify-mcp server still maintained?

io.github.lmaniraruta/license-verify-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.lmaniraruta/license-verify-mcp server under?

io.github.lmaniraruta/license-verify-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.lmaniraruta/license-verify-mcp server?

VerifyMCP ran 16 checks on io.github.lmaniraruta/license-verify-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.