velrim

endpoint

https://mcp.velrim.com/mcp

protocol

http-sse ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is velrim live?

Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.

Is velrim free to use?

Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.

What tools does velrim have?

2 tools: velrim_extract, velrim_job_status.

Is velrim safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• velrim_job_status reads auth-required 7h ago

  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.

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "job_id"
    ],
    "properties": {
      "job_id": {
        "type": "string",
        "minLength": 1,
        "description": "The job_id returned by an asynchronous Velrim extraction job (created via the Velrim API or an SDK)."
      }
    }
  }

  arguments 14 lines copy
• velrim_extract reads unknown never probed

  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.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435363738

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "schema"
    ],
    "properties": {
      "hints": {
        "type": "object",
        "description": "Discriminator hints for union schemas.",
        "propertyNames": {
          "type": "string"
        },
        "additionalProperties": {}
      },
      "schema": {
        "type": "object",
        "description": "The JSON Schema (draft 2020-12) the extracted object must conform to (required).",
        "propertyNames": {
          "type": "string"
        },
        "additionalProperties": {}
      },
      "doc_class": {
        "type": "string",
        "maxLength": 128,
        "description": "Opaque tag (<=128 chars) echoed back in meta.doc_class."
      },
      "upload_key": {
        "type": "string",
        "description": "The upload_key of a staged Velrim upload. Mutually exclusive with document_base64."
      },
      "document_base64": {
        "type": "string",
        "description": "The document bytes, base64-encoded. Provide exactly one of document_base64 or upload_key."
      }
    }
  }

  arguments 38 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.