Klarefi MCP server

• Registry namecom.klarefi/mcpverified in the MCP registry

The registry name sits under klarefi.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-24
• Tools21
• Server calls itselfklarefi-mcp
• Server version0.3.0
• Protocol version2025-11-25

On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 189 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 3 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
• Use18 npm downloads a week
• Answeredmeasuring3 of the 7 daily checks it takes to print a share
• Median first answer257 ms
• Space in an agent's context≈ 2,638 tokensthe definitions of all its tools (21), which an agent carries on every turn
• Tool definitionsB · 85 of 100
• Typed results0 of 21 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 19 of 21

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• 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.