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.

ragnarok

PYPI · RAGNAROK-MCP

Local RAG search over Obsidian vaults: SQLite hybrid search with local Ollama embeddings.

Available components

−12 this week 68 Trust /100

Last scanned (15 hours ago)

Scores higher than 61% of PyPI servers

Category Memory and Knowledge

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 freyr/ragnarok-bundle). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 9 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 557 tokens (~92/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 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
  • 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.

  • 19 Nov 26 +1

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

  • 17 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
  • 16 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 15 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
  • 14 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 13 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
  • 12 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 11 Nov 26 +1
    • First check of Tool coverage: 100 functional
    • Package version: 2.1.1 → 2.3.0 functional
    • Package version: 2.1.1 → 2.2.2 functional
    • Package version: 2.1.1 → 2.2.1 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 21 Nov 2026 · Analysed pypi/ragnarok-mcp@2.3.0

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 freyr/ragnarok-bundle
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/freyr/ragnarok-bundle/.github/workflows/publish.yml@refs/tags/server-v2.3.0
Rekor log index 3813551280
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:79090accd0e67c535643f1e3543b4b7bee2ffe53a87a2d2f5f56435e60401b4b

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 · ~474 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
find_by_jira ~31

The notes that contain a Jira key, for example ABC-123.

NameTypeReqDescription
keystringyes–

Structured output declared, but exposes no named fields.

No examples provided.

find_projects ~66

Find the earlier projects that a prompt continues or resembles, ranked by their matching notes. Each project has its slug, vault, folder, description, stage, state, next action and matching notes.

NameTypeReqDescription
limitinteger––
querystringyes–
vault–––

Structured output declared, but exposes no named fields.

No examples provided.

list_project ~44

All notes of a project in any folder, with type, status and description, with stage, state, next action.

NameTypeReqDescription
projectstringyes–
vault–––

Structured output declared, but exposes no named fields.

No examples provided.

open_note ~127

The text of a note (or of one section, by heading), its frontmatter, links and backlinks. outline=true gives the sections (heading path, words, first sentence) instead of the text. A note of more than 4000 words gives the outline unless outline=false; then open the section you need by heading, as the last heading or the full path such as "Results > Inferences". Credentials in the text are replaced with [REDACTED]. Private notes are refused.

NameTypeReqDescription
heading–––
outline–––
pathstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

open_projects ~81

The projects that are open, grouped by the state in their SUMMARY.md, newest update first. states defaults to in-progress and paused; the other values are done, superseded and abandoned. Each project has its slug, vault, folder, description, stage, state, gate, updated date and next action.

NameTypeReqDescription
states–––
vault–––

Structured output declared, but exposes no named fields.

No examples provided.

search ~125

Hybrid search (meaning and keywords) over the vault notes. Returns notes, each with its best section. Filters: vault (the name of a vault folder), project (folder slug), area, type (research, spec, plan, summary, drivers, guide, note, ...). include_private works only when the user allows it.

NameTypeReqDescription
area–––
include_archivedboolean––
include_privateboolean––
limitinteger––
project–––
querystringyes–
type–––
vault–––

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the ragnarok MCP server?

ragnarok runs locally as a PyPI package, launched with uvx ragnarok-mcp serve. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · ragnarok-mcp

# add to Claude Code
claude mcp add freyr-ragnarok -- uvx ragnarok-mcp serve
Common questions

What is the ragnarok MCP server?

ragnarok is an MCP server listed in the public MCP registry as io.github.freyr/ragnarok. Local RAG search over Obsidian vaults: SQLite hybrid search with local Ollama embeddings. This page covers its PyPI package (ragnarok-mcp).

Is the ragnarok MCP server safe to use?

ragnarok scores 68 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 ragnarok MCP server expose?

ragnarok exposes 6 tools: search, find_projects, list_project, open_projects, open_note, find_by_jira. Their descriptions and schemas cost roughly 474 tokens of context every time the server is loaded.

Is the ragnarok MCP server still maintained?

ragnarok 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 ragnarok MCP server under?

ragnarok declares the MIT 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 ragnarok MCP server?

VerifyMCP ran 15 checks on ragnarok, 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 ragnarok: 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.