signnow-mcp-server

MCP server package intended to expose SignNow (eSignature) capabilities to AI agents via the Model Context Protocol, enabling programmatic signing/document workflows through agent tool calls.

Evaluated Apr 04, 2026 (27d ago)
Homepage ↗ Communication mcp e-signature automation agents
⚙ Agent Friendliness
32
/ 100
Can an agent use this?
🔒 Security
42
/ 100
Is it safe for agents?
⚡ Reliability
25
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
45
Documentation
30
Error Messages
0
Auth Simplicity
45
Rate Limits
10

🔒 Security

TLS Enforcement
60
Auth Strength
40
Scope Granularity
30
Dep. Hygiene
40
Secret Handling
40

Specific security implementation details (TLS requirements, auth mechanism, secret handling, and dependency status) were not provided in the supplied content, so scores reflect uncertainty. As a wrapper around an eSignature provider, it should be treated as sensitive and reviewed for secure credential storage and non-leaky logging.

⚡ Reliability

Uptime/SLA
0
Version Stability
40
Breaking Changes
30
Error Recovery
30
AF Security Reliability

Best When

You want an AI agent to orchestrate SignNow operations (create/manage signing flows) from within an MCP-compatible agent runtime.

Avoid When

You need guaranteed idempotency, fine-grained pagination/streaming semantics, or you cannot obtain/secure required API credentials for SignNow.

Use Cases

  • Agent-driven creation of signing requests
  • Automating eSignature flows in support/ops workflows
  • Generating and routing documents for signature via an agent

Not For

  • Direct interactive human document signing UX
  • Use cases requiring custom UI/approval flows beyond what the MCP tool set supports
  • Workflows that demand strong guarantees about idempotent, transactional document state unless explicitly documented

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

OAuth: No Scopes: No

Authentication details are not provided in the supplied information. MCP servers that wrap third-party APIs typically require API keys or OAuth credentials, but this cannot be confirmed here.

Pricing

Free tier: No
Requires CC: No

No pricing information was provided for this specific MCP package. Pricing is likely determined by the underlying SignNow account plan and API usage.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • MCP toolsets may not expose explicit idempotency keys; repeated agent retries could create duplicate signing requests unless tool implementation prevents it.
  • If credential setup is unclear, agents may fail tool calls without actionable error guidance.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for signnow-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered