InkSeal

net.inksealPublished by inkseal.netOfficial publisherv1.0.0Updated Oct 24, 2026

Send documents for signature: upload, place fields, draft, and send once a human agrees.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

InkSeal is a remote MCP server that lets an assistant prepare documents for e-signature: upload files, place fields, draft, and send once a human agrees.

What you can do
Upload documents to InkSeal for signature workflows and place signature fields on them. Draft signature requests and send them once a human has agreed. The API key determines which workspace the server acts in and which tools are offered, so the available actions depend on the credential used.
When to use it
Useful when you want an assistant to prepare and route documents for e-signature inside an InkSeal workspace, while keeping a human approval step before anything is sent.
Requirements
A remote streamable HTTP endpoint at inkseal.net, reachable over the network. OAuth authentication is required, using an InkSeal API key sent in the Authorization header, minted in the InkSeal service credentials area. No local runtime or packages are needed.
Before you install
The server requires an API key in the Authorization header; treat it as a secret and keep it out of shared logs. It can upload documents and send signature requests, which are outward-facing actions affecting other people, so confirm the human approval step before sending. Documents are sent to a third-party service, InkSeal.

Installation

In SourceWeft

  1. Open InkSeal 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/net.inkseal%2Finkseal/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": {
    "inkseal": {
      "type": "http",
      "url": "https://inkseal.net/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.0LatestSep 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 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.