Fairsign

io.github.zhouhua188199-archPublished by GitHub account zhouhua188199-archv1.0.1Updated Oct 24, 2026

Fill and sign PDFs in the browser, send for signature, and track who has signed.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowFiles & Storage

Overview

AI-generated overview

Fairsign is a remote MCP server that lets an assistant fill and sign PDFs in the browser, send documents for signature, and track signing status.

What you can do
Fill in PDF forms and apply signatures in the browser through the assistant's connection to the hosted service. Send prepared documents out for signature. Track who has signed and the status of each request.
When to use it
Useful when a workflow involves preparing PDF forms, getting documents signed by others, and following up on signature status without leaving the assistant.
Requirements
A remote MCP endpoint at the Fairsign hosted service; no local package, environment variables, or headers are declared. The manifest declares no authentication, so check the provider's site for any account or sign-in requirements before relying on it.
Before you install
The server sends documents and signature requests to a third-party hosted service, so consider the sensitivity of the PDFs involved. It can send documents to other people and change signing status, so review actions before they are carried out. No authentication is declared in the manifest; verify how access to your documents is protected.

Installation

In SourceWeft

  1. Open Fairsign in the dashboard and add it to a workspace.
  2. 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/io.github.zhouhua188199-arch%2Ffairsign/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.

{
  "mcpServers": {
    "fairsign": {
      "type": "http",
      "url": "https://www.usefairsign.com/api/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.1LatestSep 16, 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 listedRequired15 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.