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.

Docmancer

PYPI · DOCMANCER · SCANNED AUG 5

Local-only MCP server for source-attributed Markdown memory and documentation retrieval.

Available components

36 Trust /100
Trust breakdown (6 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 →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 5 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
Schema Quality & AI Usability0
  • Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Stability & Change Management0
  • Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Tool Coverage0
  • Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Capabilities0
  • Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.Unverified

Unverified: 4 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

pypi · docmancer

# add to Claude Code
claude mcp add dev-docmancer-docmancer -- uvx docmancer
# add to Codex CLI
codex mcp add dev-docmancer-docmancer -- uvx docmancer
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-docmancer-docmancer": {
      "type": "local",
      "command": [
        "uvx",
        "docmancer"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dev-docmancer-docmancer --command uvx --arg docmancer
# ~/.hermes/config.yaml
mcp_servers:
  dev-docmancer-docmancer:
    command: "uvx"
    args: ["docmancer"]
// mcp.json
{
  "mcpServers": {
    "dev-docmancer-docmancer": {
      "command": "uvx",
      "args": [
        "docmancer"
      ]
    }
  }
}
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.

  • 5 Aug 26 +15
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 functional
    • MCP protocol: unverified → pass functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 30 functional
    • First check of Schema quality: good functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: fail functional
    • Package version: 0.9.12 → 0.9.14 functional
    • Package version: 0.9.12 → 0.9.13 functional
  • 4 Aug 26 21

    First indexed and scored.

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 5 Aug 2026 · Analysed pypi/[email protected]

Provenance No attestation

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

Result No attestation
Ecosystem pypi
Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build
Dependencies 93 packages
Packages resolved 93
Stale 5
Tree resolution Complete
MCP tools — 20 exposed · ~2,650 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.

Tool Tokens
ask_memory ~278

READ-ONLY: recall one bounded bundle of mandatory policy, curated memory, and supporting indexed agent evidence for a task. Returns an empty bundle when no relevant local memory exists. Set answer=true to use the configured provider for a grounded cited answer. Answer generation defaults to false. Aliases: query for task, budget for token_budget.

NameTypeReqDescription
agentstringTarget agent identifier used when building a context projection or recording an ask. Defaults are tool-specific.
answerbooleanWhen true, use the configured provider to generate a grounded cited answer from recalled memory.
budgetAlias for token_budget. Use token_budget when possible.
include_historybooleanWhen true, include historical or superseded memory evidence in addition to active evidence.
limitintegerMaximum number of matching results to return. Defaults are tool-specific.
modestringRecall mode. Defaults to normal.
project_pathOptional project root that scopes the operation. Omit it when the server was started with a project pin.
queryAlias for task. Use task when possible.
taskNatural-language task to recall relevant policy, memory, and evidence for. Required unless query is supplied.
token_budgetMaximum token budget for the returned context bundle. Omit to use the tool default.

No output schema declared.

No examples provided.

canonical_memory ~123

READ-ONLY: read the machine-wide canonical memory, which is what docmancer has reconciled about this user across every agent and project (about, preferences, working-principles, active-projects). Omit section for the status of all sections; pass section for that section split into its pinned and generated zones. Call this to find out what is already known about the user before asking them.

NameTypeReqDescription
sectionCanonical section name: about, preferences, working-principles, or active-projects. Omit only where the tool documents a status response.

No output schema declared.

No examples provided.

common_memory ~69

READ-ONLY: show memories recurring across two or more independent agent harnesses. Generated Docmancer integration copies are excluded. Results are recurrence evidence, not consensus or truth.

NameTypeReqDescription
project_pathOptional project root that scopes the operation. Omit it when the server was started with a project pin.
NameTypeReqDescription
resultyes

No examples provided.

context_delivery ~58

READ-ONLY: show each supported agent's integration mode, hook status, and latest observed context bundle revision and hash.

NameTypeReqDescription
project_pathOptional project root that scopes the operation. Omit it when the server was started with a project pin.
NameTypeReqDescription
resultyes

No examples provided.

context_projection ~108

READ-ONLY: render a bounded revision-linked Context projection for an agent without writing or refreshing it. Context refresh, rollback, adopt, and retire are human-only.

NameTypeReqDescription
agentstringyesTarget agent identifier used when building a context projection or recording an ask. Defaults are tool-specific.
project_pathOptional project root that scopes the operation. Omit it when the server was started with a project pin.
token_budgetintegerMaximum token budget for the returned context projection.

No output schema declared.

No examples provided.

context_status ~72

READ-ONLY: inspect the current consolidated Context revision, freshness, exclusions, and cluster metadata. Context refresh, rollback, adopt, and retire are intentionally human-only CLI or local-web operations.

NameTypeReqDescription
project_pathOptional project root that scopes the operation. Omit it when the server was started with a project pin.

No output schema declared.

No examples provided.

decision_timeline ~129

READ-ONLY: show the append-only timeline of canonical memory file creates, edits, moves, duplicates, trash operations, and restores, including human-readable diffs.

NameTypeReqDescription
file_idOptional stable memory file identifier used to filter the timeline.
limitintegerMaximum number of matching results to return. Defaults are tool-specific.
operationOptional operation name used to filter the timeline, such as create, edit, move, trash, or restore.
project_pathOptional project root that scopes the operation. Omit it when the server was started with a project pin.
NameTypeReqDescription
resultyes

No examples provided.

docmancer_docs_search ~62

Search the local docmancer docs index. Local only.

NameTypeReqDescription
limitintegerMaximum number of matching results to return. Defaults are tool-specific.
querystringyesNatural-language terms to search for in the local memory or documentation index.
NameTypeReqDescription
resultarrayyes

No examples provided.

docmancer_memory_search ~111

Search the local docmancer memory index (agent memory, instructions, rules). Local only.

NameTypeReqDescription
expand_relationsbooleanWhen true, include related memory items alongside direct matches.
include_historybooleanWhen true, include historical or superseded memory evidence in addition to active evidence.
limitintegerMaximum number of matching results to return. Defaults are tool-specific.
querystringyesNatural-language terms to search for in the local memory or documentation index.
NameTypeReqDescription
resultarrayyes

No examples provided.

docmancer_memory_status ~29

Report docmancer memory index status (path, source/section counts). Local only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

duplicate_memory ~121

MUTATING: duplicate one tree-memory file under a new stable identity and relative path.

NameTypeReqDescription
addressstringyesStable docmancer://memory address, relative path, or exact title of the memory file.
expected_hashstringyesCurrent content_hash returned by a prior read. This prevents overwriting a newer revision.
new_relative_pathstringyesRelative path for the new memory file inside its selected memory tree.
project_pathOptional project root that scopes the operation. Omit it when the server was started with a project pin.

No output schema declared.

No examples provided.

edit_memory ~219

MUTATING: replace the body of one tree-memory file, preserving its other frontmatter. Requires the file's current content_hash in expected_hash; a stale hash fails safely with a structured error naming the safe re-read-and-retry next action. Aliases: target for address, content for text, hash for expected_hash.

NameTypeReqDescription
addressStable docmancer://memory address, relative path, or exact title of the memory file. Required unless an address alias is supplied.
contentAlias for text. Use text when possible.
expected_hashCurrent content_hash returned by a prior read. Required for guarded edits, moves, and deletes unless hash is supplied.
hashAlias for expected_hash. Use expected_hash when possible.
project_pathOptional project root that scopes the operation. Omit it when the server was started with a project pin.
targetAlias for address. Use the canonical address field when possible.
textMarkdown body to write or replace. Required unless content is supplied.

No output schema declared.

No examples provided.

move_memory ~229

MUTATING, DESTRUCTIVE at the old path: move or rename one tree-memory file. Its stable address survives the move, but the old path stops resolving. Requires the file's current content_hash in expected_hash. Aliases: target for address, new_path for new_relative_path, hash for expected_hash.

NameTypeReqDescription
addressStable docmancer://memory address, relative path, or exact title of the memory file. Required unless an address alias is supplied.
expected_hashCurrent content_hash returned by a prior read. Required for guarded edits, moves, and deletes unless hash is supplied.
hashAlias for expected_hash. Use expected_hash when possible.
new_pathAlias for new_relative_path. Use new_relative_path when possible.
new_relative_pathRelative path for the memory file inside its selected memory tree. Required unless path is supplied.
project_pathOptional project root that scopes the operation. Omit it when the server was started with a project pin.
targetAlias for address. Use the canonical address field when possible.

No output schema declared.

No examples provided.

pin_memory ~141

MUTATING: pin one durable line into a canonical memory section (about, preferences, working-principles, active-projects). The pinned zone is the ONLY part of a canonical section that survives automatic reconciliation, so use this (not edit_memory) for any correction, standing preference, or fact the reconciler got wrong or left out. Idempotent: pinning the same line twice changes nothing.

NameTypeReqDescription
sectionCanonical section name: about, preferences, working-principles, or active-projects. Omit only where the tool documents a status response.
textComplete durable line to add to the selected canonical section's pinned zone.

No output schema declared.

No examples provided.

read_memory ~158

READ-ONLY: read one tree-memory file by stable address, relative path, or exact title. Ambiguous title/path matches return every candidate address instead of guessing. Example: address='docmancer://memory/01J...'. Aliases: target or memory_id for address.

NameTypeReqDescription
addressStable docmancer://memory address, relative path, or exact title of the memory file. Required unless an address alias is supplied.
memory_idAlias for address that accepts a stable memory identifier. Use address when possible.
project_pathOptional project root that scopes the operation. Omit it when the server was started with a project pin.
targetAlias for address. Use the canonical address field when possible.

No output schema declared.

No examples provided.

restore_memory ~68

MUTATING: restore one tree-memory file from a prior trash restore token.

NameTypeReqDescription
project_pathOptional project root that scopes the operation. Omit it when the server was started with a project pin.
restore_tokenstringyesRestore token returned by trash_memory for the file to restore.

No output schema declared.

No examples provided.

search_memory ~129

READ-ONLY: lexical search over one tree's active memory. Returns [] (not an error) when nothing is relevant or the tree is empty. Example: query='prior deployment decision'. Alias: text for query.

NameTypeReqDescription
limitintegerMaximum number of matching results to return. Defaults are tool-specific.
project_pathOptional project root that scopes the operation. Omit it when the server was started with a project pin.
queryNatural-language terms to search for. Required unless the text alias is supplied.
textAlias for query. Use query when possible.
NameTypeReqDescription
resultyes

No examples provided.

trash_memory ~104

DESTRUCTIVE BUT REVERSIBLE: move one tree-memory file to trash and return a restore token.

NameTypeReqDescription
addressstringyesStable docmancer://memory address, relative path, or exact title of the memory file.
expected_hashstringyesCurrent content_hash returned by a prior read. This prevents overwriting a newer revision.
project_pathOptional project root that scopes the operation. Omit it when the server was started with a project pin.

No output schema declared.

No examples provided.

unpin_memory ~88

MUTATING: remove pinned lines from a canonical memory section by case-insensitive substring match. Fails without changing anything when nothing matches.

NameTypeReqDescription
sectionCanonical section name: about, preferences, working-principles, or active-projects. Omit only where the tool documents a status response.
textCase-insensitive substring identifying pinned lines to remove from the selected section.

No output schema declared.

No examples provided.

write_memory ~354

MUTATING: create or update one curated tree-memory file (docmancer://memory/<id>). expect='absent' (default) is create-only; pass the current content_hash for a guarded update. Returns the stable address, content_hash, and revision id for follow-up calls. Example: relative_path='deployment/release.md', text='# Release\n\nUse Railway.' Aliases: path for relative_path, content for text.

NameTypeReqDescription
authoritystringAuthority level stored in frontmatter. Defaults to advisory.
contentAlias for text. Use text when possible.
curation_originstringOrigin label stored in frontmatter. Defaults to deliberate_write.
expectCreate/update guard. Use absent for create-only, or pass the current content hash for a guarded update.
memory_typestringMemory classification stored in frontmatter. Defaults to fact.
pathAlias for relative_path. Use relative_path when possible.
project_idOptional project identifier stored in the memory file frontmatter.
project_pathOptional project root that scopes the operation. Omit it when the server was started with a project pin.
relative_pathRelative path for the memory file inside its selected memory tree. Required unless path is supplied.
scopestringMemory visibility scope. Use global for shared memory or project for project-scoped memory.
sourcesOptional source references that support the memory content.
statusstringLifecycle status stored in frontmatter. Defaults to active.
tagsOptional labels used to classify and retrieve the memory content.
textMarkdown body to write or replace. Required unless content is supplied.

No output schema declared.

No examples provided.