@tthorstenson/juris

Name: @tthorstenson/juris
Author: io.github.tthorstenson

MCPcommunity

v0.1.0io.github.tthorstensonUnknownUpdated 18d agonpm GitHub

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

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

175Downloads/wk

18d agoLast update

Needs 1 credential before it runs

JURIS_API_KEYAPI keyrequired
Juris API key (Bearer token). Required for search_ucc_liens.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package

Authorio.github.tthorstenson

LicenseUnknown

Version0.1.0

Sourcenpm+mcp-registry

npm@tthorstenson/juris

GitHubtthorstenson/juris

SBOMCycloneDX 1.6 ↓

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface2 tools · none privileged

Security scan✓ Cleanv0.1.0 · 16d agoHow well does this scan work?

EvalsNone

IndexedSep 7, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

2 tools · none privileged

Statically extracted from the published packagev0.1.0 · 16d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

search_ucc_liensSearch UCC Article 9 financing statements by debtor name. Returns filings plus honest provenance (source_url, as_of, method=fixture|live, confidence). Coverage holes are admitted; filings are never invented for NY/TX/CA or other holes.

Search UCC Article 9 financing statements by debtor name. Returns filings plus honest provenance (source_url, as_of, method=fixture|live, confidence). Coverage holes are admitted; filings are never invented for NY/TX/CA or other holes.

No input schema was published for this tool.

list_ucc_coverageList Juris UCC search coverage, including day-1 adapters (KY, RI, WI), next states (CO, MI), and HARD holes (NY, TX, CA). Every row includes provenance.

List Juris UCC search coverage, including day-1 adapters (KY, RI, WI), next states (CO, MI), and HARD holes (NY, TX, CA). Every row includes provenance.

No input schema was published for this tool.

2 of 2 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

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

Keywords

mcp

Alternatives

Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-07 — observed resolution, not a publisher declaration.

60 packages resolved · 7 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

zod3.25.76
dotenv16.6.1
stripe18.5.01 dependency
- qs6.16.0+2 not drawn
fastify5.12.315 dependencies
- pino10.3.1+10 not drawn1 dependency
  - process-warning5.1.0
- rfdc1.4.1
- avvio9.3.0+1 not drawn1 dependency
  - @fastify/error4.2.0
- semver7.8.5
- toad-cache3.7.4
- find-my-way9.9.0+3 not drawn
- @fastify/error4.2.0shown above
- process-warning5.1.0shown above
- abstract-logging2.0.1
- light-my-request6.6.0+3 not drawn
- secure-json-parse4.1.0
- @fastify/proxy-addr5.1.0+2 not drawn
- fast-json-stringify7.0.1incomplete+1 not drawn
- @fastify/ajv-compiler4.0.6incomplete
- @fastify/fast-json-stringify-compiler5.1.0incomplete
@fastify/cors10.1.0+1 not drawn1 dependency
- mnemonist0.40.0incomplete
@fastify/formbody8.0.2+2 not drawn
@modelcontextprotocol/sdk1.30.0+17 not drawn

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

69 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 69

set-cookie-parser ^2.6.0 — required by light-my-request@6.6.0package cap reached
ipaddr.js ^2.1.0 — required by @fastify/proxy-addr@5.1.0package cap reached
@fastify/forwarded ^3.0.0 — required by @fastify/proxy-addr@5.1.0package cap reached
rfdc ^1.2.0 — required by fast-json-stringify@7.0.1package cap reached
fast-uri ^4.0.0 — required by fast-json-stringify@7.0.1package cap reached
ajv-formats ^3.0.1 — required by fast-json-stringify@7.0.1package cap reached
json-schema-ref-resolver ^3.0.0 — required by fast-json-stringify@7.0.1package cap reached
@fastify/merge-json-schemas ^0.2.0 — required by fast-json-stringify@7.0.1package cap reached
ajv ^8.12.0 — required by @fastify/ajv-compiler@4.0.6package cap reached
fast-uri ^4.0.0 — required by @fastify/ajv-compiler@4.0.6package cap reached
ajv-formats ^3.0.1 — required by @fastify/ajv-compiler@4.0.6package cap reached
fast-json-stringify ^7.0.0 — required by @fastify/fast-json-stringify-compiler@5.1.0package cap reached

+57 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

@tthorstenson/juris

Tools

Tools exposed

Dependency tree

Declared but not resolved

Topics

Related in search & retrieval