sign-cli (DrBaher/sign-cli) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 20 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
1 month ago

sign-cli

Agent-first e-signature CLI: a 19-tool MCP server with offline PAdES signing (real PKCS#7) and a hash-chained audit log with RFC 3161 timestamping. Per-signer approval tokens keep humans in the loop while agents drive every other step. Stdio + HTTP transports.

→ DrBaher/sign-cli· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

DrBaher

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 7 credentials: DOCUSIGN_INTEGRATION_KEY, DOCUSIGN_WEBHOOK_SECRET, DROPBOX_SIGN_API_KEY, SIGNWELL_API_KEY, SIGNWELL_WEBHOOK_SECRET, SIGN_HTTP_AUTH_TOKEN, SIGN_MCP_HTTP_AUTH_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

lowesbuild@0.28.0GHSA-g7r4-m6w7-qqqr

esbuild allows arbitrary file read when running the development server on Windows

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configDOCUSIGN_ACCOUNT_ID
configDOCUSIGN_BASE_PATH
🔐 secretDOCUSIGN_INTEGRATION_KEY
configDOCUSIGN_PRIVATE_KEY_PATH
configDOCUSIGN_USER_ID
🔐 secretDOCUSIGN_WEBHOOK_SECRET
🔐 secretDROPBOX_SIGN_API_KEY
configDROPBOX_SIGN_CLIENT_ID
configDROPBOX_SIGN_TEST_MODE
🔐 secretSIGNWELL_API_KEYsign profile set --name prod --key credentials. --value "{{env:SIGNWELL_API_KEY}}"
configSIGNWELL_BASE_URL
configSIGNWELL_SMOKE_SIGNER_EMAIL
configSIGNWELL_TEST_MODE
🔐 secretSIGNWELL_WEBHOOK_SECRET
configSIGN_ALLOW_ABSOLUTE_DOCS
configSIGN_DB_BACKEND
configSIGN_DB_PATH
configSIGN_DEBUG
configSIGN_ERROR_FORMAT
🔐 secretSIGN_HTTP_AUTH_TOKEN
configSIGN_HTTP_BASE_DELAY_MS
configSIGN_HTTP_MAX_RETRIES
configSIGN_LOCAL_AUTOCOMPLETEFor --provider local, an agent can act as a signer end-to-end without an email link. Set =false so the local provider holds at sent until each signer explicitly runs sign sign.
configSIGN_LOCAL_COMPLETE_AFTER
configSIGN_LOCAL_KEY_DIR
configSIGN_LOCAL_MAX_FETCHES_PER_HOUR
configSIGN_LOCAL_NOTIFY_URL
configSIGN_LOCAL_STORE_DIR
configSIGN_LOG_FORMAT
configSIGN_MAX_DOCUMENT_BYTES
🔐 secretSIGN_MCP_HTTP_AUTH_TOKEN
configSIGN_PG_URL
configSIGN_PROFILE
configSIGN_PROFILES_FILE
configSIGN_PROVIDER
configSIGN_SHOW_WARNINGS
configSIGN_STRICT_PROVIDER
configSIGN_TSA_URL
configSIGN_VERIFICATION_WEBHOOK_URL
configXDG_CONFIG_HOME
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

20/20 tools missing one or more hints — signer_list (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); signer_fetch_document (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); sign (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +17 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

6/20 tools referenced in tests (30%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

30 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Secrets not written to files

5 secret values written to files

Avoid persisting secrets to disk. Keep them in memory or your secret manager.

Secrets not logged

51 secret values sent to console.log

Redact or omit secret values from log output.

No arbitrary install scripts

Has postinstall/preinstall script — runs arbitrary code on npm install

Remove postinstall/preinstall hooks unless they’re essential.

Dependency freshness

1/7 production deps stale: pdf-lib@2022-05-12 (4.2y)

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 7 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/drbaher/sign-cli)](https://m8ven.ai/mcp/drbaher/sign-cli)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: df6fe27f0a3c56ba63585b30cf8e5062e03942d4
code hash: 5d5a7b1ac4fb5551f04c81f91de73c0a8904d865eba7f08bde67b31737070d50
verified: 8/6/2026, 2:57:38 PM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client