Ucc Liens

What Ucc Liens MCP server does

The Ucc Liens MCP server provides agent-accessible searches for business-debtor Uniform Commercial Code financing-statement filings. It covers Colorado, Connecticut, and Oregon through public Secretary of State data sources. Results can include filing number, filing type and status, filing and lapse dates, debtor details, secured-party details, and a source URL.

The server exposes two pack-specific tools:

• ucc_search(debtor_name, state, limit?) searches for filings associated with a business debtor name.
• ucc_new_filings(state, since, secured_party?, limit?) returns filings from a specified date onward and can restrict results by a substring in the secured-party name.

These tools can support public-record research, business due diligence, and analysis of recent lender activity. They do not provide consumer reports. Tool descriptions and successful responses include an FCRA notice stating that the information is not for credit, employment, insurance, or housing eligibility decisions.

How it works

The Ucc Liens MCP server queries state-hosted open-data APIs without authentication. Connecticut publishes one row per lien transaction, including originals, amendments, continuations, and releases. Colorado stores filings, debtor records, and secured-party records in separate datasets; the server joins those records in memory using the filing identifier.

Oregon’s source is a rolling dataset covering approximately the last 30 days. The server first identifies organization debtors and then queries corresponding secured-party rows. Consequently, an older Oregon lien may not appear if it has no filing in the current rolling window.

Individual debtors are excluded at query time. Colorado searches require a populated business organization name, Connecticut searches require a business debtor field, and Oregon searches require organization records. Vermont is not supported: both tools return a descriptive error because the available search requires CAPTCHA validation and there is no identified open-data mirror.

Setup and configuration

You can connect through the hosted MCP endpoint:

{
  "mcpServers": {
    "ucc-liens": {
      "url": "https://gateway.pipeworx.io/ucc-liens/mcp"
    }
  }
}

The hosted endpoint requires no account for the first calls according to the provided documentation and uses the same gateway as the broader Pipeworx service. Its tool list includes the pack tools plus shared gateway meta-tools, such as routing and discovery tools. Alternatively, the full gateway endpoint can be configured when direct access to all catalog packs is preferred.

For a local process, run the package through npx:

{
  "mcpServers": {
    "ucc-liens": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-ucc-liens"]
    }
  }
}

The standalone process communicates over standard input and output and exposes only this pack’s tools. No environment variables or API keys are documented as required.

The tools can also be called over HTTP through the gateway, including POST /v1/tools/ucc_search.

Tools and capabilities

ucc_search accepts a debtor name, a state code for Colorado, Connecticut, or Oregon, and an optional result limit. ucc_new_filings accepts a state, a starting date, an optional secured-party substring, and an optional limit. Both tools return state-specific filing data when available.

The Colorado implementation deliberately does not query the separate collateral dataset in its current version, so collateral descriptions are not included there. Connecticut’s published dataset also has no collateral-description field.

Limitations and notes

Oregon coverage is limited to its replaceable monthly dataset rather than a complete historical index. Vermont requests always fail descriptively instead of returning an empty result. The integration is unofficial and is not affiliated with, endorsed by, or published by the upstream state providers. The package is licensed under MIT.