Sequesign MCP Server

Cryptographically verifiable receipts of an agent's delegated work, verified offline.

Local serverstdio

What is the Sequesign MCP Server?

Sequesign is an MCP integration. Cryptographically verifiable receipts of an agent's delegated work, verified offline.

Packages and local setup

The published npm package is @sequesign/mcp, version 0.4.1. Its declared MCP transport is stdio.

The package declares SEQUESIGN_MODE: Transport: 'direct' (default; sign locally, an independent witness co-signs) or 'managed' (route through the Sequesign broker for a registered identity).; SEQUESIGN_API_KEY: Sequesign write-class API key (from the dashboard). Required for managed mode; in direct mode it authenticates the hosted witness.; SEQUESIGN_AGENT_PRIVATE_KEY: Ed25519 PKCS8 private-key PEM for the agent. In managed mode, the key registered to your API key. In direct mode, omit to mint an ephemeral key per session.; SEQUESIGN_PACKAGE_DIR: Directory where sealed receipt packages are written. Defaults to a temporary directory.; SEQUESIGN_TEMPLATE_REGISTRY_URL: Base URL of a read-only dynamic template registry (e.g. https://dashboard-api.sequesign.com/v1/registry). When set, direct-mode sessions and the discovery tools resolve templates published there in addition to the bundled ones, falling back to bundled offline. Omit to use only the bundled templates.; SEQUESIGN_TEMPLATE_REGISTRY_TOKEN: Read-only bearer token for an account-scoped template registry (discovery only; never used in verification). Omit for a public registry..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.4.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
SEQUESIGN_MODETransport: 'direct' (default; sign locally, an independent witness co-signs) or 'managed' (route through the Sequesign broker for a registered identity).Optional
SEQUESIGN_API_KEYSequesign write-class API key (from the dashboard). Required for managed mode; in direct mode it authenticates the hosted witness.Optional
SEQUESIGN_AGENT_PRIVATE_KEYEd25519 PKCS8 private-key PEM for the agent. In managed mode, the key registered to your API key. In direct mode, omit to mint an ephemeral key per session.Optional
SEQUESIGN_PACKAGE_DIRDirectory where sealed receipt packages are written. Defaults to a temporary directory.Optional
SEQUESIGN_TEMPLATE_REGISTRY_URLBase URL of a read-only dynamic template registry (e.g. https://dashboard-api.sequesign.com/v1/registry). When set, direct-mode sessions and the discovery tools resolve templates published there in addition to the bundled ones, falling back to bundled offline. Omit to use only the bundled templates.Optional
SEQUESIGN_TEMPLATE_REGISTRY_TOKENRead-only bearer token for an account-scoped template registry (discovery only; never used in verification). Omit for a public registry.Optional