Keep confidence tiers visible
Separate High- and Medium-confidence provider classifications instead of blending them into an unexplained lead count.
UCCContacts by YANETO · For MCA brokers and funders
Move from new filing activity to a focused research queue with secured-party filters, repeat-filing signals, available officer matches, and delivery by API, Google Sheets, or PostgreSQL.
Prefer to look first? Inspect the rotating public sample
Your sourcing stays private. Customer identities are never disclosed.
Clear commercial terms. Data lists are non-exclusive.
Source-aware delivery. Freshness depends on publication and ingestion.
Built for your workflow
Review provider associations, repeat-filing context, and available owner matches without rebuilding the same list every week. Use a shared Sheet or connect the feed to your own systems.
Separate High- and Medium-confidence provider classifications instead of blending them into an unexplained lead count.
Use normalized debtor and address signals to identify records that merit further research without calling them verified stacking or active obligations.
Filter and deliver structured filing data into an API workflow or the Google Sheet your team already reviews.
Find the right yes
Prioritize records using filing recency, provider associations, debtor state, repeat activity, and available officer details—then keep the supporting context attached as your team researches and reaches out.
See the data before you buy
Inspect a rotating slice of real UCC filing records before sharing your information. Then request a larger sample delivered to your business email.
Open the live public sampleTwenty-eight fields per record, available without signup through the public sample.
The public sample is a rotating slice, not a balanced state mix. Blank enrichment fields and coded values can appear.
The automated sample includes up to 25 recent records from each of 32 covered states plus Washington, DC. Tell us which states and providers matter in your request notes so we can understand your workflow.
One automated sample per verified business domain. Phone numbers and email addresses are excluded.
Request your sampleA practical alternative
| Current approach | Typical tradeoff | What UCCContacts changes |
|---|---|---|
| Buy a general lead list | Familiar and inexpensive, but not organized around a recent filing signal. | Structured filing data with filing dates, secured parties, and repeat-filing context. |
| Pull state portals by hand | Direct control, with repeated collection and spreadsheet preparation. | A recurring feed delivered to a Sheet or available through an API. |
| Build and maintain collection | Full control, plus ongoing maintenance when portals and formats change. | Multi-state collection and normalization without maintaining the source integrations yourself. |
What the data supports
Distinct filing numbers dated Sep. 1–Oct. 13, 2026.
Kept separate from the High-confidence population.
196 High and 330 Medium. Populated and format-screened, not verified.
Dataset scale only. This is not MCA volume.
Filing-date window: September 1–October 13, 2026, unless a card says September 2026. Measured October 14, 2026. Counts are distinct nonempty filing numbers after trimming and uppercasing, deduplicated across debtor rows. Filing numbers may not be unique across jurisdictions because the source has no filing-office jurisdiction field.
Filters and delivery
Build a research feed around filing date, debtor state, secured party, confidence tier, and repeat-filing signals. Debtor state describes the state recorded for the debtor; it does not establish the filing-office jurisdiction.
Pull available current or historical records with filters that fit your workflow.
Receive the current month’s backlog and new available records in a shared sheet, checked every 15 minutes.
Work with debtor, filing, secured-party, repeat-filing, and available enrichment fields in a consistent format.
Method and limits
Evaluate it with your team
Request the complimentary sample, review the fields and limitations, and decide whether the feed fits your workflow.