Juris UCC Article 9 lien search

io.github.tthorstensonPublished by GitHub account tthorstensonv0.1.0Updated Oct 24, 2026

UCC Article 9 debtor lien search + honest list_coverage; fixture-default; live HTML ToS-GRAY opt-in

VerifiedSTDIODesktop onlyFinanceBusiness & Commerce

Overview

AI-generated overview

Local MCP server that lets an assistant run UCC Article 9 debtor lien searches and check what coverage the data actually has.

What you can do
  • Run UCC Article 9 debtor lien searches against the Juris HTTP API.
  • List the coverage the service claims, described as honest about its limits.
  • Defaults to fixture data, with live HTML retrieval available only as an opt-in.
When to use it
Useful when an assistant needs to look up secured-lending liens filed against a debtor, or to check how far a lien dataset's coverage extends, in a workflow where fixture data is acceptable for testing.
Requirements
Runs as a local npm package over stdio on a desktop machine. Requires a Juris API key supplied in the JURIS_API_KEY environment variable, which is needed for the lien search tool. An optional JURIS_BASE_URL variable sets the API base URL. Network access is needed for live searches.
Before you install
The server needs an API key (JURIS_API_KEY) and sends search requests to a third-party Juris API. Live HTML retrieval is opt-in and the description flags its terms-of-service status as gray, so confirm you are permitted to use it. Results default to fixture data, so verify whether a given answer came from live or sample data before relying on it.

Installation

In SourceWeft

  1. Open Juris UCC Article 9 lien search in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.