Obsidian Vault MCP
PYPI · ZOTERO-OBSIDIAN-MCP
Local Zotero, MinerU, Obsidian literature workflow with transactional Analysis notes.
Available components
Last scanned (22 hours ago)
Scores higher than 57% of PyPI servers
Category Education and Research
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 setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Build provenance not yet verified. View diagnostics → Unverified
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 84 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability51
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 1591 tokens (~51/item across 31 items; 31 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 31 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
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 −15
- Malware scan: pass → unverified ▼ security
- Provenance: fail → unverified ▼ security
- Security disclosure: fail → unverified ▼ functional
- 3 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −21
- Provenance: unverified → fail ▼ security
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.60 functional
- 1 Nov 26 +15
- Provenance: fail → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
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 pypi/zotero-obsidian-mcp@3.0.2
Provenance Inconclusive
We could not complete the check, so nothing is claimed either way. This is a gap on our side, not a finding about the package.
| Result | Inconclusive |
|---|---|
| Ecosystem | pypi |
| Reason | Attestation not fetched |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
literature_analysis_get ~65
Get Analysis notes by stable ID, type, source key, or duplicate-question lookup.
| Name | Type | Req | Description |
|---|---|---|---|
| analysis_id | string | – | – |
| analysis_type | string | – | – |
| question | string | – | – |
| source_key | string | – | – |
| vault_path | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
literature_analysis_write ~79
Validate and transactionally write one Analysis note while preserving user-owned content.
| Name | Type | Req | Description |
|---|---|---|---|
| conflict_policy | string | – | – |
| dry_run | boolean | – | – |
| fields | object | yes | – |
| managed_content | string | yes | – |
| reviewed_by_user | boolean | – | – |
| transaction_id | string | – | – |
| vault_path | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
literature_config_get ~24
Return the validated effective Vault configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| vault_path | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
literature_config_initialize ~50
Create the Vault configuration through the transaction engine.
| Name | Type | Req | Description |
|---|---|---|---|
| conflict_policy | string | – | – |
| dry_run | boolean | – | – |
| transaction_id | string | – | – |
| vault_path | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
literature_config_validate ~36
Validate supplied JSON or the Vault's single configuration file.
| Name | Type | Req | Description |
|---|---|---|---|
| config_json | string | – | – |
| vault_path | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
literature_doctor ~35
Check Vault configuration, Zotero status, MinerU availability, and the exposed tool list.
| Name | Type | Req | Description |
|---|---|---|---|
| vault_path | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
literature_import_collection ~62
Import every parent item in a fully paginated Zotero collection.
| Name | Type | Req | Description |
|---|---|---|---|
| collection_key | string | yes | – |
| conflict_policy | string | – | – |
| dry_run | boolean | – | – |
| transaction_id | string | – | – |
| vault_path | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
literature_import_item ~62
Import or idempotently refresh one Zotero parent item.
| Name | Type | Req | Description |
|---|---|---|---|
| conflict_policy | string | – | – |
| dry_run | boolean | – | – |
| transaction_id | string | – | – |
| vault_path | string | – | – |
| zotero_key | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
literature_paper_read ~94
Read bounded, source-linked text or figures from one paper without persisting derived state.
| Name | Type | Req | Description |
|---|---|---|---|
| include_images | boolean | – | – |
| max_chars | integer | – | – |
| mode | string | – | – |
| query | string | – | – |
| query_variants | – | – | – |
| sections | – | – | – |
| top_k | integer | – | – |
| vault_path | string | – | – |
| zotero_key | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
literature_parse_mineru ~62
Parse one Vault PDF through staged MinerU normalization.
| Name | Type | Req | Description |
|---|---|---|---|
| conflict_policy | string | – | – |
| dry_run | boolean | – | – |
| transaction_id | string | – | – |
| vault_path | string | – | – |
| zotero_key | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
literature_parse_mineru_batch ~63
Parse several imported items with the configured concurrency limit.
| Name | Type | Req | Description |
|---|---|---|---|
| conflict_policy | string | – | – |
| dry_run | boolean | – | – |
| transaction_id | string | – | – |
| vault_path | string | – | – |
| zotero_keys | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
literature_preview_transaction ~35
Read the safe manifest for an existing committed transaction.
| Name | Type | Req | Description |
|---|---|---|---|
| transaction_id | string | yes | – |
| vault_path | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
literature_rebuild_analysis_base ~58
Create or update the single nine-view Literature/Analysis/Analysis.base file.
| Name | Type | Req | Description |
|---|---|---|---|
| conflict_policy | string | – | – |
| dry_run | boolean | – | – |
| transaction_id | string | – | – |
| vault_path | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
literature_rebuild_base ~52
Deterministically rebuild Literature/Literature.base.
| Name | Type | Req | Description |
|---|---|---|---|
| conflict_policy | string | – | – |
| dry_run | boolean | – | – |
| transaction_id | string | – | – |
| vault_path | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
literature_rebuild_index ~50
Deterministically rebuild Literature/index.md.
| Name | Type | Req | Description |
|---|---|---|---|
| conflict_policy | string | – | – |
| dry_run | boolean | – | – |
| transaction_id | string | – | – |
| vault_path | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
literature_remove_mineru_output ~64
Remove derived MinerU assets through a backed-up transaction.
| Name | Type | Req | Description |
|---|---|---|---|
| conflict_policy | string | – | – |
| dry_run | boolean | – | – |
| transaction_id | string | – | – |
| vault_path | string | – | – |
| zotero_key | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
literature_retrieve ~110
Retrieve bounded paper matches and source passages with request-local coverage only.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | string | – | – |
| intent | string | – | – |
| max_candidate_papers | integer | – | – |
| max_snippet_papers | integer | – | – |
| max_total_snippets | integer | – | – |
| methods | – | – | – |
| per_paper_top_k | integer | – | – |
| query | string | – | – |
| query_variants | – | – | – |
| scope | – | – | – |
| vault_path | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
literature_rollback_transaction ~53
Preview or restore every file backed up by a transaction.
| Name | Type | Req | Description |
|---|---|---|---|
| conflict_policy | string | – | – |
| dry_run | boolean | – | – |
| transaction_id | string | yes | – |
| vault_path | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
literature_sync_collection ~61
Incrementally sync existing items from a fully paginated collection.
| Name | Type | Req | Description |
|---|---|---|---|
| collection_key | string | yes | – |
| conflict_policy | string | – | – |
| dry_run | boolean | – | – |
| transaction_id | string | – | – |
| vault_path | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
literature_sync_item ~58
Incrementally sync an existing literature item.
| Name | Type | Req | Description |
|---|---|---|---|
| conflict_policy | string | – | – |
| dry_run | boolean | – | – |
| transaction_id | string | – | – |
| vault_path | string | – | – |
| zotero_key | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
literature_verify ~28
Verify identities, links, portable paths, and generated assets.
| Name | Type | Req | Description |
|---|---|---|---|
| vault_path | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
literature_version ~18
Return the production package version and public capability counts.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
literature_wiki_context ~45
Collect traceable local literature context for an Agent-authored topic.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| topic | string | yes | – |
| vault_path | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
literature_wiki_list ~24
List deterministic Wiki topic metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| vault_path | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
literature_wiki_write ~77
Validate sources and safely write an Agent-authored Wiki topic.
| Name | Type | Req | Description |
|---|---|---|---|
| conflict_policy | string | – | – |
| content | string | yes | – |
| dry_run | boolean | – | – |
| topic | string | yes | – |
| transaction_id | string | – | – |
| vault_path | string | – | – |
| zotero_keys | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
zotero_get_bibtex ~52
Get BibTeX using Better BibTeX, Zotero export, then builtin fallback.
| Name | Type | Req | Description |
|---|---|---|---|
| api_base | string | – | – |
| key | string | yes | – |
| provider | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
zotero_get_children ~39
Get all notes, annotations, attachments, and other child items.
| Name | Type | Req | Description |
|---|---|---|---|
| api_base | string | – | – |
| parent_key | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
zotero_get_item ~32
Get one normalized Zotero item.
| Name | Type | Req | Description |
|---|---|---|---|
| api_base | string | – | – |
| key | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
zotero_list_collections ~28
List every Zotero collection using complete pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| api_base | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
zotero_ping ~25
Check the Zotero Desktop local API.
| Name | Type | Req | Description |
|---|---|---|---|
| api_base | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
zotero_search_items ~50
Search all matching Zotero items using complete pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| api_base | string | – | – |
| item_type | string | – | – |
| query | string | – | – |
| tag | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
How do I install the Obsidian Vault MCP server?
Obsidian Vault MCP runs locally as a PyPI package, launched with uvx zotero-obsidian-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 · zotero-obsidian-mcp
claude mcp add luffysolution-svg-obsidian-vault-mcp -- uvx zotero-obsidian-mcp
What is the Obsidian Vault MCP server?
Obsidian Vault MCP is listed in the public MCP registry as io.github.luffysolution-svg/obsidian-vault-mcp. Local Zotero, MinerU, Obsidian literature workflow with transactional Analysis notes. This page covers its PyPI package (zotero-obsidian-mcp).
Is the Obsidian Vault MCP server safe to use?
Obsidian Vault MCP scores 58 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. 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 Obsidian Vault MCP server expose?
Obsidian Vault MCP exposes 31 tools: literature_version, literature_doctor, literature_config_get, literature_config_validate, literature_config_initialize, and 26 more. Their descriptions and schemas cost roughly 1,591 tokens of context every time the server is loaded.
Is the Obsidian Vault MCP server still maintained?
Obsidian Vault MCP 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 Obsidian Vault MCP server under?
Obsidian Vault MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.