Olaverse Lab MCP server
io.github.Olaverse-Labs/olaverse-mcpOlaverse-Labsstreamable-httpv0.3.1Scanned
Document extraction, decisions, language ID (608), diacritics, questions in 324 languages.
6 tools: 5 change things and 1 only read.
- Reads private data · 1
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
5 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Olaverse Lab MCP server can do
The Olaverse Lab MCP server is published by the GitHub account Olaverse-Labs. It has 6 tools. It can create or change data (5 tools: extract_document, decide, detect_language, restore_diacritics and 1 more), but cannot delete data. 1 tool only reads.
1 tool reads private data (get_extraction_job).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 15, 2026, version 0.3.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 5Claude Code: ask
decideAnswer typed questions about a message, ticket, record or form, with a calibrated probability for each answer.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
detect_languageIdentify the language of a text among 608 languages (built African-first; good on very short text).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
extract_documentTurn a document into JSON shaped like `template`, with a calibrated confidence (0-1) for every field.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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 60,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.
generate_questionsWrite the questions a passage answers (MIST-QG-1.1, passages in 324 languages).No findings
Why it is in this group
- The name "generate_questions" says "generate": a word for a change.
Description, as the server wrote it 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 8,000 characters, best under 2,000. n: 1 to 5, 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.
restore_diacriticsPut back diacritics, tone marks or Arabic vowel marks in text typed without them.No findings
Why it is in this group
- The description's first verb is "put": a word for a change.
Description, as the server wrote it 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ọ́ ọ?"
Only reads 1Show 1 read-only tool
get_extraction_jobThe result of a long-document extraction job that extract_document left running (by its id, exj_...).Reads private dataNo findings
Why it is in this group
- The name "get_extraction_job" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "document": it reads documents.
Description, as the server wrote it The result of a long-document extraction job that extract_document left running (by its id, exj_...).
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 21, 2026, 19:22 UTC, unchanged since Nov 7, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 5
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.olaverselab.com/mcp: tools/list returned 6 tools to an anonymous client, including extract_document (write), decide (write), detect_language (write), restore_diacritics (write), generate_questions (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:generate_questionsChanges thingsdescriptioninputSchema
Install
Pinned to version 0.3.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http olaverse https://mcp.olaverselab.com/mcp --header 'Authorization: <your-authorization>'claude mcp add --transport http olaverse https://mcp.olaverselab.com/mcp --header 'Authorization: <your-authorization>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__olaverse__get_extraction_job"
],
"ask": [
"mcp__olaverse__extract_document",
"mcp__olaverse__decide",
"mcp__olaverse__detect_language",
"mcp__olaverse__restore_diacritics",
"mcp__olaverse__generate_questions"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as olaverse. Review it before you use it.
Capability tags behind 1 rule
- mcp__olaverse__get_extraction_job private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Olaverse-Labs/olaverse-mcp/verify?hash=4891d6126f88ccacf958cb31b994c4c02219503c9c4f574ee20c6e40c3fc2bfa" | jq -e '.changed == false'Pinned hash 4891d6126f88, from Nov 15, 2026, 01:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.Olaverse-Labs/olaverse-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.Olaverse-Labs/olaverse-mcp)Source: MCP Registry · repository. Synced Nov 15, 2026, 02:17 UTC.
Olaverse Lab MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Olaverse Lab MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Olaverse Lab MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Olaverse Lab MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Olaverse Lab MCP server have?
- 6 tools: 5 write, 1 read. extract_document, decide, detect_language, restore_diacritics, generate_questions and get_extraction_job.
Does the Olaverse Lab MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Olaverse Lab MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Olaverse Lab MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 14, 2026. Every change is on this page and in its Atom feed.