SmoothSign

cc.smoothsignPublished by smoothsign.ccOfficial publisherv1.0.0Updated Oct 26, 2026

Send PDFs for e-signature by email and SMS code. Check signing status. No document storage.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that lets an assistant send PDFs for e-signature by email and SMS code and check signing status, without storing documents.

What you can do
  • Send a PDF out for e-signature, delivered by email and SMS verification code
  • Check the signing status of documents already sent
  • No document storage: files are not kept by the service
When to use it
Useful when you want an assistant to hand a PDF to a signer and later confirm whether it has been signed, without leaving the chat. Suited to light signing workflows rather than document management.
Requirements
A remote MCP endpoint at smoothsign.cc over streamable HTTP, with OAuth sign-in required. No environment variables or headers are declared; a SmoothSign account is implied by the OAuth requirement.
Before you install
Sending a PDF dispatches it to a third-party service and to the recipient's email and phone, so check the document and recipient before sending. Signing requests may involve costs or account terms not described here. The service states it does not store documents, so keep your own copies.

Installation

In SourceWeft

  1. Open SmoothSign 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/cc.smoothsign%2Fsmoothsign/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": {
    "smoothsign": {
      "type": "http",
      "url": "https://smoothsign.cc/mcp"
    }
  }
}

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.0LatestOct 18, 2026

Score

67% 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.