Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/kumarprobeops/signforge-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/kumarprobeops/signforge-mcp/signforge)<a href="https://agentmods.dev/mcp/kumarprobeops/signforge-mcp/signforge"><img src="https://agentmods.dev/badge/mcp/kumarprobeops/signforge-mcp/signforge/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/kumarprobeops/signforge-mcp/signforge"><img src="https://agentmods.dev/badge/mcp/kumarprobeops/signforge-mcp/signforge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
signforge scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "signforge": { "command": "npx", "args": [ "-y", "@signforge/mcp-server" ], "env": { "SIGNFORGE_API_KEY": "", "SIGNFORGE_API_URL": "" } } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 13 lines scan A 5b6a5f530776
signforge is an MCP server published in the GitHub repository kumarprobeops/signforge-mcp (0 stars, last pushed 6mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
groupdocs-signature-mcp
MCP server "groupdocs-signature-mcp" as configured in groupdocs-signature/GroupDocs.Signature.Mcp. Launched with GroupDocs.Signature.Mcp. Needs 5 environment variables to run.
pdf-content-search
MCP server "pdf-content-search" as configured in juergenkoller-software/pdf-content-search-mcp. Launched with /usr/local/bin/pdf-content-search-mcp. Needs 2 environment variables to run.
rendoc-mcp-server
Generate professional PDFs (invoices, contracts, reports) from AI tools via rendoc templates. Runs locally from the @rendoc/mcp-server npm package. Needs 1 environment variable to run.
mcp
MCP server for Signbee — document signing for AI agents. Runs locally from the signbee-mcp npm package. Needs 1 environment variable to run.
dottedsign-mcp
Automate eSignature workflows and signing tasks via natural language commands. Remote server at mcp.dottedsign.com.
addsign-mcp
MCP server for AddSign — agents send documents for signature, track signing status, and download signed PDFs. Runs locally from the addsign-mcp npm package. Needs 1 environment variable to run.