Send documents for signature, track signers, and get verifiable proof of signing.
Connects to blue·auth to send AI-created PDFs for electronic signature, monitor signer status, and retrieve signed documents with verification evidence. Useful for contracts, agreements, and forms that need legal proof of signing.
Try asking Muse: "Send this contract to my client for signature and let me know when they've signed it."
Source: Found in the official MCP Registry (io.github.ricdanyalgil/blueauth-document-signing) · First listed September 25, 2026
Each bar is one check, every 15 minutes. Green means it answered. Last checked 4 h ago.
What Muse can see: You sign in to your own account with it, so Muse can reach what that account allows. Read what it asks for before you agree.
Before it acts: Read what Muse plans to do before you approve it, and remove the app from Muse when you stop using it.
musedirectory.ai is not part of Meta. More about how Muse handles your information
blue·auth Document Signing is not in Muse's Connectors list yet, and it needs you to sign in with your blue·auth Document Signing account. Apps that need this kind of sign-in usually cannot be used from a Muse chat yet. Follow it here and we will tell you when it reaches Muse.
https://blueauth.co/api/mcp-server/mcpNot in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
blue·auth Document Signing is a remote MCP server, so any assistant that can add a custom connector by link can use it. Same link, same tools.
In ChatGPT, open Settings, then Connectors (called Apps & Connectors on some accounts).
Under Advanced settings, switch on Developer mode. That is what lets you add a connector by link.
Choose Create, give it a name, paste the link as the MCP server URL, and save. If it needs a sign-in, ChatGPT asks for it here.
Start a chat, open the tools menu, pick the connector, and ask. ChatGPT asks before it runs a tool the first time.
Custom connectors need a paid ChatGPT plan, and on Team, Enterprise and Edu accounts only an admin can add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in ChatGPT
In Claude, open Settings, then Connectors.
Choose Add custom connector, give it a name, and paste the link.
If it needs a sign-in, Claude sends you to it. Then turn the connector on in a chat from the tools menu and ask.
Custom connectors are available on paid Claude plans; on Team and Enterprise accounts an admin may need to add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in Claude
https://blueauth.co/api/mcp-server/mcpResponse time at the last check: 618ms. Worked in 98.6% of checks over 30 days.
Screened, no issues found
Screening looks for known threats and hidden instructions at the time of the check, and runs again weekly and whenever the tool list changes. It cannot see the server's code, so only connect what you need and review what Muse asks to do. How screening works.
This endpoint requires sign-in before it lists tools, so there is no public tool catalog.
https://blueauth.co/api/mcp-server/mcpblue·auth Document Signing is not in Muse's Connectors list yet, and it needs you to sign in with your blue·auth Document Signing account. Apps that need this kind of sign-in usually cannot be used from a Muse chat yet. Follow it here and we will tell you when it reaches Muse.
At the last check (November 13, 2026, 11:15 UTC) the endpoint was working, sign-in needed, answering in 618ms. Over the last 7 days it answered 92.9% of health checks. It is checked every 15 minutes.
It was screened on September 25, 2026 with the result "screened, no issues found". Screening checks the domain against threat feeds and reads the tools for hidden instructions and requests for passwords or card numbers. It cannot see the server's code, so grant only the access you need.
Send documents for signature, track signers, and get verifiable proof of signing. For example, you could ask Muse: "Send this contract to my client for signature and let me know when they've signed it."
This listing was added from public sources (Found in the official MCP Registry (io.github.ricdanyalgil/blueauth-document-signing)). If you build blue·auth Document Signing, claim it to correct the details and get your badge.
Paste this on your site or README. It always shows the latest check.
<a href="https://musedirectory.ai/connector/blue-auth-document-signing"><img src="https://musedirectory.ai/badge/blue-auth-document-signing.svg" alt="blue·auth Document Signing on musedirectory.ai" width="236" height="40"></a>