Klarefi
REMOTE · WWW.KLAREFI.COM · 2 COMPONENTS
Complete regulated intake work and retrieve cited case files without deciding the case.
Available components
Last scanned (21 hours ago)
Scores higher than 77% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (create_connector_from_openapi). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- 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 1982 tokens (~90/item across 22 items; 21 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 Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 43% 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 22 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
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 8 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Oct 26 0
- Tool “answer_question” rewrote its description, which is the text the model reads security
- Tool “submit_case_review” rewrote its description, which is the text the model reads security
- Tool “save_workflow_draft” rewrote its description, which is the text the model reads security
- Tool “create_connector_from_openapi” rewrote its description, which is the text the model reads security
- Tool “create_connector” rewrote its description, which is the text the model reads security
- “create_connector_from_openapi” added an optional parameter “connection_status” cosmetic
- 30 Oct 26 0
- Tool “submit_case_review” rewrote its description, which is the text the model reads security
- 12 Oct 26 0
- Tool “get_case_package” rewrote its description, which is the text the model reads security
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 · Probed https://www.klarefi.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=klarefi.com | CN=WE1,O=Google Trust Services,C=US | 30 Sept 2026 | 29 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d5a87dcef4ca063b13c9d996f198ecb5 |
| SANs: klarefi.com, *.klarefi.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.klarefi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| klarefi.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; img-src 'self' data: blob: https:; font-src 'self' data:; script-src 'self' 'nonce-25gOSaMVVqoP2UC/honCkw==' 'strict-dynamic' https://datafa.st; style-src-elem 'self' 'unsafe-inline'; style-src-attr 'unsafe-inline'; style-src 'self' 'unsafe-inline'; connect-src 'self' https: wss:; worker-src 'self' blob:; media-src 'self' blob:; frame-src 'self' https://*.workos.com https://*.workos.dev https://cal.com https://app.cal.com; form-action 'self'; upgrade-insecure-requests; report-uri /api/csp-report; report-to csp-endpoint |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.klarefi.com/mcp | Verified | 200 | |
| http (plaintext) | http://www.klarefi.com/mcp | HTTPS enforced | 301 | https://www.klarefi.com/mcp |
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 →
answer_fields Answer intake 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.
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | – | Applicant access token. Use it with session_id instead of url. |
| api_base_url | string | – | Optional Klarefi deployment URL for local stdio use. The hosted MCP endpoint does not accept this override. |
| fields | object | yes | String values keyed by fact_id. |
| session_id | string | – | – |
| task_id | string | – | – |
| url | string | – | Signed hosted intake URL. Include it in every call to the hosted MCP endpoint. |
No output schema declared.
No examples provided.
answer_question Answer intake question ~149
Answer the active applicant question with free text, optionally targeting a task_id. When the applicant cannot supply what it asks for now, say so and why; the question is then closed and not asked again unless something new is sent.
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | – | Applicant access token. Use it with session_id instead of url. |
| api_base_url | string | – | Optional Klarefi deployment URL for local stdio use. The hosted MCP endpoint does not accept this override. |
| session_id | string | – | – |
| task_id | string | – | – |
| text | string | yes | – |
| url | string | – | Signed hosted intake URL. Include it in every call to the hosted MCP endpoint. |
No output schema declared.
No examples provided.
create_connector Create or update connector ~60
Create or update a Klarefi verification connector manifest. The result reports whether the configuration is active or staged for operator approval. Set connection_status to not_connected and omit credentials to add now; upsert with connected and credentials later. Checks remain open until connected.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create_connector_from_openapi Import connector from OpenAPI ~100
Import a public OpenAPI JSON URL as a Klarefi verification connector. JSON specs only (convert YAML first). The result reports whether the configuration is active or staged for operator approval. Set connection_status to not_connected to import before credentials exist.
| Name | Type | Req | Description |
|---|---|---|---|
| base_url | string | – | – |
| connection_status | string | – | – |
| connector_key | string | yes | – |
| label | string | – | – |
| openapi_url | string | yes | – |
No output schema declared.
No examples provided.
create_intake_session Create intake session ~103
Create a hosted Klarefi intake session.
| Name | Type | Req | Description |
|---|---|---|---|
| case_type_id | string | yes | – |
| external_applicant_id | string | – | – |
| external_case_id | string | – | – |
| external_customer_id | string | – | – |
| locale | string | – | – |
| prefill | object | – | Prefill payload passed through to the session; schema owned by the prefill feature |
| return_url | string | – | – |
| ttl_hours | number | – | – |
No output schema declared.
No examples provided.
delete_connector Delete connector ~33
Delete a configured Klarefi connector by key or stage its deletion for operator approval.
| Name | Type | Req | Description |
|---|---|---|---|
| connector_key | string | yes | – |
No output schema declared.
No examples provided.
get_case Get case ~26
Retrieve a Klarefi case and resolved facts.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | string | yes | – |
No output schema declared.
No examples provided.
get_case_package Get case package ~56
Get the cited case_package.v1 artifact and a signed read-only case-file URL. The package carries the facts, the calculated facts, and the offer or decline on the case with its files.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | string | yes | – |
No output schema declared.
No examples provided.
get_case_workspace Get case workspace ~41
Inspect a case workspace with facts, cited evidence, blockers, ownership, and timeline. This does not mutate the case.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | string | yes | – |
No output schema declared.
No examples provided.
get_intake_state Get intake state ~113
Get the current applicant intake state. Pass url, or session_id with access_token, on the hosted MCP endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | – | Applicant access token. Use it with session_id instead of url. |
| api_base_url | string | – | Optional Klarefi deployment URL for local stdio use. The hosted MCP endpoint does not accept this override. |
| session_id | string | – | – |
| url | string | – | Signed hosted intake URL. Include it in every call to the hosted MCP endpoint. |
No output schema declared.
No examples provided.
get_review_command Get review command ~36
Poll the status and result of an intake-review command.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | string | yes | – |
| command_id | string | yes | – |
No output schema declared.
No examples provided.
give_intake_consent Give intake consent ~131
Record the applicant's consent to processing. Call it when the intake state's next_action is consent, and only after the applicant has agreed to the notice in next_action.notice. Returns the fresh intake state.
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | – | Applicant access token. Use it with session_id instead of url. |
| api_base_url | string | – | Optional Klarefi deployment URL for local stdio use. The hosted MCP endpoint does not accept this override. |
| session_id | string | – | – |
| url | string | – | Signed hosted intake URL. Include it in every call to the hosted MCP endpoint. |
No output schema declared.
No examples provided.
list_operator_queue List operator queue ~36
List the bounded Klarefi operator queue for this API key's environment. Requires cases:review.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
No output schema declared.
No examples provided.
list_workflows 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 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.
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | – | Applicant access token. Use it with session_id instead of url. |
| api_base_url | string | – | Optional Klarefi deployment URL for local stdio use. The hosted MCP endpoint does not accept this override. |
| session_id | string | – | – |
| url | string | – | Signed hosted intake URL. Include it in every call to the hosted MCP endpoint. |
No output schema declared.
No examples provided.
save_intake_draft Save intake draft ~121
Save applicant form draft fields without submitting. Field values must be strings or null.
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | – | Applicant access token. Use it with session_id instead of url. |
| api_base_url | string | – | Optional Klarefi deployment URL for local stdio use. The hosted MCP endpoint does not accept this override. |
| fields | object | yes | Draft field values keyed by field_id. |
| session_id | string | – | – |
| url | string | – | Signed hosted intake URL. Include it in every call to the hosted MCP endpoint. |
No output schema declared.
No examples provided.
save_workflow_draft Save workflow draft ~98
Validate and save a workflow declaration as a draft. This tool cannot publish or activate the workflow. Each input_bindings entry on a check is a fact ID, { "literal": value } for a fixed plain-text value (never a secret), or { "case": "case_id" | "case_reference" | "external_case_id" }. A parameter left out uses the connector's default.
| Name | Type | Req | Description |
|---|---|---|---|
| workflow | object | yes | – |
No output schema declared.
No examples provided.
submit_case_review Submit case review command ~134
Submit an auditable intake-review command. Allowed commands review or correct facts, update evidence, escalate, or record a case-wide checks go. For checks_go supply payload.decision as go, not_now, or withdraw and an optional rationale; poll get_review_command, because a decision sent before the case has started stays accepted until it applies. This tool cannot complete or reopen a case.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | string | yes | – |
| command_type | string | yes | – |
| idempotency_key | string | – | – |
| payload | object | yes | – |
| rationale | string | – | – |
| trace_id | string | – | – |
No output schema declared.
No examples provided.
submit_intake Submit intake ~125
Submit the applicant intake. Returns submitted, blockers, and the fresh intake state.
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | – | Applicant access token. Use it with session_id instead of url. |
| api_base_url | string | – | Optional Klarefi deployment URL for local stdio use. The hosted MCP endpoint does not accept this override. |
| field_values | object | – | Optional final field values; each value must be string or null. |
| session_id | string | – | – |
| url | string | – | Signed hosted intake URL. Include it in every call to the hosted MCP endpoint. |
No output schema declared.
No examples provided.
upload_document Upload intake 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.
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | – | Applicant access token. Use it with session_id instead of url. |
| api_base_url | string | – | Optional Klarefi deployment URL for local stdio use. The hosted MCP endpoint does not accept this override. |
| content_base64 | string | – | – |
| file_path | string | – | – |
| filename | string | – | Required with content_base64. Defaults to the basename of file_path. |
| mime_type | string | – | – |
| session_id | string | – | – |
| task_id | string | – | – |
| url | string | – | 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 Wait for next intake action ~122
Poll until the intake leaves processing or the timeout expires. If timed_out is true, call wait_for_next_action again.
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | – | Applicant access token. Use it with session_id instead of url. |
| api_base_url | string | – | Optional Klarefi deployment URL for local stdio use. The hosted MCP endpoint does not accept this override. |
| session_id | string | – | – |
| timeout_seconds | number | – | – |
| url | string | – | Signed hosted intake URL. Include it in every call to the hosted MCP endpoint. |
No output schema declared.
No examples provided.
How do I install the Klarefi MCP server?
Klarefi is a hosted endpoint at https://www.klarefi.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.klarefi.com
claude mcp add --transport http com-klarefi-mcp 'https://www.klarefi.com/mcp'
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 hosted endpoint (https://www.klarefi.com/mcp).
Is the Klarefi MCP server safe to use?
Klarefi scores 80 out of 100 on VerifyMCP. 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 21 tools: create_connector_from_openapi, create_connector, delete_connector, create_intake_session, get_case, and 16 more. Their descriptions and schemas cost roughly 1,963 tokens of context every time the server is loaded.
Does the Klarefi MCP server require authentication?
No. We connected to Klarefi without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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 did VerifyMCP test on the Klarefi MCP server?
VerifyMCP ran 14 checks on Klarefi, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.