Groupdocs Signature MCP runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 3 Sep 2026.
MCP server for GroupDocs.Signature — sign, search and verify document signatures via AI agents.
We read the source, 22 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
# Native graphics deps GroupDocs.Signature needs on Linux. The engine rasterizes # signature glyphs (text, QR codes, barcodes, certificate annotations) onto # document pages via System.Drawing.Common — that path P/Invokes libgdiplus # (the GDI+ implementation) and uses libfont…
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
MCP server for GroupDocs.Watermark — add and search document watermarks via AI agents.
MCP server for GroupDocs.Merger — merge, split, and inspect documents via AI agents.
MCP server for GroupDocs.Markdown — convert documents to Markdown via AI agents.
MCP server for GroupDocs.Comparison — compare, analyze, and inspect documents via AI agents.
MCP server for GroupDocs.Annotation — add, list, update, remove document annotations via AI agents.
MCP server for GroupDocs.Metadata — read, search, write, and remove document metadata.
MCP server for LayerOne DocX (documents & Factur-X) and Sign (e-signature) APIs.
MCP server for GroupDocs.Total — annotate, sign, convert, watermark, parse, redact documents via AI.
Answers built from our own checks of this server.