Productivity

blocksign.red

Create, send, list, and verify agreements and contract templates with status tracking and audit-chain verification.

1 endpoint11 known toolsFirst detected September 12, 2026Last detected September 12, 2026

ENDPOINT 1

https://mcp.blocksign.red/mcp

No auth detected

MCP server metadata

Name: blocksign-mcp-server
Version: 0.0.1

Capabilities

promptsresourcestools

Server instructions

Use these tools to create blockchain-anchored e-signature agreements. With an API key, pass Authorization: Bearer bsk_agent_*. No key? Call create_agreement with 'payment' (a Stripe shared token spt_*) and 'sender' (name + email) — we charge and treat the payer as the sender. Start with `list_templates`, or `create_agreement` for a one-call signing flow.

Known tools 11

create_agreement

Create and optionally send an agreement in a single call.

Potential side effects

get_agreement_status

Fetch unified status for an agreement: envelope state, per-signer status, verification URL.

Inferred read-only

list_agreements

List recent agreements for the calling org.

Inferred read-only

list_templates

List contract templates available to the calling org (org-owned + platform public).

Inferred read-only

verify_agreement

Public verification of an agreement's audit chain and on-chain anchor.

Inferred read-only

void_agreement

Void an envelope before all parties sign.

Inferred read-only

preview_template

Render a template with variables (no PDF, no envelope) — useful to validate inputs before create_agreement.

Inferred read-only

upload_document

Upload a document for use in agreements.

Potential side effects

detect_fields

Run AI field detection on a previously uploaded text document.

Inferred read-only

check_billing_status

Check current billing plan, credit balance, usage, and per-document pricing for the calling org.

Inferred read-only

purchase_credits

Purchase a credit pack (10, 50, or 200 credits).

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.blocksign-mcp-server]
url = "https://mcp.blocksign.red/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "blocksign-mcp-server": {
      "type": "http",
      "url": "https://mcp.blocksign.red/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: blocksign-mcp-server
Remote MCP URL: https://mcp.blocksign.red/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "blocksign-mcp-server": {
      "url": "https://mcp.blocksign.red/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "blocksign-mcp-server": {
      "type": "http",
      "url": "https://mcp.blocksign.red/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "blocksign-mcp-server",
  "transport": "streamable-http",
  "url": "https://mcp.blocksign.red/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.