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.

Clerkfield

NPM · CLERKFIELD-MCP · 2 COMPONENTS

Verify U.S. businesses against state registries and search UCC liens by business or lender.

0 this week 64 Trust /100

Last scanned (14 hours ago)

Scores higher than 37% 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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 423 tokens (~141/item across 3 items; 3 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (15)

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

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

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.

  • 11 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 10 Nov 26 49

    First indexed and scored.

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/clerkfield-mcp@1.0.0

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 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~350 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
get_coverage ~44

Which U.S. states each check covers (business check, lien search, search by lender).

NameTypeReqDescription
statestring–Two-letter state code; omit for every state

No output schema declared.

No examples provided.

search_liens ~147

List UCC financing statements filed against a business (debtor) or filed by a lender (secured party), newest first, with a summary of active, lapsed and terminated filings and the lenders on active filings. Each filing has its file number, dates, status, parties, collateral and later amendments. Covered states: see get_coverage; search by lender in see get_coverage.

NameTypeReqDescription
active_onlyboolean–Only active filings (default false)
debtorstring–Business name to search (give debtor or secured_party)
secured_partystring–Lender name to search
statestringyesTwo-letter state code, e.g. FL

No output schema declared.

No examples provided.

verify_business ~159

Check a U.S. business against the official registry of the state it was formed in. Returns a verdict (pass, review or fail) with flags explaining why (name match, active status, months in business, whether the owner is listed), plus the state's record: legal name, entity id, status, formation date, addresses, registered agent and officers. Covered states: see get_coverage.

NameTypeReqDescription
min_monthsinteger–Minimum months in business (default 6)
namestringyesBusiness name, as the applicant gave it
ownerstring–Applicant's name, checked against the officers the state lists
statestringyesTwo-letter state code where the business was formed, e.g. NY

No output schema declared.

No examples provided.

Install

How do I install the Clerkfield MCP server?

Clerkfield runs locally as an npm package, launched with npx -y clerkfield-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 · clerkfield-mcp

# add to Claude Code
claude mcp add com-clerkfield-mcp -- npx -y clerkfield-mcp
Common questions

What is the Clerkfield MCP server?

Clerkfield is an MCP server listed in the public MCP registry as com.clerkfield/mcp. Verify U.S. businesses against state registries and search UCC liens by business or lender. This page covers its npm package (clerkfield-mcp).

Is the Clerkfield MCP server safe to use?

Clerkfield scores 64 out of 100 on VerifyMCP. We recorded 1 known advisory 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 Clerkfield MCP server expose?

Clerkfield exposes 3 tools: verify_business, search_liens, get_coverage. Their descriptions and schemas cost roughly 350 tokens of context every time the server is loaded.

Is the Clerkfield MCP server still maintained?

Clerkfield 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 Clerkfield MCP server under?

Clerkfield 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 Clerkfield MCP server?

VerifyMCP ran 15 checks on Clerkfield, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Clerkfield: Stability. One category scores 0 for that reason, because we only credit what we can confirm. 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.