io.github.juliangeymonat-jpg/wikimoth
PYPI · WIKIMOTH · 2 COMPONENTS
Deterministic, token-minimal agent memory: multi-hop [[wikilink]] recall with no LLM in the loop.
Available components
Last scanned (3 hours ago)
Scores higher than 64% of PyPI servers
Category Memory and Knowledge
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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 123 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 805 tokens (~115/item across 7 items; 7 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 Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 7 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 5 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 4 Nov 26 −1
- Stability: pass → 0.87 functional
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 28 Oct 26 0
- Stability: pass → 0.97 functional
- 22 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 21 Oct 26 0
- Stability: pass → 0.97 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 5 Nov 2026 · Analysed pypi/wikimoth@0.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
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 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
list_conflicts ~144
Deterministically list contradiction CANDIDATES in the WikiMoth vault: notes that assert different values for the same (subject, predicate). No model finds them. Each candidate is for YOU to adjudicate: decide if it is a real contradiction and which note is current. Notes tagged valid-time 'disjoint' are likely a legitimate succession (consider superseding), 'overlapping' is a real conflict. Use before trusting a possibly-stale fact recalled from memory.
| Name | Type | Req | Description |
|---|---|---|---|
| all_keys | boolean | – | compare every non-subject key, not just domain facts |
| include_inline | boolean | – | also read Dataview 'key:: value' inline body fields |
No output schema declared.
No examples provided.
list_duplicates ~108
Deterministically find exact and near-duplicate notes (MinHash/Jaccard, no model). WikiMoth capture is append-only and never merges, so content gets restated; this surfaces it. Candidates only: decide which to keep (consider superseding the older one).
| Name | Type | Req | Description |
|---|---|---|---|
| include_sessions | boolean | – | also scan session-* notes (skipped by default) |
| threshold | number | – | near-duplicate Jaccard threshold in (0,1] (default 0.8) |
No output schema declared.
No examples provided.
list_fading ~98
Deterministically list the 'fading' review queue: notes going cold (old, rarely linked, rarely recalled), scored by a decay + access + connectivity strength. Read-only, nothing is deleted. Use to suggest what the user might archive, refresh, or supersede.
| Name | Type | Req | Description |
|---|---|---|---|
| tau_days | number | – | decay time constant in days (default 90) |
| threshold | number | – | fading strength threshold (default 0.25) |
No output schema declared.
No examples provided.
list_lint ~110
Deterministically report vault-hygiene issues: broken [[links]], orphan notes, duplicate identities, empty stubs, stale/expired notes, and supersession chains/cycles. No model. Read-only. Use to check the memory's structural health or before trusting a possibly-broken link.
| Name | Type | Req | Description |
|---|---|---|---|
| include_sessions | boolean | – | include session-* notes in orphan/stub/stale checks |
| stale_days | integer | – | also flag notes whose mtime is older than N days (0 = off) |
No output schema declared.
No examples provided.
recall ~170
Deterministically recall the note-chain from the user's WikiMoth [[wikilink]] memory that answers a question. Walks the authored links (multi-hop), returns the exact notes with NO LLM call to retrieve, far fewer tokens than dumping the whole vault, and the same result every time. Call this before answering anything that might live in the user's notes, memory, or past sessions.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | time-travel: show the vault as it was valid at this ISO date (YYYY-MM-DD) |
| query | string | yes | the question or topic to recall from memory |
| show_superseded | boolean | – | include superseded note bodies (default false hides them, keeping the edge) |
| top_k | integer | – | max note chunks to return (default 8) |
No output schema declared.
No examples provided.
status ~42
Report the connected WikiMoth memory vault: path, note and chunk counts, whole-vault token size, and the token backend. Use to confirm memory is wired up.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
supersede ~133
Mark an OLD note as replaced by a NEW one, WITHOUT deleting it (invalidate-don't-delete: the file stays, its frontmatter records superseded_by/valid_to/status). Call this AFTER you have adjudicated that NEW genuinely replaces OLD (e.g. from a list_conflicts candidate). OLD/NEW are note stems, slugs, or paths.
| Name | Type | Req | Description |
|---|---|---|---|
| new | string | yes | the current note that replaces it |
| old | string | yes | the superseded note (stem/slug/path) |
| reason | string | – | optional audit note |
| reverse | boolean | – | also stamp replaces: on NEW |
No output schema declared.
No examples provided.
How do I install the io.github.juliangeymonat-jpg/wikimoth MCP server?
io.github.juliangeymonat-jpg/wikimoth runs locally as a PyPI package, launched with uvx wikimoth. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · wikimoth
claude mcp add juliangeymonat-jpg-wikimoth -- uvx wikimoth
What is the io.github.juliangeymonat-jpg/wikimoth MCP server?
io.github.juliangeymonat-jpg/wikimoth is an MCP server listed in the public MCP registry as io.github.juliangeymonat-jpg/wikimoth. Deterministic, token-minimal agent memory: multi-hop [[wikilink]] recall with no LLM in the loop. This page covers its PyPI package (wikimoth).
Is the io.github.juliangeymonat-jpg/wikimoth MCP server safe to use?
io.github.juliangeymonat-jpg/wikimoth scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 io.github.juliangeymonat-jpg/wikimoth MCP server expose?
io.github.juliangeymonat-jpg/wikimoth exposes 7 tools: recall, status, list_conflicts, list_lint, list_duplicates, and 2 more. Their descriptions and schemas cost roughly 805 tokens of context every time the server is loaded.
Is the io.github.juliangeymonat-jpg/wikimoth MCP server still maintained?
io.github.juliangeymonat-jpg/wikimoth is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.juliangeymonat-jpg/wikimoth MCP server under?
io.github.juliangeymonat-jpg/wikimoth declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.