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.

Ovellum

NPM · OVELLUM

Auto, manual, or hybrid docs that never fall out of sync.

Available components

−1 this week 85 Trust /100

Last scanned (20 hours ago)

Scores higher than 87% of npm servers

Category Developer Tools

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 Security93
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known medium-severity CVE affects minimatch 10.2.6, reached via ts-morph > @ts-morph/common > minimatch. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 52 of 167 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability87
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 689 tokens (~68/item across 10 items; 9 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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
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.

  • 4 Nov 26 0
    • Dependency health: partial → 0.83 functional
  • 2 Nov 26 0
    • Dependency health: 0.83 → partial functional
  • 31 Oct 26 −1
    • CVE-2026-118764 affects this package: medium ▼ security
    • Known CVEs: pass → fail ▼ security
  • 30 Oct 26 0
    • Stability: 0.97 → pass security
  • 29 Oct 26 0
    • Stability: pass → 0.97 functional
  • 23 Oct 26 0
    • CVE-2026-97058 no longer affects this package ▲ security
    • Known CVEs: partial → pass ▲ security
    • Stability: 0.97 → pass security
  • 22 Oct 26 +1

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

  • 21 Oct 26 −1
    • Stability: pass → 0.93 functional
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 4 Nov 2026 · Analysed npm/ovellum@0.24.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-g3hv-75wg-m249 CVE-2026-118764 medium yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 167 packages
Packages resolved 167
Stale 52
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~672 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
ovellum_build ~42

Run an Ovellum build (parse + generate + merge, or site build). Returns the build summary.

NameTypeReqDescription
draftsboolean–Include draft pages.

No output schema declared.

No examples provided.

ovellum_check ~68

Validate the project without writing: broken internal links, unsafe URL schemes, and stale translations (and, with strict, id-less protected zones, stale anchors, and title-less pages). Returns counts and a per-issue list.

NameTypeReqDescription
strictboolean–Run the stricter validations too.

No output schema declared.

No examples provided.

ovellum_diff ~39

Compare the current source against the last build IR snapshot. Returns added / removed / changed / renamed symbols and which docs would change. Read-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ovellum_get_page ~63

Read a built page's Markdown from the output directory (the AI-friendly .md mirror). Path is relative to the output dir; must stay inside it.

NameTypeReqDescription
pathstringyesPath under the output dir, e.g. "guide/intro.md".

No output schema declared.

No examples provided.

ovellum_list_orphans ~66

List quarantined manual blocks under protect.orphanDir, with age, last-seen, and (vs the IR snapshot) whether each anchor is back in source. Optional stale filter.

NameTypeReqDescription
staleboolean–Only orphans older than protect.orphanRetention days.

No output schema declared.

No examples provided.

ovellum_query_symbol ~79

Look up a documented symbol in the persisted IR snapshot by exact anchor id or by name. Returns kind, signature, source location, description, params, and returns.

NameTypeReqDescription
idstring–Exact anchor id, e.g. "src/math.ts::add".
namestring–Symbol name to match (returns all matches).

No output schema declared.

No examples provided.

ovellum_reattach ~123

Rescue an orphaned manual block: splice its prose back into a @manual zone under a target anchor (defaulting to the suggested present-again / renamed anchor) and remove the archive, or delete the orphan. The non-interactive counterpart of `ovellum orphans --reattach`.

NameTypeReqDescription
anchorIdstringyesThe orphan to act on (its original anchor id).
deleteboolean–Delete the orphan instead of reattaching.
targetstring–Anchor id to reattach under (default: the suggested target).

No output schema declared.

No examples provided.

ovellum_search_docs ~64

Full-text search over the built docs. Returns ranked pages with a path, title, score, and snippet. Run a build first so the output exists.

NameTypeReqDescription
limitnumber–Max results (default 10).
querystringyesSearch terms.

No output schema declared.

No examples provided.

ovellum_write_zone ~128

Write Markdown prose into a protected @manual zone under an anchor id, so it survives the next hybrid regeneration. Inserts a new block or replaces an existing one with the same blockId. Use dryRun to preview without writing. Survival requires hybrid mode.

NameTypeReqDescription
anchorIdstringyesAnchor the block attaches to, e.g. "src/math.ts::add".
blockIdstring–Stable id for the block (default "agent-note").
contentstringyesMarkdown body of the protected block.
dryRunboolean–Preview the change without writing.

No output schema declared.

No examples provided.

Install

How do I install the Ovellum MCP server?

Ovellum runs locally as an npm package, launched with npx -y ovellum. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · ovellum

# add to Claude Code
claude mcp add oinam-ovellum -- npx -y ovellum
Common questions

What is the Ovellum MCP server?

Ovellum is an MCP server listed in the public MCP registry as io.github.oinam/ovellum. Auto, manual, or hybrid docs that never fall out of sync. This page covers its npm package (ovellum).

Is the Ovellum MCP server safe to use?

Ovellum scores 85 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. 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 Ovellum MCP server expose?

Ovellum exposes 9 tools: ovellum_query_symbol, ovellum_diff, ovellum_check, ovellum_list_orphans, ovellum_get_page, and 4 more. Their descriptions and schemas cost roughly 672 tokens of context every time the server is loaded.

Is the Ovellum MCP server still maintained?

Ovellum is still listed as active in the MCP registry. We last reached this channel on 4 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 Ovellum MCP server under?

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