blue·auth Document Signing

io.github.ricdanyalgilPublished by GitHub account ricdanyalgilv1.0.0Updated Oct 24, 2026

Send AI-created PDFs for signature, track signers, and return verifiable document evidence.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

A remote MCP server that lets an assistant send AI-created PDFs for signature, track signers, and return verifiable document evidence.

What you can do
Send AI-created PDFs out for signature through blue·auth document signing workflows. Track the status of signers on documents that have been sent. Return verifiable evidence for signed documents. The manifest lists no individual tools, so exact operations are not documented here.
When to use it
Useful when an assistant drafts or produces a PDF that needs a real signature from one or more people, and you want to follow signing progress and keep verifiable proof of the result without leaving the conversation.
Requirements
A remote MCP endpoint at blueauth.co reached over streamable HTTP. OAuth authentication is required, so a blue·auth account and an OAuth sign-in are needed. No environment variables or headers are declared.
Before you install
Sending a document for signature shares its contents with blue·auth and the recipients, so avoid confidential material you would not send externally. Signing requests go to real people and may create legally meaningful records. OAuth grants the server access to your blue·auth account; review the scopes before authorizing.

Installation

In SourceWeft

  1. Open blue·auth Document Signing 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/io.github.ricdanyalgil%2Fblueauth-document-signing/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": {
    "blue-auth-document-signing": {
      "type": "http",
      "url": "https://blueauth.co/api/mcp-server/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.