Signvoy

com.signvoyPublished by signvoy.comOfficial publisherv1.0.0Updated Oct 24, 2026

Send documents for e-signature, track signing status, and download signed PDFs. No API key required.

Overview

AI-generated overview

Lets an assistant send documents for e-signature, track signing status, and download signed PDFs through a remote endpoint.

What you can do
Signvoy is a remote MCP server for e-signature workflows. According to its registry description, it lets an assistant send documents out for signature, check the signing status of those documents, and download the resulting signed PDFs. No tool list is published in the manifest, so the exact tool names and parameters are not documented here.
When to use it
Worth considering when an assistant needs to hand a document to someone for signature and later confirm whether it was signed, or retrieve the signed copy. It fits contract, approval, and form-signing flows rather than general document editing.
Requirements
It runs as a remote streamable HTTP endpoint at api.signvoy.com, so no local runtime or package installation is needed. The manifest declares no authentication, no environment variables, and no headers, and the description states no API key is required. Network access to the endpoint is required.
Before you install
The server sends documents to a third-party signing service, so document contents leave the user's machine. It can send documents out for signature and download signed files, which are actions with legal and privacy consequences. The manifest declares no authentication, so anyone able to reach the endpoint may be able to act through it; verify how the service identifies and authorizes the caller before relying on it.

Installation

In SourceWeft

  1. Open Signvoy in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.signvoy%2Fsignvoy/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "signvoy": {
      "type": "http",
      "url": "https://api.signvoy.com/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.