# DocuSense (pypi · docusense-mcp)

Agents read PDFs and docs by section and claim: ~20x fewer tokens, hash-verified citations, diffs.

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- pypi · `docusense-mcp`: 66/100 (this document), [markdown](https://verifymcp.io/servers/hksharma2004-docusense/docusense-mcp.md), [page](https://verifymcp.io/servers/hksharma2004-docusense/docusense-mcp)

## Channel facts

- Registry: `pypi`
- Package: `docusense-mcp`
- Version: `0.1.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 49/100
  - Malware scan not yet available for this package.
  - Known CVEs were checked across the 84 of 86 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - Runs uv_build at install time, a recognised build step with no custom scripting around it.
  - Dependency health was assessed across the 84 of 86 dependencies we could resolve, so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to hksharma2004/docu-sense).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 76/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1735 tokens (~96/item across 18 items; 17 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the DocuSense MCP server?

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

### Claude

```bash
claude mcp add hksharma2004-docusense -- uvx docusense-mcp serve-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "hksharma2004-docusense": {
      "command": "uvx",
      "args": [
        "docusense-mcp",
        "serve-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "hksharma2004-docusense": {
      "command": "uvx",
      "args": [
        "docusense-mcp",
        "serve-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add hksharma2004-docusense -- uvx docusense-mcp serve-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hksharma2004-docusense": {
      "type": "local",
      "command": [
        "uvx",
        "docusense-mcp",
        "serve-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add hksharma2004-docusense --command uvx --arg docusense-mcp --arg serve-mcp
```

### Hermes

```yaml
mcp_servers:
  hksharma2004-docusense:
    command: "uvx"
    args: ["docusense-mcp", "serve-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "hksharma2004-docusense": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "docusense-mcp",
        "serve-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add hksharma2004-docusense -t stdio -c uvx -a docusense-mcp serve-mcp
```

### Other

```json
{
  "mcpServers": {
    "hksharma2004-docusense": {
      "command": "uvx",
      "args": [
        "docusense-mcp",
        "serve-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 66, −14)

- [security regression] Malware scan: pass → unverified
- [functional regression] Security disclosure: unverified → fail

### 2026-11-20 (score 80, +6)

- [security improvement] Source repository: fail → pass

### 2026-11-19 (score 74, +16)

- [security improvement] Malware scan: unverified → pass
- [functional improvement] Stability: unverified → 0.10

### 2026-11-16 (score 58)

First indexed and scored.

## MCP tools (17)

### `list_documents` (~27 tokens)

List every document with its versions (oldest→newest) and which version is latest.

### `get_section_map` (~107 tokens)

Table of contents of a document version: section numbers, titles, levels and page ranges.

doc: document id ('employee-handbook'), version id ('employee-handbook@v2') or, for RFCs, 'RFC 5321'.
Defaults to the latest version. max_depth: deepest heading level to include (1 = top-level only).

Input parameters:

- `doc` (string, required)
- `max_depth` (integer)
- `max_tokens` (integer)
- `version`

### `read_section` (~100 tokens)

Read the paragraphs of one section, each with a citation and SHA-256.

section: a section number ('4.5.3.1', 'A.1') or part of a title ('Terminology').
include_subsections: also return text of nested subsections.

Input parameters:

- `doc` (string, required)
- `include_subsections` (boolean)
- `max_tokens` (integer)
- `section` (string, required)
- `version`

### `search` (~112 tokens)

Find passages relevant to a query.

mode: 'lexical' (BM25: exact terms, numbers, identifiers), 'semantic' (embeddings: paraphrased
questions) or 'hybrid' (both, fused with reciprocal rank fusion).
doc: optional filter; a document id searches all its versions, a version id only that version.

Input parameters:

- `doc`
- `k` (integer)
- `max_tokens` (integer)
- `mode` (string)
- `query` (string, required)

### `search_claims` (~149 tokens)

Search normative statements extracted from the documents (sentence-level evidence).

topic: words describing what the statement is about ('annual leave carry over', 'text line length').
subject: who it applies to ('employees', 'clients', 'authorization server').
modality: MUST, MUST NOT, SHOULD, SHOULD NOT, MAY (synonyms like SHALL / REQUIRED / must not accepted).
claim_type: requirement | exclusion | numeric. Numeric claims include value and unit (e.g. 1000 octet).

Input parameters:

- `claim_type`
- `doc`
- `k` (integer)
- `max_tokens` (integer)
- `modality`
- `subject`
- `topic`

### `resolve_reference` (~109 tokens)

Follow cross-references to their target section, with a preview of the target text.

Either span_id (resolve every reference inside that span) or reference text such as
'Section 3.4 of [RFC5322]' together with doc (the document the reference appears in).
status: resolved (target stored), external (outside the store) or unresolved (target section missing).

Input parameters:

- `doc`
- `max_tokens` (integer)
- `reference`
- `span_id`

### `lookup_definition` (~58 tokens)

Find where a term is defined ('resource owner', 'eligible employee', 'mailbox'), with the defining text.

Input parameters:

- `doc`
- `k` (integer)
- `max_tokens` (integer)
- `term` (string, required)

### `get_evidence` (~60 tokens)

Full text of one span with its provenance (byte range, SHA-256, parser version), section path,
whether its version is the latest, and a live hash verification result.

Input parameters:

- `span_id` (integer, required)
- `verify` (boolean)

### `verify_span` (~58 tokens)

Re-hash a span against the stored source text. verified=false means the evidence was altered
and must not be cited. deep=true also re-parses the original file.

Input parameters:

- `deep` (boolean)
- `span_id` (integer, required)

### `assemble_context` (~87 tokens)

Build the final evidence pack for an answer. For each span: verify its SHA-256 (rejecting tampered
spans), attach the latest version's text if the span is obsolete, append conflicting claims, then pack
everything into token_budget (requested > newer version > conflicts). Cite the returned citations.

Input parameters:

- `span_ids` (array, required)
- `token_budget` (integer)

### `list_versions` (~53 tokens)

All versions of a document (oldest→newest, append-only) with hashes, parser version, origin and
declared relations such as 'obsoletes RFC 2821'.

Input parameters:

- `doc` (string, required)

### `diff_versions` (~105 tokens)

Compare two versions of a document. Defaults: latest vs the version before it.

level: 'section' (added/removed/modified/renumbered sections with changed sentences),
'claim' (requirements whose modality or value changed, added or removed), or
'reference' (citations added/removed).

Input parameters:

- `doc` (string, required)
- `from_version`
- `level` (string)
- `max_tokens` (integer)
- `to_version`

### `blame` (~64 tokens)

Which version first introduced a passage, and its status (identical/similar/absent) in every version.
Give span_id, or text + doc to locate the passage in the latest version.

Input parameters:

- `doc`
- `span_id`
- `text`

### `find_affected_documents` (~61 tokens)

Documents that reference this document (cite, update or obsolete it). Use it to see what may need
review when the document changes; flags sources that still cite an obsolete version.

Input parameters:

- `doc` (string, required)
- `max_tokens` (integer)

### `find_contradictions` (~123 tokens)

Statements from different documents that conflict (different values for the same limit, or opposing
MUST/MUST NOT/MAY requirements). Both sides are returned as evidence; nothing is auto-resolved.

status: confirmed (rule + LLM judge agree), candidate (rule only) or rejected (judge disagreed, hidden by default).
include_history: also include pairs involving obsolete versions.

Input parameters:

- `doc`
- `include_history` (boolean)
- `include_rejected` (boolean)
- `k` (integer)
- `max_tokens` (integer)

### `add_document` (~155 tokens)

Add a local file or folder (.pdf, .docx, .html, .md, .txt) to DocuSense.

Re-adding a file whose content changed appends a new version (v1, v2, …); unchanged files are skipped,
so it is safe to call repeatedly. doc / label set the document id / version label (single file only).
Ingestion runs in the background: if it is not finished within wait_seconds the result has
status 'running' and a job_id; call ingest_status(job_id) until it is 'done'.

Input parameters:

- `doc`
- `label`
- `path` (string, required)
- `title`
- `wait_seconds` (number)

### `ingest_status` (~35 tokens)

Status of a background add_document job (or the 10 most recent jobs when job_id is omitted).

Input parameters:

- `job_id`

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/hksharma2004-docusense/docusense-mcp#diagnostics

## Score history

- 2026-11-21: 66
- 2026-11-20: 80
- 2026-11-19: 74
- 2026-11-18: 58
- 2026-11-17: 58
- 2026-11-16: 58

## Common questions

### What is the DocuSense MCP server?

DocuSense is an MCP server listed in the public MCP registry as io.github.hksharma2004/docusense. Agents read PDFs and docs by section and claim: ~20x fewer tokens, hash-verified citations, diffs. This page covers its PyPI package (docusense-mcp).

### Is the DocuSense MCP server safe to use?

DocuSense scores 66 out of 100 on VerifyMCP. 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 DocuSense MCP server expose?

DocuSense exposes 17 tools: list_documents, get_section_map, read_section, search, search_claims, and 12 more. Their descriptions and schemas cost roughly 1,463 tokens of context every time the server is loaded.

### Is the DocuSense MCP server still maintained?

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

DocuSense 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 DocuSense MCP server?

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

## Links

- PyPI project: https://pypi.org/project/docusense-mcp/
- Socket report: https://socket.dev/pypi/package/docusense-mcp
- Repository: https://github.com/hksharma2004/docu-sense
- Website: https://docusense.xyz/
- Changelog RSS feed: https://verifymcp.io/servers/hksharma2004-docusense/docusense-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/hksharma2004-docusense/docusense-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/hksharma2004-docusense/docusense-mcp.json
- HTML version of this page: https://verifymcp.io/servers/hksharma2004-docusense/docusense-mcp
