Klarefi

Last 30 days

Uptime

100%

Response time

239 ms typical, 239 ms slowest 5%

Last check

1 h ago

Next check

in 5 h

How to call it

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "klarefi": {
      "type": "http",
      "url": "https://www.klarefi.com/mcp"
    }
  }
}

21 tools

• create_connector_from_openapi

  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.

• create_connector

  Create or update a Klarefi verification connector manifest. The result reports whether the configuration is active or staged for operator approval.

• delete_connector

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

• create_intake_session

  Create a hosted Klarefi intake session.

• get_case

  Retrieve a Klarefi case and resolved facts.

• list_operator_queue

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

• get_case_workspace

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

• get_case_package

  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.

• submit_case_review

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

• get_review_command

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

• list_workflows

  List versioned Form · Fact · Verify workflow declarations.

• save_workflow_draft

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

• open_intake

  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.

• get_intake_state

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

• answer_question

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

• answer_fields

  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.

• upload_document

  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.

• give_intake_consent

  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.

• submit_intake

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

• save_intake_draft

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

• wait_for_next_action

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

Security scan

• No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks