_ registry / mcp http-sse · checked 25m ago

swiftsign

https://swiftsign.ca

Registry code: 54ba7afe736b19c3

api record

E-signatures for agents: mint a sandbox key, send PDFs, track status, download the sealed result.

from a public catalogue that lists it, not from the operator

endpoint
https://swiftsign.ca/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is swiftsign live?
Yes — it answered the hub's last check (checked 25m ago). It answered 100% of checks over the last 30 days.
Is swiftsign free to use?
Not measured yet.
What tools does swiftsign have?
10 tools: swiftsign_check_status, swiftsign_list_envelopes, swiftsign_list_templates, swiftsign_send_envelope, swiftsign_confirm_send, swiftsign_send_from_template, swiftsign_void_envelope, swiftsign_download_signed_pdf, ….
Is swiftsign safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.6%

90 days 98.9%· all time 98.9%

latency
515ms

last good check

priced tools
0

of 10 tools

_ answered our checks, 90 days 556 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
documents & files
used for
  • send a pdf for e-signature
  • track signing status
  • download a signed pdf
  • void an envelope
takes → gives
documents → documents, data
tools
4 reads2 changes data1 moves money3 sends messages
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 10 tools
10 never probed 0 of 10 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • swiftsign_check_status reads unknown never probed

    Check the status of an envelope — who signed, who hasn't, download links. Works in both sandbox (sk_test_ keys) and live.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "envelopeId"
  ],
  "properties": {
    "envelopeId": {
      "type": "string",
      "description": "The envelope ID to check"
    }
  }
}
    arguments 13 lines
  • swiftsign_list_envelopes reads unknown never probed

    List envelopes (sent documents) with their status. Scoped to your key's mode — sandbox (sk_test_) keys see test envelopes, live keys see live.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • swiftsign_list_templates reads unknown never probed

    List your saved templates. Scoped to your key's mode — sandbox (sk_test_) keys see test templates, live keys see live.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • swiftsign_send_envelope sends messages unknown never probed

    Send a document for e-signature. Accepts PDF as base64, recipients, and field placement. Sandbox keys (sk_test_) send immediately (watermarked test mail). LIVE keys create a DRAFT and return it for human review unless confirm: true — nothing is emailed until confirmed. Field placement: page+x+y (percent, top-left origin) OR an anchor string, not both. After everyone signs, retrieve the sealed PDF with swiftsign_download_signed_pdf.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "subject",
    "documents",
    "recipients",
    "fields"
  ],
  "properties": {
    "fields": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "recipientIndex",
          "type",
          "page",
          "x",
          "y"
        ],
        "properties": {
          "x": {
            "type": "number",
            "description": "X position, percent 0-100 of page width, top-left origin"
          },
          "y": {
            "type": "number",
            "description": "Y position, percent 0-100 of page height, top-left origin"
          },
          "page": {
            "type": "number",
            "description": "Page number (1-based). Ignored when anchor resolves."
          },
          "type": {
            "enum": [
              "SIGNATURE",
              "NAME",
              "DATE",
              "TEXT",
              "INITIALS",
              "CHECKBOX",
              "RADIO",
              "DROPDOWN",
              "ATTACHMENT"
            ],
            "type": "string",
            "description": "Field type"
          },
          "width": {
            "type": "number",
            "description": "Field width (percent)"
          },
          "anchor": {
            "type": "string",
            "description": "Anchor text to search in the PDF. Use anchor OR page+x+y, not both."
          },
          "height": {
            "type": "number",
            "description": "Field height (percent)"
          },
          "options": {
            "type": "array",
            "items": {
              "type": "string"
            },
            "description": "Choices for RADIO / DROPDOWN fields"
          },
          "yOffset": {
            "type": "number",
            "description": "Y offset from anchor (percent)"
          },
          "document": {
            "type": "number",
            "default": 0,
            "description": "Document index (0-based)"
          },
          "recipientIndex": {
            "type": "number",
            "description": "Index into recipients array (0-based)"
          }
        }
      },
      "description": "Signing fields to place on documents"
    },
    "confirm": {
      "type": "boolean",
      "description": "Set true to dispatch immediately on a LIVE key (sk_live_/sk_oat_). Without it, live envelopes are created as DRAFT and returned for human review before anything is emailed. Test keys (sk_test_) always send immediately (sandbox, watermarked)."
    },
    "message": {
      "type": "string",
      "description": "Optional message to include"
    },
    "subject": {
      "type": "string",
      "description": "Email subject / document title"
    },
    "documents": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "name",
          "base64"
        ],
        "properties": {
          "name": {
            "type": "string",
            "description": "Document filename (e.g. 'contract.pdf')"
          },
          "base64": {
            "type": "string",
            "description": "Base64-encoded PDF content"
          }
        }
      },
      "description": "PDF documents to send"
    },
    "recipients": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "name",
          "email"
        ],
        "properties": {
          "name": {
            "type": "string",
            "description": "Recipient full name"
          },
          "role": {
            "enum": [
              "SIGNER",
              "CC"
            ],
            "type": "string",
            "default": "SIGNER"
          },
          "email": {
            "type": "string",
            "description": "Recipient email address"
          },
          "routingOrder": {
            "type": "number",
            "default": 1,
            "description": "Signing order (1 = first)"
          }
        }
      },
      "description": "People who need to sign or receive a copy"
    }
  }
}
    arguments 154 lines
  • swiftsign_confirm_send sends messages unknown never probed

    Dispatch a DRAFT envelope — use after a human has reviewed an envelope that swiftsign_send_envelope or swiftsign_send_from_template returned as draft_pending_confirmation. This emails the signers. Does NOT work on envelopes already SENT/COMPLETED/VOIDED.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "envelopeId"
  ],
  "properties": {
    "envelopeId": {
      "type": "string",
      "description": "The DRAFT envelope ID to dispatch"
    }
  }
}
    arguments 13 lines
  • swiftsign_send_from_template sends messages unknown never probed

    Send an envelope from a saved template by assigning signers to roles. Sandbox keys (sk_test_) send immediately; LIVE keys create a DRAFT for human review unless confirm: true — nothing is emailed until confirmed.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "templateId",
    "roleAssignments"
  ],
  "properties": {
    "confirm": {
      "type": "boolean",
      "description": "Set true to dispatch immediately on a LIVE key (sk_live_/sk_oat_). Without it, live envelopes are created as DRAFT and returned for human review before anything is emailed. Test keys (sk_test_) always send immediately (sandbox, watermarked)."
    },
    "message": {
      "type": "string",
      "description": "Optional message to include"
    },
    "subject": {
      "type": "string",
      "description": "Email subject / document title"
    },
    "templateId": {
      "type": "string",
      "description": "The template ID to send from"
    },
    "roleAssignments": {
      "type": "object",
      "description": "Map of template role name → signer { name, email }",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {
        "type": "object",
        "required": [
          "name",
          "email"
        ],
        "properties": {
          "name": {
            "type": "string",
            "description": "Signer full name"
          },
          "email": {
            "type": "string",
            "description": "Signer email address"
          }
        }
      }
    }
  }
}
    arguments 50 lines
  • swiftsign_void_envelope changes data unknown never probed

    Cancel/void an envelope that hasn't been completed yet. Signers can no longer sign a voided envelope. Works in both sandbox (sk_test_ keys) and live.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "envelopeId"
  ],
  "properties": {
    "envelopeId": {
      "type": "string",
      "description": "The envelope ID to void"
    }
  }
}
    arguments 13 lines
  • swiftsign_download_signed_pdf reads unknown never probed

    Download the completed, sealed PDF (or its Certificate of Completion) for an envelope. Only works once status is COMPLETED — run swiftsign_check_status first. Does NOT work on DRAFT or SENT envelopes; nothing has been signed yet on those.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "envelopeId"
  ],
  "properties": {
    "document": {
      "type": "number",
      "description": "Which document to download when an envelope has several (0-based, default 0)"
    },
    "envelopeId": {
      "type": "string",
      "description": "The envelope ID (must be COMPLETED)"
    },
    "outputPath": {
      "type": "string",
      "description": "Where to save the file (default: ./swiftsign-<id>.pdf). Ignored on the hosted endpoint, which returns base64."
    },
    "certificate": {
      "type": "boolean",
      "description": "If true, download the Certificate of Completion (audit trail) instead of the signed document"
    }
  }
}
    arguments 25 lines
  • swiftsign_upgrade moves money unknown never probed

    Initiate the upgrade to PRO ($15/mo flat). Returns a Stripe checkout_url that a human opens once to add a card — agents cannot complete the payment themselves. Moves the account from sandbox (sk_test_) to live sends. Returns status 'updated' if already on the plan.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "plan": {
      "type": "string",
      "const": "PRO",
      "description": "Plan to upgrade to (default PRO)"
    }
  }
}
    arguments 11 lines
  • swiftsign_create_embedded_url changes data unknown never probed

    Mint a short-lived embedded signing URL for a recipient (30-minute expiry). Returns a url to embed plus its expiresAt. The envelope must already be SENT. Works in both sandbox (sk_test_ keys) and live.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "envelopeId",
    "recipientId"
  ],
  "properties": {
    "returnUrl": {
      "type": "string",
      "description": "URL to redirect the signer to after they finish"
    },
    "envelopeId": {
      "type": "string",
      "description": "The envelope ID"
    },
    "recipientId": {
      "type": "string",
      "description": "The recipient ID within that envelope"
    }
  }
}
    arguments 22 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 54ba7afe736b19c3.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/54ba7afe736b19c3/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/54ba7afe736b19c3/badge.svg)](https://brick.blue/agent/54ba7afe736b19c3?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.