redact-pdf-mcp
Related Servers
Alternatives to redact-pdf-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to redact PII from text, summarize redacted content, and manage custom redaction patterns across multiple languages.-

@actalumen/mcp-serverofficial
FlicenseAqualityCmaintenanceEnables AI agents to upload, verify, and chat about documents for compliance (e.g., SOC2, GDPR) with PII redacted server-side.88 npm-- AlicenseNot gradedqualityBmaintenanceEnables AI agents and users to process documents through natural language, supporting PDF operations like text extraction, redaction, splitting, form filling, annotations, and content search.42 npm62MIT
- FlicenseAqualityCmaintenanceDetects and redacts sensitive personal information such as names, emails, phone numbers, ID numbers, and locations in text before it is processed by AI agents, using configurable mask, hash, or remove strategies.1-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to perform comprehensive PDF operations locally, including compression, text extraction, PII redaction, page organization, splitting, merging, watermarking, creation, and form filling, all without cloud uploads.11 npm-
- FlicenseNot gradedqualityFmaintenanceRedacts PII from LLM traces and tool payloads before they leave review, enabling PII scanning, payload redaction, sensitive field classification, privacy receipts, and trace audit exports.-
TDQS
Scored across 6 tools
Most tools have clearly distinct purposes: account status, demo, sync redaction, async redaction, status polling, and download. The only real overlap is between redact_pdf_and_wait and redact_pdf, but the descriptions strongly differentiate them by blocking vs. asynchronous behavior.
Tool names generally follow a verb_noun snake_case pattern (get_account_status, get_job_status, download_redacted). The exceptions are redact_pdf_and_wait, which uses a phrase suffix, and try_demo, which is vaguer than the rest, but the overall convention is consistent.
Six tools is well-scoped for the service: authentication status, demo, synchronous redaction, asynchronous redaction, job status, and result download. Each tool earns its place and there is no obvious redundancy or bloat.
The tool set covers the full workflow: check credentials, try without a key, submit redaction synchronously or asynchronously, poll progress, and download the finished file. There are no dead ends for the core use case, and both fast and batched workflows are supported.