Skip to main content
Glama
GOLayerone

layerone-mcp

Official
by GOLayerone
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to layerone-mcp

No user-submitted related servers found.

    Related Servers

    • docforge-mcp

      filhocf
      A
      license
      B
      quality
      C
      maintenance
      Enables complete Office document lifecycle management for AI agents, including creation, editing, conversion, and templating of DOCX, XLSX, PPTX, PDF, and EML files.
      40
      65 PyPI
      MIT
    • Formify MCP by formify-e-sign

      Formify MCPofficial

      formify-e-sign
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to create fillable PDFs, send contracts for e-signature, verify signers via BankID or ID scans, and track post-send document workflows.
      5
      MIT

    • online.econtract/mcp

      contractlayer
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents and developers to create, send, and follow up on contracts for e-signature, manage signers and templates, retrieve signed PDFs and audit trails, and verify PDF signatures. It keeps signing and declining in the hands of each signer through personal links.
      1
      MIT

    • Sign Harness MCP Server

      reina20xx
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to create e-signature contracts, issue signing URLs, check pending signature statuses, and verify document SHA-256 hashes and signature seals through natural language.
      MIT
    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

    A3.8/5.0

    Scored across 20 tools

    Disambiguation5/5

    The tools are cleanly divided into two domains (docx_ and sign_), each with distinct actions. Within each domain, every tool targets a specific resource or operation with no overlap.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with lowercase and underscores, using clear prefixes (docx_, sign_) to indicate the domain. No mixing of conventions.

    Tool Count5/5

    20 tools is well-scoped for a service combining document template management and electronic signature workflows. Each tool has a clear purpose, and the count is reasonable for the functionality offered.

    Completeness4/5

    The tool set covers the core workflows for template operations and signature lifecycle. A minor gap is the lack of a tool to list all sent signature requests, but the essential CRUD and rendering/signing steps are present.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources