Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Olaverse Lab

PYPI · OLAVERSE-MCP · 2 COMPONENTS

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

+3 this week 67 Trust /100

Last scanned (11 hours ago)

Scores higher than 60% of PyPI servers

Category Documents and Files

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 32 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Olaverse-Labs/olaverse-mcp). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 6 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability57
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 20 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 19 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 18 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 16 Nov 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.

  • 15 Nov 26 0
    • Package version: 0.3.0 → 0.3.1 functional
  • 14 Nov 26 −11
    • Malware scan: pass → unverified ▼ security
    • Schema quality: 165 → 183 ▼ functional
    • Stability: unverified → 0.27 ▲ functional
    • Package version: 0.2.1 → 0.3.0 functional
  • 12 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
Diagnostics

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 21 Nov 2026 · Analysed pypi/olaverse-mcp@0.3.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo Olaverse-Labs/olaverse-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Olaverse-Labs/olaverse-mcp/.github/workflows/publish.yml@refs/tags/v0.3.1
Rekor log index 3890805861
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:3f8897ee144cddfcd6c88ceb72d5b64252c5707df99ff96319c7e24850cc7182

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 32 packages
Packages resolved 32
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~994 tokens

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 →

Tool Tokens
decide ~192

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.

NameTypeReqDescription
questionsobjectyes–
state–yes–

No output schema declared.

No examples provided.

detect_language ~102

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.

NameTypeReqDescription
modestring––
textstringyes–
top_kinteger––

No output schema declared.

No examples provided.

extract_document ~347

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.

NameTypeReqDescription
file_path–––
image–––
instructions–––
pdf–––
templateobjectyes–
text–––

No output schema declared.

No examples provided.

generate_questions ~201

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.

NameTypeReqDescription
language–––
n–––
passagestringyes–
question_language–––

No output schema declared.

No examples provided.

get_extraction_job ~41

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

NameTypeReqDescription
job_idstringyes–

No output schema declared.

No examples provided.

restore_diacritics ~111

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ọ́ ọ?"

NameTypeReqDescription
languagestringyes–
textstringyes–

No output schema declared.

No examples provided.

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.

pypi · olaverse-mcp

# add to Claude Code
claude mcp add olaverse-labs-olaverse-mcp -- uvx olaverse-mcp
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.