Velrim MCP Server

by velrim Your server? Claim it

answering

Velrim is answering right now. Last checked 10 min ago. It exposes 2 tools.

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

Uptime history 52 days of history · worst day 93%

52 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

954 ms

Response time

average over 24h

open, no key

Access

streamable-http

Velrim missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add extract --transport http https://mcp.velrim.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://mcp.velrim.com/mcp

~/.codex/config.toml

[mcp_servers.extract]
url = "https://mcp.velrim.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "extract": {
      "url": "https://mcp.velrim.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "extract": {
      "type": "http",
      "url": "https://mcp.velrim.com/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

velrim

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.

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.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.velrim.com/mcp	streamable-http	answering	862 ms	10 min ago

Alternatives to Velrim

same job, measured the same way

Dokyumi Document Extraction

by dokyumi

Extract attached documents with saved schemas and review owned results, confidence and validation.

9 tools answering

Docpick

by arknill

Schema-driven document extraction with local OCR + LLM. Document in, Structured JSON out.

99 installs/wk local only

SchemaSure — structured extraction

by noamjose

Extract schema-valid JSON from text/HTML or document images. Pay with x402 on Base or MPP on Tempo.

78 installs/wk local only

Brainiall Documents

by brainiall

High-fidelity PDF to structured Markdown conversion and document field extraction.

3 tools answering

ParseRelay

by parserelay

Parse a document into structured, confidence-scored fields. Bring your own model, pay per scan.

43 installs/wk local only

Handinloop MCP Server

by lesofi

Human-in-the-loop document extraction: submit a doc, get validated fields and an audit trail.

481 installs/wk local only

Handinloop MCP Server

by handinloop

Human-in-the-loop document extraction: submit a doc, get validated fields and an audit trail.

answering

Parserail MCP

by thecompound

Documents to schema-valid JSON plus 38 more finished-job AI tools, on one credit wallet.

61 installs/wk local only

Velrim — questions

Answers built from our own checks of this server.

What can Velrim do?

It exposes 2 tools, read directly from the server on our last check. Among them: velrim_extract, velrim_job_status. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Velrim working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 954 ms. The bar chart above shows every period we have measured.

How do I connect Velrim?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Velrim need an API key?

No. Velrim completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Velrim?

It answers our handshake in 954 ms on average, which is faster than 7% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.