Skip to main content
Glama
esign-cn-open-source

e签宝 MCP Server

Official
by esign-cn-open-source
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to e签宝 MCP Server

No user-submitted related servers found.

    Related Servers

    • AnyDoc

      xianhong1208
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables document conversion and processing through MCP, including Office/PDF/Markdown conversions, OCR, and PDF operations like split, rotate, encrypt, and extract.
      MIT

    • paraph-mcp

      servants-of-the-server-fire
      A
      license
      A
      quality
      C
      maintenance
      MCP server for the Paraph e-signature API that enables AI tools to fill PDF forms and manage electronic signing workflows. It provides tools for template management, document filling, sending signing requests, and tracking signing progress.
      7
      5 npm
      MIT

    • Aoexl Sign

      aryansingh0203
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables users to create, manage, and track electronic signing requests and templates through Claude Desktop and other MCP-compatible clients. Provides multi-tenant authentication with customer API keys for secure document workflow operations.
      66 npm
      -
    • Aspose.PDF Cloud MCP Server by aspose-cloud

      Aspose.PDF Cloud MCP Serverofficial

      aspose-cloud
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables PDF conversion to DOC, merging multiple PDFs, reading document properties, and bundled storage file operations for complete upload-process-download workflows through MCP.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: create_sign_flow initiates a signing process, while query_sign_flow retrieves details about an existing one. There is no overlap in functionality, making it easy for an agent to choose the correct tool based on the task.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern with snake_case: create_sign_flow and query_sign_flow. The naming is predictable and aligns well with their respective actions, ensuring clarity and uniformity.

    Tool Count2/5

    With only two tools, the server feels under-scoped for an e-signature domain, which typically requires operations like updating flows, canceling, downloading documents, or managing templates. This limited set may hinder agents from completing common workflows.

    Completeness2/5

    The tool surface is severely incomplete for e-signature functionality. It lacks essential operations such as updating or canceling flows, downloading signed documents, and managing templates or signers. Agents will face significant gaps in handling full signing lifecycles.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources