# Olaverse Lab (pypi · olaverse-mcp)

Document extraction, decisions, language ID (608), diacritics, questions in 324 languages.

- Trust score: 67/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.olaverselab.com`: 66/100, [markdown](https://verifymcp.io/servers/olaverse-labs-olaverse-mcp/mcp.md), [page](https://verifymcp.io/servers/olaverse-labs-olaverse-mcp/mcp)
- pypi · `olaverse-mcp`: 67/100 (this document), [markdown](https://verifymcp.io/servers/olaverse-labs-olaverse-mcp/olaverse-mcp.md), [page](https://verifymcp.io/servers/olaverse-labs-olaverse-mcp/olaverse-mcp)

## Channel facts

- Registry: `pypi`
- Package: `olaverse-mcp`
- Version: `0.3.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 32 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to Olaverse-Labs/olaverse-mcp).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1126 tokens (~187/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Olaverse Lab MCP server?

Olaverse Lab runs locally as a PyPI package, launched with uvx olaverse-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add olaverse-labs-olaverse-mcp -- uvx olaverse-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "olaverse-labs-olaverse-mcp": {
      "command": "uvx",
      "args": [
        "olaverse-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "olaverse-labs-olaverse-mcp": {
      "command": "uvx",
      "args": [
        "olaverse-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add olaverse-labs-olaverse-mcp -- uvx olaverse-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "olaverse-labs-olaverse-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "olaverse-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add olaverse-labs-olaverse-mcp --command uvx --arg olaverse-mcp
```

### Hermes

```yaml
mcp_servers:
  olaverse-labs-olaverse-mcp:
    command: "uvx"
    args: ["olaverse-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "olaverse-labs-olaverse-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "olaverse-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add olaverse-labs-olaverse-mcp -t stdio -c uvx -a olaverse-mcp
```

### Other

```json
{
  "mcpServers": {
    "olaverse-labs-olaverse-mcp": {
      "command": "uvx",
      "args": [
        "olaverse-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 67, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-20 (score 82, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-19 (score 66, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-18 (score 81, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-16 (score 65, +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.

### 2026-11-15 (score 64, 0)

- [functional] Package version: 0.3.0 → 0.3.1

### 2026-11-14 (score 64, −11)

- [security regression] Malware scan: pass → unverified
- [functional regression] Schema quality: 165 → 183
- [functional improvement] Stability: unverified → 0.27
- [functional] Package version: 0.2.1 → 0.3.0

### 2026-11-12 (score 75, +15)

- [security improvement] Malware scan: unverified → pass

## MCP tools (6)

### `extract_document` (~347 tokens)

Turn a document into JSON shaped like `template`, with a calibrated confidence (0-1) for every field.

template: the shape of the answer; each leaf names a type: "verbatim-string" (copied exactly), "string",
  "number", "integer", "date" (YYYY-MM-DD), "date-time", "boolean", ["a", "b"] (pick one), [["a", "b"]] (pick
  any), ["string"] (a list), or [{...}] (a list of objects, e.g. line items).
  Example: {"merchant": "verbatim-string", "total": "number", "date": "date",
            "items": [{"name": "verbatim-string", "price": "number"}]}
Give the document as exactly one of:
  text: the document as text.
  image: a JPEG or PNG, base64 or a data URL (a photo, scan or screenshot of one page).
  pdf: a PDF with a text layer, base64.
  file_path: a JPEG/PNG, PDF or text file on this machine (local server only).
instructions: optional guidance, e.g. "dates are day/month/year" or "amounts in kobo".

Long documents (over 120,000 characters) are split into parts, extracted in parallel and merged; that can take
minutes. Missing values come back as null. Treat fields with confidence below about 0.95 as needing a check.

Input parameters:

- `file_path`
- `image`
- `instructions`
- `pdf`
- `template` (object, required)
- `text`

### `get_extraction_job` (~41 tokens)

The result of a long-document extraction job that extract_document left running (by its id, exj_...).

Input parameters:

- `job_id` (string, required)

### `decide` (~192 tokens)

Answer typed questions about a message, ticket, record or form, with a calibrated probability for each answer.

state: the thing to decide about: a string (e.g. a customer message) or a JSON object (a record).
questions: {question_id: {...}}, each one of:
  {"type": "noul", "instructions": "The customer is asking for a refund."}         -> probability it's true
  {"type": "choice", "instructions": "Which team?", "criteria": {"billing": "payments", "delivery": "orders"}}
  {"type": "score", "instructions": "How urgent?", "criteria": ["can wait", "today", "immediately"]}
Works in 19 languages, including English, Pidgin, Hausa, Yorùbá, Igbo, Swahili and Arabic.

Input parameters:

- `questions` (object, required)
- `state` (required)

### `detect_language` (~102 tokens)

Identify the language of a text among 608 languages (built African-first; good on very short text).

mode: "traffic" (user messages and chat; favours languages people actually use) or "coverage" (all languages
equal, for building corpora). Returns the ISO 639-3 code, script, name, confidence and runners-up.

Input parameters:

- `mode` (string)
- `text` (string, required)
- `top_k` (integer)

### `restore_diacritics` (~111 tokens)

Put back diacritics, tone marks or Arabic vowel marks in text typed without them.

language: yor (Yorùbá), ibo (Igbo), hau (Hausa), vie, pol, tur, por, spa, fra, ita or ara (Arabic).
Example: "se eranko naa si gbo o?" (yor) -> "ṣé ẹranko náà sì gbọ́ ọ?"

Input parameters:

- `language` (string, required)
- `text` (string, required)

### `generate_questions` (~201 tokens)

Write the questions a passage answers (MIST-QG-1.1, passages in 324 languages).

Useful for FAQs, study cards and search or RAG training data. passage: up to 100,000 characters (long ones are
split into ~2,000-character chunks and the questions spread over them). n: 1 to 100 (at most 5 per 2,000
characters), or "auto" to write as many as the passage supports. language: the passage's language (detected when
left out). question_language: write the questions in another language: English or French for any passage, or one
of 30 widely spoken languages (Spanish, Hindi, Chinese, Swahili, Yoruba, Amharic...) for an English or French
passage or one in those 30.

Input parameters:

- `language`
- `n`
- `passage` (string, required)
- `question_language`

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/olaverse-labs-olaverse-mcp/olaverse-mcp#diagnostics

## Score history

- 2026-11-21: 67
- 2026-11-20: 82
- 2026-11-19: 66
- 2026-11-18: 81
- 2026-11-17: 65
- 2026-11-16: 65
- 2026-11-15: 64
- 2026-11-14: 64
- 2026-11-13: 75
- 2026-11-12: 75
- 2026-11-11: 60
- 2026-11-10: 60
- 2026-11-09: 75
- 2026-11-08: 60
- 2026-11-07: 60
- 2026-11-06: 60

## Common questions

### What is the Olaverse Lab MCP server?

Olaverse Lab is an MCP server listed in the public MCP registry as io.github.Olaverse-Labs/olaverse-mcp. Document extraction, decisions, language ID (608), diacritics, questions in 324 languages. This page covers its PyPI package (olaverse-mcp).

### Is the Olaverse Lab MCP server safe to use?

Olaverse Lab scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. 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 Olaverse Lab MCP server expose?

Olaverse Lab exposes 6 tools: extract_document, get_extraction_job, decide, detect_language, restore_diacritics, generate_questions. Their descriptions and schemas cost roughly 994 tokens of context every time the server is loaded.

### Is the Olaverse Lab MCP server still maintained?

Olaverse Lab is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Olaverse Lab MCP server under?

Olaverse Lab declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Olaverse Lab MCP server?

VerifyMCP ran 15 checks on Olaverse Lab, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about Olaverse Lab: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- PyPI project: https://pypi.org/project/olaverse-mcp/
- Socket report: https://socket.dev/pypi/package/olaverse-mcp
- Repository: https://github.com/Olaverse-Labs/olaverse-mcp
- Website: https://www.olaverselab.com/
- Changelog RSS feed: https://verifymcp.io/servers/olaverse-labs-olaverse-mcp/olaverse-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/olaverse-labs-olaverse-mcp/olaverse-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/olaverse-labs-olaverse-mcp/olaverse-mcp.json
- HTML version of this page: https://verifymcp.io/servers/olaverse-labs-olaverse-mcp/olaverse-mcp
