Nutrient DWSSAFE
A Model Context Protocol (MCP) server implementation that integrates with the Nutrient Document Web Service (DWS) Processor API, providing powerful PDF processing capabilities for AI assistants.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
[](https://www.npmjs.com/package/@nutrient-sdk/dws-mcp-server) [](https://smithery.ai/servers/nutrient/dws-mcp-server)
Give AI agents the power to generate, read, extract, process, and sign documents.
Description
A Model Context Protocol (MCP) server that connects AI assistants to the Nutrient Document Web Service (DWS) Processor and Data Extraction APIs — enabling document creation, editing, conversion, digital signing, OCR, and redaction, plus structured data extraction (typed JSON with bounding boxes and confidence, or schema-guided field extraction with per-field citations) through natural language.
Features
- Local stdio MCP server for Claude Desktop and other MCP-compatible clients
- Browser-based OAuth on the first request that uses the Nutrient API, with optional API-key fallback for CI and headless environments
- Document conversion, OCR, redaction, watermarking, annotation flattening, and digital signing (Processor API)
- Data extraction (Data Extraction API): parse whole documents to Markdown or spatial JSON, then pull named fields into a JSON schema you define, with per-field citations. Four parse modes:
text(1 credit/page, no OCR),structure(1.5),understand(9, the default),agentic(18, VLM) - Sandbox-aware local file handling with explicit output paths
- Read-only account lookup for DWS credits and usage
What You Can Do
Once configured, you (or your AI agent) can process
130c5e474871OBSERVED · 2026-10-07Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add dws-mcp-server --env NUTRIENT_DWS_API_KEY=${NUTRIENT_DWS_API_KEY} --env NUTRIENT_DWS_EXTRACTION_API_KEY=${NUTRIENT_DWS_EXTRACTION_API_KEY} -- npx -y @nutrient-sdk/[email protected]Exposed tools (20)
19 read · 1 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
ai_redactor | read | |
check_credits | read | Check your Nutrient DWS API credit balance and usage for the current billing period. This is a read-only account lookup. It does not upload any document content. Returns: subscription type, total credits, used credits, and remaining credits. |
directory_tree | read | Browse local files when sandbox mode is disabled. This is a read-only local filesystem operation, but it can inspect any path visible to the current user. Sandbox mode is strongly recommended. |
document_processor | read | |
document_signer | read | |
entity_types | read | Optional sensitive entity types to redact; omit to use the tool default. |
example | read | Example tool |
extract_document_fields | read | Extract named fields from a document into a JSON object, optionally retaining citations in a file. |
extract_fields | read | |
fields | read | Comma-separated field names to extract. |
input_path | read | Path to the document to watermark and sign. |
office_to_pdfa | read | Convert an Office document to an archival PDF/A file. |
output_path | read | Path for the final signed PDF. |
parse_document | read | |
parse_for_rag | read | Parse a document as Markdown for retrieval-augmented generation and search indexing. |
path | read | Input path |
redact_pii | read | Detect and permanently redact personally identifiable information from a document. |
sandbox_file_tree | read | Browse files already available in the configured sandbox directory. This is a read-only local filesystem operation and does not upload documents to Nutrient. |
sign_and_watermark | write | Add a text watermark to a document, then digitally sign the watermarked PDF. |
watermark_text | read | Text to place in the watermark. |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- declared (5 observation(s))
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (10)
example.docx
example.pptx
example.xlsx
.prettierignore
.prettierrc.json
resolve({ server, url: `http://127.0.0.1:${port}` })baseUrl: `http://127.0.0.1:${addr.port}`,resolve({ server, url: `http://127.0.0.1:${port}` })@modelcontextprotocol/sdk, axios, form-data, open, winston, zod, @eslint/js, @types/node
For example, load the macOS CLI credential without printing it:
Gates applied: no_behavioural_pass.
130c5e474871full audit observations/trust-audit/mcp-server/pspdfkit__nutrient-dws.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-07 | 130c5e474871 | SAFE | B | 89 | first audit |
Questions
What is the Nutrient DWS MCP server?
A Model Context Protocol (MCP) server implementation that integrates with the Nutrient Document Web Service (DWS) Processor API, providing powerful PDF processing capabilities for AI assistants.
What tools does Nutrient DWS expose?
20 in total: 19 read-only, 1 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is Nutrient DWS safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does Nutrient DWS need?
It reads NUTRIENT_DWS_API_KEY and NUTRIENT_DWS_EXTRACTION_API_KEY from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does Nutrient DWS run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as @nutrient-sdk/dws-mcp-server at 0.1.3.
How current is this page?
The grade is for one exact copy of the source (130c5e474871), read on 2026-10-07. The repository is watched and re-audited when it changes.