Velrim
REMOTE · MCP.VELRIM.COM · SCANNED SEP 25
Document extraction against a JSON Schema with a calibrated confidence per field; async job status.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 441 tokens (~220/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Velrim MCP server?
Velrim is a hosted endpoint at https://mcp.velrim.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.velrim.com
claude mcp add --transport http com-velrim-extract 'https://mcp.velrim.com/mcp'
{
"mcpServers": {
"com-velrim-extract": {
"url": "https://mcp.velrim.com/mcp"
}
}
} {
"servers": {
"com-velrim-extract": {
"type": "http",
"url": "https://mcp.velrim.com/mcp"
}
}
} [mcp_servers.com-velrim-extract] url = "https://mcp.velrim.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-velrim-extract": {
"type": "remote",
"url": "https://mcp.velrim.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-velrim-extract --url 'https://mcp.velrim.com/mcp' --transport streamable-http
mcp_servers:
com-velrim-extract:
url: "https://mcp.velrim.com/mcp" {
"McpServers": {
"com-velrim-extract": {
"Transport": "http",
"Url": "https://mcp.velrim.com/mcp"
}
}
} assistant mcp add com-velrim-extract -t streamable-http -u 'https://mcp.velrim.com/mcp'
{
"mcpServers": {
"com-velrim-extract": {
"type": "http",
"url": "https://mcp.velrim.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 13 Sept 26 +41
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- First check of Tool coverage: 100 functional
- 11 Sept 26 33
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://mcp.velrim.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=velrim.com | CN=WE1,O=Google Trust Services,C=US | 8 Sept 2026 | 7 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 367123cccbb138e91370224b31d4777b |
| SANs: velrim.com, mcp.velrim.com, *.mcp.velrim.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.velrim.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| velrim.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.velrim.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.velrim.com/mcp | HTTPS enforced | 301 | https://mcp.velrim.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
velrim_extract ~273
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.
| Name | Type | Req | Description |
|---|---|---|---|
| doc_class | string | – | Opaque tag (<=128 chars) echoed back in meta.doc_class. |
| document_base64 | string | – | The document bytes, base64-encoded. Provide exactly one of document_base64 or upload_key. |
| hints | object | – | Discriminator hints for union schemas. |
| schema | object | yes | The JSON Schema (draft 2020-12) the extracted object must conform to (required). |
| upload_key | string | – | The upload_key of a staged Velrim upload. Mutually exclusive with document_base64. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | object | – | – |
| fields | object | – | – |
| meta | object | – | – |
No examples provided.
velrim_job_status ~168
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.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The job_id returned by an asynchronous Velrim extraction job (created via the Velrim API or an SDK). |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | – |
| job_id | string | – | – |
| result | object | – | – |
| status | string | – | "running" | "succeeded" | "failed" (additive-tolerant). |
No examples provided.
What is the Velrim MCP server?
Velrim is an MCP server listed in the public MCP registry as com.velrim/extract. Document extraction against a JSON Schema with a calibrated confidence per field; async job status. This page covers its hosted endpoint (https://mcp.velrim.com/mcp).
Is the Velrim MCP server safe to use?
Velrim scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Velrim MCP server expose?
Velrim exposes 2 tools: velrim_extract, velrim_job_status. Their descriptions and schemas cost roughly 441 tokens of context every time the server is loaded.
Does the Velrim MCP server require authentication?
Yes. Velrim asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Velrim MCP server still maintained?
Velrim is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.