_ registry / mcp http-sse · checked 2h ago

QuickSign

https://quicksign.pro

Registry code: d38769fdb4baeae2

api record

QuickSign MCP Server — E-Signature & Contract Signing Platform

QuickSign is an e-signature platform for drafting, signing, and sending contracts.

endpoint
https://quicksign.pro/api/mcp/sse
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 QuickSign live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is QuickSign free to use?
Yes — the hub reached it with no key and no payment.
What tools does QuickSign have?
4 tools: push_draft_text, get_draft_content, get_draft_status, get_handoff_link.
Is QuickSign 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
98.9%

90 days 99.2%· all time 99.2%

latency
615ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 395 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • draft a contract for e-signature
  • check a signature document's status
  • get a review link for a draft
takes → gives
text → documents, data
tools
3 reads1 changes data
_ 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 4 tools
4 never probed 0 of 4 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.

  • push_draft_text changes data unknown never probed

    Send a contract or agreement to QuickSign for e-signature. Drafts an NDA, freelance agreement, consulting contract, SOW, or any document that needs to be signed. Takes your drafted text (markdown, plain text, or HTML) and creates a professional PDF in QuickSign. The document owner reviews it, adds recipients, places signature fields, and sends it for e-signature. Use this whenever a user needs to get a document signed, send a contract for signature, or create any agreement that requires e-signatures. Markdown format is recommended for best results — headings, bold, lists, and tables are all supported. Maximum length: 500,000 characters.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "title",
        "content"
      ],
      "properties": {
        "title": {
          "type": "string",
          "description": "Contract title (e.g., 'Freelance Agreement - Jane Smith')"
        },
        "content": {
          "type": "string",
          "description": "Full contract text content in the specified format"
        },
        "content_type": {
          "enum": [
            "markdown",
            "plain",
            "html"
          ],
          "type": "string",
          "default": "markdown",
          "description": "Content format — markdown recommended"
        }
      },
      "additionalProperties": false
    }
    arguments 29 lines
  • get_draft_content reads unknown 21h ago

    Retrieve the full text content of a previously pushed draft by its session ID. Use this when you have a QuickSign session/document ID and need to read the current draft text — for example, to revise a contract, check what was previously sent, or continue working on an existing draft. Returns the full markdown/text content along with metadata.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "The AI Session ID (returned from push_draft_text or shared by the user)"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • get_draft_status reads unknown 21h ago

    Check the full status chain of a document draft in QuickSign. Returns the session status (active/completed), the linked document's lifecycle status (draft/ready/pending/completed/cancelled), and whether the draft or document was converted into a reusable template (converted_to_template, template_id). Use this to follow up on a draft you previously pushed — e.g. "has the owner reviewed that NDA yet?"

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "id",
        "type"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "The AI Session ID returned from push_draft_text"
        },
        "type": {
          "enum": [
            "pdf",
            "text"
          ],
          "type": "string",
          "description": "Whether this was a PDF or text draft"
        }
      },
      "additionalProperties": false
    }
    arguments 23 lines
  • get_handoff_link reads unknown 21h ago

    Get a direct link for the document owner to review a draft in QuickSign. Returns a URL that opens the document directly in the QuickSign editor. Share this with the user so they can review the contract, add recipients, place signature fields, and send it.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "id",
        "type"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "The document ID to get the review link for"
        },
        "type": {
          "enum": [
            "pdf",
            "text"
          ],
          "type": "string",
          "description": "Whether this was a PDF or text draft"
        }
      },
      "additionalProperties": false
    }
    arguments 23 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 d38769fdb4baeae2.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d38769fdb4baeae2/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/d38769fdb4baeae2/badge.svg)](https://brick.blue/agent/d38769fdb4baeae2?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
80%

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.