0
/ 100
5 days ago
npm
mcp-server-zapsign
MCP Server for ZapSign API Integration - Complete electronic signature solution
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.
Install from
M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.
// key findings
🚨
Code appears obfuscated
2 files are unreadable to a human reviewer. Cannot audit what they do.
⚠️
Known vulnerabilities in dependencies: 10 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 1 credential: ZAPSIGN_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// required environment variables
This server reads these from
process.env. You'll be asked to provide them before it can run.config
ENABLE_METRICSconfig
ENABLE_RATE_LIMITING— Enable rate limiting true Noconfig
HOST— Server host localhost Noconfig
LOG_LEVEL— Logging level info Noconfig
MAX_REQUESTS_PER_MINUTEconfig
PORT— Server port 3001 Noconfig
SERVER_NAME— mcp-server-zapsignconfig
SERVER_VERSION🔐 secret
ZAPSIGN_API_KEY— your_zapsign_api_key_hereconfig
ZAPSIGN_API_VERSIONconfig
ZAPSIGN_BASE_URL— ZapSign API base URL https://api.zapsign.com.br No// full audit trail
The full breakdown of what we checked, the deductions that landed, the network hosts, the dependency advisories, and concrete fix guidance is available to verified publishers.
// improvement guidance — verified publishers only
We have 2 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
[](https://m8ven.ai/mcp/mcp-server-zapsign-1s2jnc)commit: 27e384dcde496b4dbcc5649e95cee8dda81f6638
code hash: 2b66b200bab115c1127c64e3457e9e2d363610c2cd7ea125b26d8ad693722917
verified: 5/29/2026, 12:01:16 PM