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.
npx agentmods add mcp/drbaher/sign-cli/claude-desktop-sign-cligit clone --depth 1 https://github.com/DrBaher/sign-cliWrote 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/drbaher/sign-cli/claude-desktop-sign-cli)<a href="https://agentmods.dev/mcp/drbaher/sign-cli/claude-desktop-sign-cli"><img src="https://agentmods.dev/badge/mcp/drbaher/sign-cli/claude-desktop-sign-cli.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
sign-cli 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 4d 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
{
"sign-cli": {
"command": "node",
"args": [
"/absolute/path/to/sign-cli/dist/cli.js",
"mcp",
"serve",
"--read-only",
"true",
"--capability",
"tools",
"--tool",
"signer_list",
"--tool",
"signer_fetch_document",
"--tool",
"request_show",
"--tool",
"request_status",
"--tool",
"audit_verify",
"--tool",
"request_watch",
"--emit-events",
"/absolute/path/to/sign-cli-logs/mcp.ndjson",
"--emit-events-redact",
"true"
],
"env": {
"SIGN_DB_PATH": "/absolute/path/to/sign-cli/data/sign.db"
}
}
}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.
- 4d ago First seen · 33 lines scan A 794f3ad06b8e
sign-cli is an MCP server published in the GitHub repository DrBaher/sign-cli (0 stars, last pushed 1mo 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
document-integrity-validator-mcp
AI reasoning checks any document against known international standards before your agent acts on it. Runs locally from the document-integrity-validator-mcp npm package. Needs 1 environment variable to run.
mcp
SwiftSign MCP server for Claude Code — send documents for e-signature. Runs locally from the swiftsign-mcp npm package. Needs 1 environment variable to run.
mcp
E-signatures for agents: mint a sandbox key, send PDFs, track status, download the sealed result. Remote server at swiftsign.ca.
fedramp-docs
MCP server "fedramp-docs" as configured in hackIDLE/fedramp-docs-mcp. Launched with fedramp-docs-mcp. Needs 1 environment variable to run.
open-agreements
Fill standard legal agreement templates (NDAs, SAFEs, NVCA docs, employment) as DOCX files. Runs locally from the @open-agreements/contract-templates-mcp npm package.
attestix
Attestix - Attestation Infrastructure for AI Agents. DID-based agent identity, W3C Verifiable Credentials, EU AI Act compliance, delegation chains, and reputation scoring. 47 MCP tools across 9 modules. Runs locally from the attestix Python package.