Klarefi MCP server

• answer_fieldsFree

  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.

• answer_questionFree

  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.

• create_connectorwrite actionFree

  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.

• create_connector_from_openapiwrite actionFree

  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.

• create_intake_sessionwrite actionFree

  Create a hosted Klarefi intake session.

• delete_connectorwrite actionFree

  Delete a configured Klarefi connector by key or stage its deletion for operator approval.

• get_caseFree

  Retrieve a Klarefi case and resolved facts.

• get_case_packageFree

  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.

• get_case_workspaceFree

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

• get_intake_stateFree

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

• get_review_commandFree

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

• give_intake_consentFree

  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.

• list_operator_queueFree

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

• list_workflowsFree

  List versioned Form · Fact · Verify workflow declarations.

• open_intakeFree

  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.

• save_intake_draftFree

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

• save_workflow_draftFree

  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.

• submit_case_reviewwrite actionFree

  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.

• submit_intakewrite actionFree

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

• upload_documentwrite actionFree

  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.

• wait_for_next_actionFree

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

• Code scan9 source files scanned25/25
• Live reliabilityremote reachable in 1013ms20/20
• Tool poisoning21 tool descriptions checked15/15
• Auth qualityAPI key sent as a header8/15
• Maintenancelast push 6 days ago15/15
• Maintainer identityendpoint served from the registry-verified namespace domain8/10

Safety score

91/100

higher than 85% of 48,255 servers

Tools

21

the typical server has 7

Tools that change things

33%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote server answers 100%

Response time

88 ms

faster than 86% of 30,031 servers

Downloads a week

55

more than 46% of 12,191 servers with a package

Grade history

• 2026-11-04restoreB → Ascore 91

Klarefi: common questions

Is Klarefi MCP server safe?

Yes, by our scan: it is graded A (91/100). Read the Klarefi safety report

How do I install Klarefi?

It runs remotely at www.klarefi.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Klarefi need an API key?

Yes. The registry entry asks for KLAREFI_API_KEY, Authorization.

Is Klarefi maintained?

The last commit was 6 days ago (2026-10-29). The latest release is v0.3.0.

Is Klarefi up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

How does Klarefi compare with other MCP servers?

safety score 91/100 (higher than 85% of 48,255 servers); tools 21 (the typical server has 7); tools that change things 33% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.