Etchv MCP Server
OfficialRelated Servers
Alternatives to Etchv MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to add text and image watermarks, search for existing watermarks, and remove watermarks from documents. Supports over 50 document and image formats including PDF, DOCX, and XLSX.MIT
- AlicenseNot gradedqualityBmaintenanceProvides AI content watermarking and C2PA compliance for EU AI Act Article 50, enabling detection, verification, and batch processing of authenticated content.4MIT
- AlicenseAqualityBmaintenanceVerifiable document intelligence for AI agents. Extract text, tables, and structured data from PDFs and URLs. Summarize, answer questions, check claims, and translate — all with cited evidence. Store tamper-evident evidence bundles with cryptographic signatures and on-chain attestation via Base L2. Cross-document semantic search and Q&A across named collections. Pay per call with USDC22101MIT

AltText.ai MCP Serverofficial
AlicenseAqualityBmaintenanceEnables AI assistants to generate alt text, manage image libraries, and audit web pages for accessibility using the AltText.ai API.1215MIT
pdf4me-mcpofficial
AlicenseBqualityBmaintenanceEnables AI assistants to perform a wide range of PDF processing tasks, including conversion, editing, merging, splitting, OCR, barcode/QR code generation and reading, AI-powered data extraction, and image processing, through the PDF4me API.92MIT- AlicenseAqualityCmaintenanceEnables AI assistants to manage document signing workflows via natural language, including creating envelopes, uploading documents, analyzing contracts, and verifying blockchain anchors.8501MIT
TDQS
Scored across 18 tools
Most tools target a distinct resource+action pair, and descriptions clarify the job-based flow (watermark/detect → get_job → get_job_result). The only mild overlaps are get_job vs get_job_result and the storage delivery list/get pair, but the descriptions make the boundaries readable.
Every tool follows a predictable snake_case verb_noun pattern (list_assets, get_asset, download_asset, update_asset, delete_asset, store_asset, redeliver_webhook, etc.). No camelCase or vague verbs break the pattern.
18 tools is slightly heavy but justified: four distinct areas (watermarking jobs, assets, storage destinations/deliveries, webhooks) each need CRUD-ish coverage. Nothing feels gratuitous, though a couple of read tools could conceivably be folded together.
Assets cover read/download/update/delete but there is no create/upload operation, and webhooks expose list/redeliver/deliveries but no create or delete (explicitly deferred to the dashboard). These are deliberate gaps but leave agents unable to complete full lifecycle workflows without leaving the tool surface.