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.

Klarefi

NPM · @KLAREFI/MCP · 2 COMPONENTS

Complete regulated intake work and retrieve cited case files without deciding the case.

+1 this week 78 Trust /100

Last scanned (22 hours ago)

Scores higher than 59% of npm servers

Category CRM and Sales

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 Security83
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @modelcontextprotocol/server 2.0.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 0 of 4 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability78
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1652 tokens (~78/item across 21 items; 20 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage80
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 41% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (17)

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

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.

  • 16 Nov 26 0
    • Stability: 0.97 → pass security
  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 8 Nov 26 0
    • Stability: 0.97 → pass security
  • 7 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Nov 26 −1
    • Stability: pass → 0.87 functional
  • 29 Oct 26 0
    • Stability: 0.97 → pass security
  • 28 Oct 26 0
    • GHSA-f897-62hf-6gxq affects this package: high ▼ security
    • Stability: pass → 0.97 functional
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/@klarefi/mcp@0.3.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 4 findings
ID CVE Severity Vector Fix available
GHSA-46jr-4wx8-v453 CVE-2026-111768 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-f897-62hf-6gxq high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-jm63-cq47-j5jp CVE-2026-111770 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:H yes
GHSA-rvq5-wwqv-78pq CVE-2026-111771 medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 4 packages
Packages resolved 4
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 20 exposed · ~1,633 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
answer_fields ~141

Answer structured requested facts by fact_id. Values must be strings; yes_no fields take "yes" or "no", and date fields use YYYY-MM-DD.

NameTypeReqDescription
access_tokenstring–Applicant access token. Use it with session_id instead of url.
api_base_urlstring–Optional Klarefi deployment URL for local stdio use. The hosted MCP endpoint does not accept this override.
fieldsobjectyesString values keyed by fact_id.
session_idstring––
task_idstring––
urlstring–Signed hosted intake URL. Include it in every call to the hosted MCP endpoint.

No output schema declared.

No examples provided.

answer_question ~118

Answer the active applicant question with free text, optionally targeting a task_id.

NameTypeReqDescription
access_tokenstring–Applicant access token. Use it with session_id instead of url.
api_base_urlstring–Optional Klarefi deployment URL for local stdio use. The hosted MCP endpoint does not accept this override.
session_idstring––
task_idstring––
textstringyes–
urlstring–Signed hosted intake URL. Include it in every call to the hosted MCP endpoint.

No output schema declared.

No examples provided.

create_connector ~46

Create or update a Klarefi verification connector manifest. The connector is active as soon as this returns — there is no draft/review step, so review its functions before routing live traffic.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

create_connector_from_openapi ~80

Import a public OpenAPI JSON URL as a Klarefi verification connector. JSON specs only (convert YAML first). The connector goes live immediately — review its functions before routing live traffic.

NameTypeReqDescription
base_urlstring––
connector_keystringyes–
labelstring––
openapi_urlstringyes–

No output schema declared.

No examples provided.

create_intake_session ~103

Create a hosted Klarefi intake session.

NameTypeReqDescription
case_type_idstringyes–
external_applicant_idstring––
external_case_idstring––
external_customer_idstring––
localestring––
prefillobject–Prefill payload passed through to the session; schema owned by the prefill feature
return_urlstring––
ttl_hoursnumber––

No output schema declared.

No examples provided.

delete_connector ~26

Delete a configured Klarefi connector by key.

NameTypeReqDescription
connector_keystringyes–

No output schema declared.

No examples provided.

get_case ~26

Retrieve a Klarefi case and resolved facts.

NameTypeReqDescription
case_idstringyes–

No output schema declared.

No examples provided.

get_case_package ~34

Get the cited case_package.v1 artifact and a signed read-only case-file URL.

NameTypeReqDescription
case_idstringyes–

No output schema declared.

No examples provided.

get_case_workspace ~41

Inspect a case workspace with facts, cited evidence, blockers, ownership, and timeline. This does not mutate the case.

NameTypeReqDescription
case_idstringyes–

No output schema declared.

No examples provided.

get_intake_state ~113

Get the current applicant intake state. Pass url, or session_id with access_token, on the hosted MCP endpoint.

NameTypeReqDescription
access_tokenstring–Applicant access token. Use it with session_id instead of url.
api_base_urlstring–Optional Klarefi deployment URL for local stdio use. The hosted MCP endpoint does not accept this override.
session_idstring––
urlstring–Signed hosted intake URL. Include it in every call to the hosted MCP endpoint.

No output schema declared.

No examples provided.

get_review_command ~36

Poll the status and result of an intake-review command.

NameTypeReqDescription
case_idstringyes–
command_idstringyes–

No output schema declared.

No examples provided.

list_operator_queue ~36

List the bounded Klarefi operator queue for this API key's environment. Requires cases:review.

NameTypeReqDescription
limitnumber––

No output schema declared.

No examples provided.

list_workflows ~20

List versioned Form · Fact · Verify workflow declarations.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

open_intake ~132

Read an applicant intake from a signed URL or from session_id plus access_token. No Klarefi API key is required. On the hosted MCP endpoint, include the same intake credential in each later intake tool call.

NameTypeReqDescription
access_tokenstring–Applicant access token. Use it with session_id instead of url.
api_base_urlstring–Optional Klarefi deployment URL for local stdio use. The hosted MCP endpoint does not accept this override.
session_idstring––
urlstring–Signed hosted intake URL. Include it in every call to the hosted MCP endpoint.

No output schema declared.

No examples provided.

save_intake_draft ~121

Save applicant form draft fields without submitting. Field values must be strings or null.

NameTypeReqDescription
access_tokenstring–Applicant access token. Use it with session_id instead of url.
api_base_urlstring–Optional Klarefi deployment URL for local stdio use. The hosted MCP endpoint does not accept this override.
fieldsobjectyesDraft field values keyed by field_id.
session_idstring––
urlstring–Signed hosted intake URL. Include it in every call to the hosted MCP endpoint.

No output schema declared.

No examples provided.

save_workflow_draft ~37

Validate and save a workflow declaration as a draft. This tool cannot publish or activate the workflow.

NameTypeReqDescription
workflowobjectyes–

No output schema declared.

No examples provided.

submit_case_review ~90

Submit an auditable intake-review command. Allowed commands review or correct facts, request clarification, update evidence, or escalate. This tool cannot complete or reopen a case.

NameTypeReqDescription
case_idstringyes–
command_typestringyes–
idempotency_keystring––
payloadobjectyes–
rationalestring––
trace_idstring––

No output schema declared.

No examples provided.

submit_intake ~125

Submit the applicant intake. Returns submitted, blockers, and the fresh intake state.

NameTypeReqDescription
access_tokenstring–Applicant access token. Use it with session_id instead of url.
api_base_urlstring–Optional Klarefi deployment URL for local stdio use. The hosted MCP endpoint does not accept this override.
field_valuesobject–Optional final field values; each value must be string or null.
session_idstring––
urlstring–Signed hosted intake URL. Include it in every call to the hosted MCP endpoint.

No output schema declared.

No examples provided.

upload_document ~186

Upload a requested applicant document. Use content_base64 on the hosted MCP endpoint. Local stdio clients can use file_path. Inline content is limited to 5MB decoded; local files can be up to 25MB.

NameTypeReqDescription
access_tokenstring–Applicant access token. Use it with session_id instead of url.
api_base_urlstring–Optional Klarefi deployment URL for local stdio use. The hosted MCP endpoint does not accept this override.
content_base64string––
file_pathstring––
filenamestring–Required with content_base64. Defaults to the basename of file_path.
mime_typestring––
session_idstring––
task_idstring––
urlstring–Signed hosted intake URL. Include it in every call to the hosted MCP endpoint.

No output schema declared.

No examples provided.

wait_for_next_action ~122

Poll until the intake leaves processing or the timeout expires. If timed_out is true, call wait_for_next_action again.

NameTypeReqDescription
access_tokenstring–Applicant access token. Use it with session_id instead of url.
api_base_urlstring–Optional Klarefi deployment URL for local stdio use. The hosted MCP endpoint does not accept this override.
session_idstring––
timeout_secondsnumber––
urlstring–Signed hosted intake URL. Include it in every call to the hosted MCP endpoint.

No output schema declared.

No examples provided.

Install

How do I install the Klarefi MCP server?

Klarefi runs locally as an npm package, launched with npx -y @klarefi/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 · @klarefi/mcp

# add to Claude Code
claude mcp add com-klarefi-mcp -- npx -y @klarefi/mcp
Common questions

What is the Klarefi MCP server?

Klarefi is an MCP server listed in the public MCP registry as com.klarefi/mcp. Complete regulated intake work and retrieve cited case files without deciding the case. This page covers its npm package (@klarefi/mcp).

Is the Klarefi MCP server safe to use?

Klarefi scores 78 out of 100 on VerifyMCP. We recorded 4 known advisories 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 Klarefi MCP server expose?

Klarefi exposes 20 tools: create_connector_from_openapi, create_connector, delete_connector, create_intake_session, get_case, and 15 more. Their descriptions and schemas cost roughly 1,633 tokens of context every time the server is loaded.

Is the Klarefi MCP server still maintained?

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

Klarefi declares the ISC 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 Klarefi MCP server?

VerifyMCP ran 17 checks on Klarefi, covering Malware scan, Known CVEs, Install scripts, Dependency health and 13 more. 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.