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

REMOTE · MCP.OLAVERSELAB.COM · 2 COMPONENTS

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

+4 this week 66 Trust /100

Last scanned (21 hours ago)

Scores higher than 51% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Documents and Files

Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability58
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1148 tokens (~191/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 (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • 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 hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

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 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1
    • Tool “generate_questions” rewrote its description, which is the text the model reads security
    • Tool “extract_document” rewrote its description, which is the text the model reads security
  • 14 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “generate_questions” rewrote its description, which is the text the model reads security
    • Schema quality: 168 → 187 ▼ functional
    • “generate_questions” added an optional parameter “question_language” cosmetic
  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

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 · Probed https://mcp.olaverselab.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.olaverselab.com CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US 6 Nov 2026 6 May 2027 RSA 2048 SHA256-RSA 550f4331260136c917555a9b86433e9
SANs: mcp.olaverselab.com
CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 2 Nov 2017 2 Nov 2027 RSA 2048 SHA256-RSA d07782a133fc6f9a57296e131ffd179
CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 1 Aug 2013 15 Jan 2038 RSA 2048 SHA256-RSA 33af1e6a711a9a0bb2864b11d09fae5

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.olaverselab.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
olaverselab.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.olaverselab.com/mcp Verified 200
http (plaintext) http://mcp.olaverselab.com/mcp HTTPS enforced 301 https://mcp.olaverselab.com/mcp
MCP tools · 6 exposed · ~1,016 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 ~196

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 ~105

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 ~353

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 ~207

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 ~114

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 is a hosted endpoint at https://mcp.olaverselab.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.olaverselab.com

# add to Claude Code
claude mcp add --transport http olaverse-labs-olaverse-mcp 'https://mcp.olaverselab.com/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 hosted endpoint (https://mcp.olaverselab.com/mcp).

Is the Olaverse Lab MCP server safe to use?

Olaverse Lab scores 66 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 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 1,016 tokens of context every time the server is loaded.

Does the Olaverse Lab MCP server require authentication?

No. We connected to Olaverse Lab without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

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 did VerifyMCP test on the Olaverse Lab MCP server?

VerifyMCP ran 12 checks on Olaverse Lab, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Olaverse Lab: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.