deckproof-mcp
Related Servers
Alternatives to deckproof-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables creating, editing, and reading PowerPoint presentations (PPTX) with security features like ZIP bomb protection, macro detection, and path traversal prevention.-
- AlicenseAqualityAmaintenanceEnables creating and editing PowerPoint .pptx files without corruption, with native editable SVG shapes, glued connectors, table surgery, threaded comments, live editing, and a comprehensive 138-tool MCP server surface.25232 PyPIAGPL 3.0
- FlicenseNot gradedqualityDmaintenanceEnables processing PowerPoint and Word documents, extracting content and structure, combining them, and generating new presentations.1-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to programmatically create, manipulate, and analyze Microsoft PowerPoint presentations with advanced formatting and template management.5MIT
- AlicenseNot gradedqualityFmaintenanceA server that enables creating and editing PowerPoint presentations programmatically through the Model Context Protocol, supporting features like adding slides, images, textboxes, charts, and tables.8,041 PyPI1,856MIT
- AlicenseNot gradedqualityCmaintenanceEnables users to create, edit, and manage PowerPoint presentations, including slides, text, images, tables, charts, templates, and professional design effects.MIT
TDQS
Scored across 5 tools
Each tool addresses a distinct phase: layout discovery, deck creation, structural validation, audit reporting, and repair. The overlap between validate and audit is acceptable because validate gives a pass/fail health check while audit adds detailed metrics and portability risk.
All tools share the consistent `pptx_` prefix and use clear snake_case verbs: list_layouts, create_deck, validate, audit, repair. The pattern is predictable and makes tool purpose immediately recognizable.
Five tools is well-scoped for a deck-focused reliability server: one for discovering layouts, one for creation, and three for validation/audit/repair. Each tool has a distinct role without unnecessary bloat or missing essentials.
The tool surface covers the full intended workflow: understand available layouts, create a deck, verify it, inspect it in depth, and repair structural issues. The self-certifying creation step also closes the loop by ensuring newly created decks are valid before they are returned.