Velrim

com.velrimPublished by velrim.comOfficial publisherv0.1.0Updated Oct 24, 2026

Document extraction against a JSON Schema with a calibrated confidence per field; async job status.

VerifiedStreamable HTTPWeb executableFiles & StorageData & Analytics

Overview

AI-generated overview

Velrim is a remote MCP server that lets an assistant extract structured, schema-typed data from PDFs and images, with per-field confidence and source anchors.

What you can do
Extract structured data from a PDF or image against a JSON Schema you supply, returning a typed object with a state, calibrated confidence score and source anchor for every field. Poll an asynchronous extraction job by job_id and retrieve the same typed result once it completes.
When to use it
Use it when you need reliable field-level extraction from documents or scanned images into a fixed schema, and want confidence scores and source anchors to check results rather than free-text output.
Requirements
A remote endpoint at mcp.velrim.com over streamable HTTP. A Velrim API key is required, sent as a bearer token in the Authorization header; keys are created in the Velrim dashboard. Documents are passed as base64 or as the upload_key of a staged upload.
Before you install
The Authorization header carries a secret API key; keep it private. Documents you submit are sent to Velrim's servers, so avoid confidential material unless that is acceptable. Extraction results include confidence scores and anchors, so low-confidence fields should be verified.

Installation

In SourceWeft

  1. Open Velrim in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.velrim%2Fextract/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "velrim": {
      "type": "http",
      "url": "https://mcp.velrim.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

2

velrim_extract

Extract structured data from a document (PDF or image, passed as document_base64 or as the upload_key of a staged upload) against a JSON Schema you supply. Returns a typed object and, for every field, a state (present, null, or missing), a calibrated confidence score, and an anchor (the source page and bounding box). The confidence is calibrated against published reliability curves (https://velrim.com/reliability), so a 0.9 means the field is right about 90% of the time on that document class — branch on it directly: act on a field at or above your accept threshold, escalate the fields below it and any that are missing. Use each field's anchor to check it against the source page.

Parametershintsschemarequireddoc_classupload_keydocument_base64

velrim_job_status

Poll an asynchronous extraction job by its job_id (from POST /v1/jobs on the Velrim API; velrim_extract itself is synchronous and never creates jobs). Returns the job status and, once complete, the same typed result as velrim_extract: per field a state (present, null, or missing), a calibrated confidence score, and an anchor (source page and bounding box). Confidence is calibrated against published reliability curves (https://velrim.com/reliability) — branch the same way: act on a field at or above your accept threshold, escalate the rest, and use each anchor to check a field against its source page.

Parametersjob_idrequired

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.